Does SpeedyCache work with WordPress 6.1.1 and PHP 8.1.12? A smoke test was performed on .
19 | PHP notices |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors |
Memory usage: 58.05 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.1.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 200,000+ |
WordPress.org page | https://wordpress.org/plugins/speedycache/ |
Badges |
Get badge code |
URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=speedycache%2Fspeedycache.php&plugin_status=all&paged=1&s&_wpnonce=d6e19fd9bd |
Aspect | after-activation |
HTTP status | 200 |
Load time | 0.447 s |
Memory usage | 3.05 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=speedycache |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.371 s |
Memory usage | 4.06 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=speedycache-manage-cache |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.230 s |
Memory usage | 3.02 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=speedycache-cdn |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.260 s |
Memory usage | 3.02 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=speedycache-exclude |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.213 s |
Memory usage | 3.02 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=speedycache-db |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.218 s |
Memory usage | 3.02 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/admin.php?page=speedycache-support |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.211 s |
Memory usage | 3.02 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.235 s |
Memory usage | 3.08 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.271 s | 0.251 s | -0.020 s | 3.05 MiB | 3.1 MiB | + 57.97 KiB |
/wp-admin/edit.php | 0.178 s | 0.190 s | +0.012 s | 3.07 MiB | 3.13 MiB | + 58.67 KiB |
/wp-admin/post-new.php | 0.764 s | 0.967 s | +0.203 s | 4.97 MiB | 5.03 MiB | + 63.52 KiB |
/wp-admin/upload.php | 0.552 s | 0.459 s | -0.093 s | 2.99 MiB | 3.03 MiB | + 40.91 KiB |
/wp-admin/options-writing.php | 0.132 s | 0.165 s | +0.033 s | 2.99 MiB | 3.01 MiB | + 26.94 KiB |
/wp-admin/media-new.php | 0.246 s | 0.240 s | -0.006 s | 2.97 MiB | 3.02 MiB | + 53.1 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.187 s | 0.177 s | -0.010 s | 2.98 MiB | 3.04 MiB | + 58.9 KiB |
/wp-admin/post-new.php?post_type=page | 0.591 s | 0.605 s | +0.014 s | 4.96 MiB | 5.02 MiB | + 58.23 KiB |
/wp-admin/options-discussion.php | 0.214 s | 0.229 s | +0.015 s | 2.97 MiB | 3.01 MiB | + 40.78 KiB |
/wp-admin/edit-comments.php | 0.195 s | 0.201 s | +0.006 s | 3 MiB | 3.04 MiB | + 40.95 KiB |
/ | 0.289 s | 0.215 s | -0.074 s | 2.94 MiB | 3.08 MiB | + 138.61 KiB |
Average | 0.329 s | 0.336 s | +0.007 s | 3.35 MiB | 3.41 MiB | + 58.05 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 | 62.8% | 6,933 | 1,177 | 21 | |
JavaScript | 17.3% | 1,905 | 100 | 3 | |
CSS | 14.2% | 1,571 | 40 | 3 | |
SVG | 5.7% | 626 | 0 | 2 | |
HTML | 0.0% | 2 | 0 | 1 | |
Total | 11,037 | 1,317 | 30 |
Lines of code | 7,734 |
---|---|
Total complexity | 1,927 |
Median class complexity | 52.5 |
Median method complexity | 6.0 |
Most complex class | SpeedyCache\Cache |
Most complex function | speedycache_settings_page() |
Classes | 14 |
---|---|
Methods | 159 |
Functions | 92 |
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[01-Feb-2023 14:38:39 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:47 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:50 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:51 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:53 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:53 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:53 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:53 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:54 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:54 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:54 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:54 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835
[01-Feb-2023 14:38:55 UTC] PHP Notice: Function WP_User_Query::query was called <strong>incorrectly</strong>. User queries should not be run before the <code>plugins_loaded</code> hook. 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 6.1.1.) in /wp-includes/functions.php on line 5835