Does "The Ultimate AdBlock Detector - AdBlock Guard" work with WordPress 6.7.1 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: 326.8 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
0.403 seconds
The average page load time increased by this amount after activating the plugin.
WordPress version | 6.7.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 70+ |
WordPress.org page | https://wordpress.org/plugins/ad-block-guard/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=ad-block-guard%2Fad-block-guard.php&plugin_status=all&paged=1&s&_wpnonce=5ff8916e8b |
Aspect | after-activation |
HTTP status | 200 |
Load time | 2.135 s |
Memory usage | 4.1 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wuadblockguard_settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 2.184 s |
Memory usage | 4.31 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wuadblockguard_demo_page |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.012 s |
Memory usage | 3.8 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=wuadblockguard_license_key |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.622 s |
Memory usage | 3.81 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.292 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.521 s | 0.940 s | +0.419 s | 3.48 MiB | 3.87 MiB | + 400.48 KiB |
/wp-admin/edit.php | 0.225 s | 0.748 s | +0.523 s | 3.54 MiB | 3.89 MiB | + 359.83 KiB |
/wp-admin/post-new.php | 0.825 s | 1.963 s | +1.138 s | 5.92 MiB | 6.3 MiB | + 384.59 KiB |
/wp-admin/upload.php | 0.697 s | 0.892 s | +0.195 s | 3.49 MiB | 3.8 MiB | + 316.78 KiB |
/wp-admin/options-writing.php | 0.250 s | 0.656 s | +0.406 s | 3.47 MiB | 3.79 MiB | + 330.85 KiB |
/wp-admin/media-new.php | 0.282 s | 0.764 s | +0.482 s | 3.46 MiB | 3.79 MiB | + 339.05 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.224 s | 0.676 s | +0.452 s | 3.48 MiB | 3.82 MiB | + 357.23 KiB |
/wp-admin/post-new.php?post_type=page | 1.124 s | 1.192 s | +0.068 s | 5.92 MiB | 6.29 MiB | + 385.56 KiB |
/wp-admin/options-discussion.php | 0.302 s | 0.852 s | +0.550 s | 3.47 MiB | 3.79 MiB | + 327.79 KiB |
/wp-admin/edit-comments.php | 0.262 s | 0.752 s | +0.490 s | 3.49 MiB | 3.83 MiB | + 348.94 KiB |
/ | 0.525 s | 0.237 s | -0.288 s | 3.47 MiB | 3.52 MiB | + 43.75 KiB |
Average | 0.476 s | 0.879 s | +0.403 s | 3.93 MiB | 4.25 MiB | + 326.8 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 | 60.6% | 2,730 | 1,168 | 19 | |
JavaScript | 16.7% | 752 | 97 | 7 | |
PO File | 9.3% | 417 | 198 | 1 | |
CSS | 5.7% | 255 | 15 | 3 | |
Bourne Shell | 4.5% | 204 | 34 | 4 | |
JSON | 3.3% | 147 | 0 | 5 | |
Total | 4,505 | 1,512 | 39 |
Lines of code | 3,092 |
---|---|
Total complexity | 553 |
Median class complexity | 28.0 |
Median method complexity | 2.0 |
Most complex class | WuAdBlockGuard\Frontend |
Most complex function | WuAdBlockGuard\CarbonFieldsSetup::define_fields() |
Classes | 16 |
---|---|
Methods | 203 |
Functions | 4 |
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
2The log file is empty.