SpeedyCache 1.0.0

Does SpeedyCache work with WordPress 6.1.1 and PHP 8.1.12? A smoke test was performed on .

Summary

Errors
19PHP notices
No JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

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.

Environment
WordPress version6.1.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 200,000+
WordPress.org page https://wordpress.org/plugins/speedycache/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 8

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
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

SpeedyCache

Page screenshot: SpeedyCache
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

SpeedyCache → Manage Cache

Page screenshot: SpeedyCache → Manage Cache
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

SpeedyCache → CDN

Page screenshot: SpeedyCache → CDN
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

SpeedyCache → Excludes

Page screenshot: SpeedyCache → Excludes
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

SpeedyCache → Database

Page screenshot: SpeedyCache → Database
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

SpeedyCache → Support

Page screenshot: SpeedyCache → Support
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

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.235 s
Memory usage 3.08 MiB
JS errors None
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.271 s0.251 s-0.020 s3.05 MiB3.1 MiB+ 57.97 KiB
/wp-admin/edit.php0.178 s0.190 s+0.012 s3.07 MiB3.13 MiB+ 58.67 KiB
/wp-admin/post-new.php0.764 s0.967 s+0.203 s4.97 MiB5.03 MiB+ 63.52 KiB
/wp-admin/upload.php0.552 s0.459 s-0.093 s2.99 MiB3.03 MiB+ 40.91 KiB
/wp-admin/options-writing.php0.132 s0.165 s+0.033 s2.99 MiB3.01 MiB+ 26.94 KiB
/wp-admin/media-new.php0.246 s0.240 s-0.006 s2.97 MiB3.02 MiB+ 53.1 KiB
/wp-admin/edit-tags.php?taxonomy=category0.187 s0.177 s-0.010 s2.98 MiB3.04 MiB+ 58.9 KiB
/wp-admin/post-new.php?post_type=page0.591 s0.605 s+0.014 s4.96 MiB5.02 MiB+ 58.23 KiB
/wp-admin/options-discussion.php0.214 s0.229 s+0.015 s2.97 MiB3.01 MiB+ 40.78 KiB
/wp-admin/edit-comments.php0.195 s0.201 s+0.006 s3 MiB3.04 MiB+ 40.95 KiB
/0.289 s0.215 s-0.074 s2.94 MiB3.08 MiB+ 138.61 KiB
Average 0.329 s0.336 s+0.007 s3.35 MiB3.41 MiB+ 58.05 KiB

Code Statistics

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.

PHP
JavaScript
CSS
Language % Lines of code Comment lines Files
PHP62.8%6,9331,17721
JavaScript17.3%1,9051003
CSS14.2%1,571403
SVG5.7%62602
HTML0.0%201
Total 11,037 1,317 30

PHP Code Analysis | More results »

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

Additions

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.

Options wp_options 2

PHP Error Log 19 lines

[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
See also: All tests for this plugin, How to Hide SpeedyCache Admin Menus