Does "CookieAdmin - Cookie Consent Banner" work with WordPress 6.8.2 and PHP 8.1.12? A smoke test was performed on .
4 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 29.79 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 | 60,000+ |
WordPress.org page | https://wordpress.org/plugins/cookieadmin/ |
Badges |
|
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=cookieadmin%2Fcookieadmin.php&plugin_status=all&paged=1&s&_wpnonce=31a495701c |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.264 s |
Memory usage | 3.67 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=cookieadmin |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.224 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=cookieadmin-consent |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.314 s |
Memory usage | 3.66 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=cookieadmin-settings |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.156 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=cookieadmin-scan-cookies |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.180 s |
Memory usage | 3.52 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.264 s |
Memory usage | 3.7 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.338 s | 0.263 s | -0.075 s | 3.51 MiB | 3.52 MiB | + 18.35 KiB |
/wp-admin/edit.php | 0.174 s | 0.186 s | +0.012 s | 3.57 MiB | 3.59 MiB | + 18.39 KiB |
/wp-admin/post-new.php | 0.720 s | 0.606 s | -0.114 s | 6.06 MiB | 6.08 MiB | + 22.77 KiB |
/wp-admin/upload.php | 0.576 s | 0.479 s | -0.097 s | 3.52 MiB | 3.52 MiB | + 1008 bytes |
/wp-admin/options-writing.php | 0.185 s | 0.180 s | -0.005 s | 3.5 MiB | 3.51 MiB | + 4.98 KiB |
/wp-admin/media-new.php | 0.256 s | 0.203 s | -0.053 s | 3.49 MiB | 3.5 MiB | + 13.17 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.180 s | 0.194 s | +0.014 s | 3.5 MiB | 3.53 MiB | + 23.85 KiB |
/wp-admin/post-new.php?post_type=page | 0.600 s | 0.609 s | +0.009 s | 6.05 MiB | 6.07 MiB | + 18.3 KiB |
/wp-admin/options-discussion.php | 0.266 s | 0.271 s | +0.005 s | 3.5 MiB | 3.5 MiB | + 1.48 KiB |
/wp-admin/edit-comments.php | 0.180 s | 0.184 s | +0.004 s | 3.52 MiB | 3.52 MiB | + 1000 bytes |
/ | 0.280 s | 0.433 s | +0.153 s | 3.5 MiB | 3.7 MiB | + 204.38 KiB |
Average | 0.341 s | 0.328 s | -0.013 s | 3.98 MiB | 4 MiB | + 29.79 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 | 40.3% | 1,637 | 127 | 10 | |
CSS | 35.1% | 1,427 | 70 | 2 | |
JavaScript | 22.1% | 898 | 74 | 3 | |
JSON | 2.0% | 83 | 0 | 2 | |
SVG | 0.4% | 15 | 0 | 2 | |
Total | 4,060 | 271 | 19 |
Lines of code | 1,667 |
---|---|
Total complexity | 375 |
Median class complexity | 22.0 |
Median method complexity | 4.0 |
Most complex class | CookieAdmin\Admin |
Most complex function | CookieAdmin\Admin::cookieadmin_save_settings() |
Classes | 6 |
---|---|
Methods | 34 |
Functions | 20 |
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[21-Aug-2025 08:00:51 UTC] PHP Notice: Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6121
[21-Aug-2025 08:00:52 UTC] PHP Notice: Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6121
[21-Aug-2025 08:00:53 UTC] PHP Notice: Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6121
[21-Aug-2025 08:00:54 UTC] PHP Notice: Function WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 6121