Description
SSF Speed Cache provides a local early page cache for eligible cookie-free public GET requests. It includes content-change invalidation, exclusions, a cache inspector, lazy content images, explicit hero priority, reviewed standalone-script deferral and previous-settings restore.
Use the path inspector to see whether an anonymous request is eligible and whether a fresh entry exists. Restore the previous settings if a change affects your site. The plugin works locally without an account or a paid add-on.
The cache deliberately skips forms, tokens, private pages, sessions, query strings, cart/checkout/account paths and unsupported response variations. Custom dynamic sites require explicit exclusions and staging tests. The public path inventory is indexed in batches. Multisite is not supported in 1.0.
External services
The optional ssf_speed_video shortcode displays a local button. If a visitor clicks it, their browser connects to www.youtube-nocookie.com to display the selected video and sends the request information needed for playback, including their IP address and browser headers. No video or thumbnail is requested before the click. See YouTube Terms of Service and Google Privacy Policy.
Source code
All PHP, JavaScript and CSS distributed here are the editable sources. The click-to-play handler is in assets/media.js. Its styles and the settings screen styles are in assets/media.css and assets/admin.css. They are loaded directly; no build step is required.
Installation
- Back up and test on staging. Keep one page-cache owner and review host/CDN caching separately.
- Install and activate the ZIP.
- Ensure WP_CACHE is defined as true before wp-settings.php in wp-config.php, using the host’s file editor. Do not add a duplicate definition.
- Open SSF Speed Cache and enable early page caching. Existing foreign drop-in files are not overwritten.
- Verify an eligible page twice without cookies; inspect X-SSF-Speed-Cache response headers. Test all dynamic and private journeys.
FAQ
-
Does it guarantee a score or ranking?
-
No. Hosting, content, themes, extensions, third-party scripts and visitor conditions affect results.
-
Why does a page bypass caching?
-
Requests with cookies, authentication, query strings or protected paths bypass. Responses with forms, input fields, request tokens, private cache headers or unsupported variations also bypass. The inspector explains configuration decisions; real request conditions can add more exclusions.
-
How do I disable it?
-
Use Recovery to disable caching, or deactivate the plugin. Deactivation removes only SSF’s own advanced-cache.php. Saved settings remain available.
-
Does it modify server configuration?
-
No. It does not edit wp-config.php, server compression, the site’s root .htaccess, CDN settings or a foreign advanced-cache.php. The private cache folder receives its own access-protection files.
-
Does it send data externally?
-
No telemetry or SSF account is required. The optional [ssf_speed_video id=”VIDEO_ID” title=”Watch video”] shortcode contacts YouTube after the visitor clicks. See https://www.youtube.com/t/terms and https://policies.google.com/privacy. No remote YouTube thumbnail is fetched before the click.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“SSF Speed Cache” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “SSF Speed Cache” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.1
- Validate individual settings and extension form fields, and reject ambiguous request paths before reading the cache.
- Index public pages in batches and preserve additional security headers on cache hits.
- Supply readable asset sources and document the optional video service.
1.0.0
- First release: early public-page cache, exclusions, invalidation, media controls, diagnostics and recovery.
