Does "Global Weather Pro: Accurate Local Forecasts" work with WordPress 6.8.2 and PHP 8.1.12? A smoke test was performed on .
| No PHP errors, warnings or notices | |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors | |
| Looks good! No problems were detected. |
Memory usage: 10.81 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
| WordPress version | 6.8.2 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
| Last updated | |
|---|---|
| Active installs | <10 |
| WordPress.org page | https://wordpress.org/plugins/global-weather-pro/ |
| Badges |
|
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=global-weather-pro%2Fglobal-weather-pro.php&plugin_status=all&paged=1&s&_wpnonce=c1e248db34 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.311 s |
| Memory usage | 3.55 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/options-general.php?page=global-weather-pro |
|---|---|
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 4.498 s |
| Memory usage | 3.88 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.221 s |
| Memory usage | 3.46 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/widgets.php |
|---|---|
| Aspect | new-sidebar-widgets |
| HTTP status | 200 |
| Load time | 1.351 s |
| Memory usage | 5.84 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.377 s | 0.349 s | -0.028 s | 3.51 MiB | 3.53 MiB | + 22.64 KiB |
| /wp-admin/edit.php | 0.207 s | 0.217 s | +0.010 s | 3.57 MiB | 3.59 MiB | + 22.48 KiB |
| /wp-admin/post-new.php | 0.850 s | 0.696 s | -0.154 s | 6.06 MiB | 6.09 MiB | + 26.11 KiB |
| /wp-admin/upload.php | 0.665 s | 0.526 s | -0.139 s | 3.52 MiB | 3.53 MiB | + 5.07 KiB |
| /wp-admin/options-writing.php | 0.225 s | 0.213 s | -0.012 s | 3.5 MiB | 3.51 MiB | + 9.07 KiB |
| /wp-admin/media-new.php | 0.462 s | 0.249 s | -0.213 s | 3.49 MiB | 3.51 MiB | + 17.27 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.235 s | 0.203 s | -0.032 s | 3.5 MiB | 3.53 MiB | + 27.94 KiB |
| /wp-admin/post-new.php?post_type=page | 0.682 s | 0.623 s | -0.059 s | 6.05 MiB | 6.07 MiB | + 21.64 KiB |
| /wp-admin/options-discussion.php | 0.336 s | 0.401 s | +0.065 s | 3.5 MiB | 3.51 MiB | + 5.57 KiB |
| /wp-admin/edit-comments.php | 0.426 s | 0.196 s | -0.230 s | 3.52 MiB | 3.53 MiB | + 5.07 KiB |
| / | 0.317 s | 0.400 s | +0.083 s | 3.5 MiB | 3.46 MiB | - 43.95 KiB |
| Average | 0.435 s | 0.370 s | -0.064 s | 3.98 MiB | 3.99 MiB | + 10.81 KiB |
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| CSS | 50.4% | 2,407 | 134 | 7 | |
| JavaScript | 37.1% | 1,774 | 180 | 9 | |
| PHP | 7.5% | 360 | 51 | 3 | |
| SVG | 4.9% | 236 | 0 | 236 | |
| HTML | 0.1% | 3 | 0 | 3 | |
| Total | 4,780 | 365 | 258 | ||
| Lines of code | 366 |
|---|---|
| Total complexity | 60 |
| Median class complexity | 2.0 |
| Median method complexity | 1.0 |
| Most complex class | GWPro_Header_Weather_Widget |
| Most complex function | handle_get_weather_data_and_localize() |
| Classes | 2 |
|---|---|
| Methods | 4 |
| Functions | 17 |
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
wp_options 2| ID | Name |
|---|---|
| gwpro_header_weather_widget | Global Weather Pro Header |
| gwpro_sidebar_weather_widget | Global Weather Pro Sidebar |
The log file is empty.