Does Muzaara Google Ads Report work with WordPress 5.8.1 and PHP 7.4.8? A smoke test was performed on .
8 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 144.89 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.098 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 5.8.1 |
---|---|
PHP version | 7.4.8 |
MySQL version | 8.0.21 |
PHP memory limit | 256M |
Last updated | |
---|---|
Active installs | 90+ |
WordPress.org page | https://wordpress.org/plugins/muzaara-adwords-optimize-dashboard/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=muzaara-adwords-optimize-dashboard%2Fmuzaara-gads.php&plugin_status=all&paged=1&s&_wpnonce=6d31e9db77 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.728 s |
Memory usage | 3.21 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=muzaara |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.809 s |
Memory usage | 3.18 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=muzaara-settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.595 s |
Memory usage | 3.18 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.292 s |
Memory usage | 2.94 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.319 s | 0.445 s | +0.126 s | 3.08 MiB | 3.23 MiB | + 154.3 KiB |
/wp-admin/edit.php | 0.180 s | 0.252 s | +0.072 s | 3.11 MiB | 3.33 MiB | + 218.67 KiB |
/wp-admin/post-new.php | 1.059 s | 1.273 s | +0.214 s | 5.27 MiB | 5.38 MiB | + 117.41 KiB |
/wp-admin/upload.php | 0.539 s | 0.610 s | +0.071 s | 3.03 MiB | 3.2 MiB | + 177.13 KiB |
/wp-admin/options-writing.php | 0.162 s | 0.218 s | +0.056 s | 3.02 MiB | 3.18 MiB | + 157.71 KiB |
/wp-admin/media-new.php | 0.265 s | 0.279 s | +0.014 s | 3.01 MiB | 3.17 MiB | + 170.05 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.195 s | 0.330 s | +0.135 s | 3.04 MiB | 3.2 MiB | + 162.77 KiB |
/wp-admin/post-new.php?post_type=page | 0.917 s | 1.102 s | +0.185 s | 5.26 MiB | 5.37 MiB | + 117 KiB |
/wp-admin/options-discussion.php | 0.224 s | 0.444 s | +0.220 s | 3 MiB | 3.18 MiB | + 177.61 KiB |
/wp-admin/edit-comments.php | 0.210 s | 0.279 s | +0.069 s | 3.04 MiB | 3.2 MiB | + 161.35 KiB |
/ | 0.333 s | 0.244 s | -0.089 s | 2.96 MiB | 2.94 MiB | - 20.2 KiB |
Average | 0.400 s | 0.498 s | +0.098 s | 3.44 MiB | 3.58 MiB | + 144.89 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 | |
---|---|---|---|---|---|
PHP | 92.0% | 124,393 | 154,895 | 3,305 | |
JSON | 4.9% | 6,608 | 0 | 123 | |
JavaScript | 1.7% | 2,298 | 150 | 13 | |
CSS | 0.9% | 1,163 | 27 | 8 | |
Markdown | 0.4% | 550 | 0 | 7 | |
SVG | 0.0% | 57 | 0 | 2 | |
Protocol Buffers | 0.0% | 33 | 0 | 1 | |
YAML | 0.0% | 31 | 0 | 2 | |
Dockerfile | 0.0% | 12 | 5 | 1 | |
XML | 0.0% | 12 | 0 | 1 | |
INI | 0.0% | 8 | 2 | 2 | |
Bourne Shell | 0.0% | 4 | 2 | 1 | |
Total | 135,169 | 155,081 | 3,466 |
Lines of code | 120,349 |
---|---|
Total complexity | 18,849 |
Median class complexity | 2.0 |
Median method complexity | 1.0 |
Most complex class | Google\Ads\GoogleAds\V6\Services\GoogleAdsRow |
Most complex function | Google\Ads\GoogleAds\Util\FieldMasks::buildPaths() |
Classes | 3,050 |
---|---|
Methods | 14,541 |
Functions | 23 |
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
1[14-Sep-2021 04:15:10 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/access</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:10 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/devKey</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:10 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/access</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:10 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/devKey</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:14 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/access</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:14 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/devKey</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:14 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/access</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663
[14-Sep-2021 04:15:14 UTC] PHP Notice: register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>muzaara/v1/devKey</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5663