Title: Andrei Baicus's Replies | WordPress.org --- # Andrei Baicus [ ](https://wordpress.org/support/users/baicusandrei/) * [Profile](https://wordpress.org/support/users/baicusandrei/) * [Topics Started](https://wordpress.org/support/users/baicusandrei/topics/) * [Replies Created](https://wordpress.org/support/users/baicusandrei/replies/) * [Reviews Written](https://wordpress.org/support/users/baicusandrei/reviews/) * [Topics Replied To](https://wordpress.org/support/users/baicusandrei/replied-to/) * [Engagements](https://wordpress.org/support/users/baicusandrei/engagements/) * [Favorites](https://wordpress.org/support/users/baicusandrei/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 113 total) 1 [2](https://wordpress.org/support/users/baicusandrei/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/baicusandrei/replies/page/3/?output_format=md)… [6](https://wordpress.org/support/users/baicusandrei/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/baicusandrei/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/baicusandrei/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/baicusandrei/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] WWW and Non WWW Caching](https://wordpress.org/support/topic/www-and-non-www-caching/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [4 days, 3 hours ago](https://wordpress.org/support/topic/www-and-non-www-caching/#post-18908359) * Hello [@bobsled](https://wordpress.org/support/users/bobsled/), * That behavior is expected if the cache rule is only set for `example.com`. Since the plugin keeps that rule in sync, changing it manually to cover `www` wouldn’t be a good long-term fix. * The better approach is to redirect `www` to the apex so there’s only one canonical hostname in use. That keeps caching consistent, avoids duplicate behavior between` www` and non-`www`, and ensures the plugin-managed rule continues to work as intended. * So my personal recommendation is keeping the cache rule as-is and handling `www` via a redirect instead. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] X-WP-CF-Super-Cache-Disabled-Reason: Not a slashed URL](https://wordpress.org/support/topic/x-wp-cf-super-cache-disabled-reason-not-a-slashed-url-2/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [1 month ago](https://wordpress.org/support/topic/x-wp-cf-super-cache-disabled-reason-not-a-slashed-url-2/#post-18879530) * Hey [@glonojake](https://wordpress.org/support/users/glonojake/), * This is expected behavior. The header `X-WP-CF-Super-Cache-Disabled-Reason: Not a slashed URL` means the plugin skipped its disk cache for that request because the URL doesn’t have a trailing slash. However, if you look at the `cf-cache- status: HIT`, Cloudflare’s edge cache is serving the page just fine. So visitors are still getting a cached response at full speed. The disk cache and the Cloudflare edge cache are two separate layers. The plugin writes to disk as a fallback, but once Cloudflare has the page cached at the edge, it doesn’t need to hit the disk cache (or even your origin) at all. * **However, this could be contributing to your low hit rate (as per the other thread).** Looking at your URL structure (`/2026/threefer-thursday-hit-me-fred`), it appears your permalink structure doesn’t include a trailing slash. This means WordPress isn’t redirecting non-slashed URLs to their slashed equivalents, so traffic can hit both versions and create duplicate cache entries. * To fix this, go to **Settings > Permalinks** in WordPress and add a trailing slash to your permalink structure (e.g. `/%year%/%postname%/`), then click ** Save Changes**. WordPress will then automatically redirect non-slashed URLs to the slashed version, consolidating your cache entries and improving your hit rate. * All the best! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Edge Cache TTL?](https://wordpress.org/support/topic/edge-cache-ttl/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [1 month ago](https://wordpress.org/support/topic/edge-cache-ttl/#post-18879521) * Hey, [@glonojake](https://wordpress.org/support/users/glonojake/) * We don’t recommend editing the cache rule that Super Page Cache creates in Cloudflare, and you don’t need to set an Edge TTL manually. The rule is intentionally set to “Respect Origin TTL”, which means Cloudflare will use the TTL values sent by the plugin in the response headers (via s-maxage). This is the correct behavior and gives the plugin full control over caching duration. You can find the setting for the TTL under “Advanced” in the dashboard. By default is set to `0`, which means the TTL is actually 1 year. * As for the 5.57% hit rate – that’s likely not an Edge TTL issue. A few things that commonly affect hit rates: - **Exclusion rules** – logged-in users, WooCommerce cart/checkout pages, and certain cookies can cause many requests to bypass cache. It’s worth reviewing your exclusion settings to make sure nothing is being excluded unintentionally. - **Query strings** – URLs with query parameters (e.g. UTM tracking, search queries) are often treated as unique cache keys and won’t hit the cache. - **Low traffic / high URL diversity** – if your site has many unique URLs and relatively low traffic, the cache simply doesn’t get warmed up enough to show a high hit rate. - **Cache not yet warmed** – if the plugin or Cloudflare cache was recently cleared, the hit rate will be low until traffic rebuilds it. * I hope this helps! Have a great day ahead! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Action scheduler shows SPC issue?](https://wordpress.org/support/topic/action-scheduler-shows-spc-issue/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [2 months ago](https://wordpress.org/support/topic/action-scheduler-shows-spc-issue/#post-18854914) * Hello [@salutethepig](https://wordpress.org/support/users/salutethepig/), * You can change how many items are displayed on the page by opening the “Screen Options” panel at the top right. There you should be able to change the “Number of items per page” – I believe the maximum value is 999. This way you can bulk clear all, or most of them in one go. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Image Lazy Load is Not Working!](https://wordpress.org/support/topic/lazy-load-is-not-woorking/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [2 months, 4 weeks ago](https://wordpress.org/support/topic/lazy-load-is-not-woorking/#post-18827092) * [@mohsinworld](https://wordpress.org/support/users/mohsinworld/), * There’s not much we can help with without any additional details. Could you maybe provide some error logs from the website after enabling the option so we can see if anything is wrong there? Otherwise, can you check the browser console and the network tab in the inspector when loading the website with that option enabled so we can see if there’s anything we can spot that’s not working as expected? Thank you! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Compatibility issue between Super Page Cache (Disk Cache) and Fox Currency](https://wordpress.org/support/topic/compatibility-issue-between-super-page-cache-disk-cache-and-fox-currency/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [2 months, 4 weeks ago](https://wordpress.org/support/topic/compatibility-issue-between-super-page-cache-disk-cache-and-fox-currency/#post-18826876) * Hello [@sipakmarcin](https://wordpress.org/support/users/sipakmarcin/), * Sorry for the late reply! If the currency plugin is basing its currency switching on a cookie, then you could probably use the **Skip Caching for These Cookies** field to exclude that cookie from caching. The only issue would then be that when the cookie is set, the respective pages will bypass cache. * For YayCurrency you can add `yay_currency_` to the excluded cookies list. * Unfortunately there’s no way to serve both cached pages and make the switcher work for YayCurrency as there’s no branching cache based on cookies. It will simply Bypass cache when this cookie is set. * For the Fox Currency one, on my end, it seems that enabling its option for ** I am using cache plugin on my site** works just fine. You should just make sure you clear the cache after changing it. This option seems to update the currency from the frontend using AJAX. The old currency will flash for a bit but then change to the proper one. * I hope this helps! Have a great day! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Performance difference between 4.x and 5.x plugin](https://wordpress.org/support/topic/performance-difference-between-4-x-and-5-x-plugin/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [2 months, 4 weeks ago](https://wordpress.org/support/topic/performance-difference-between-4-x-and-5-x-plugin/#post-18826828) * Hello [@kpbryce132](https://wordpress.org/support/users/kpbryce132/), * From a performance perspective, version 5.x introduced several important improvements, not limited to: - **Can work independently of Cloudflare** – Caching is no longer Cloudflare- only, and the static cache works by itself if you want to use it, reliably on any hosting environment. - **Improved cache efficiency** – Smarter handling of query parameters, cookies, AJAX requests, and purge logic helps increase cache hit rates and reduce server load. - **Smarter lazy loading** – We’ve added a system that detects image placement making above-the-fold images load immediately while below-the-fold content loads lazily for faster perceived performance. - **Font optimization** – Added some option to combine and locally host Google Fonts to reduce external requests. - **Database optimization tools** – Clean up revisions, drafts, spam, and transients to keep the database lean. - **More reliable background processing** – Improved scheduling and cache preloading stability. * Overall, versions from 5.0.0 onwards deliver better cache reliability, improved efficiency, and broader compatibility compared to 4. You can see a full changelog [here](https://store.themeisle.com/changelog/Super%20Page%20Cache%20Pro). * The Pro version further enhances performance with advanced CSS and JavaScript optimization, including critical CSS generation for even better Core Web Vitals. I hope this sheds some light on the differences. Have a great day ahead! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] instantpage Still Load](https://wordpress.org/support/topic/instantpage-still-load/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [3 months ago](https://wordpress.org/support/topic/instantpage-still-load/#post-18817491) * Hello [@imtino](https://wordpress.org/support/users/imtino/), I remember fixing this bug and releasing the fix. I tried to reproducing it just now and the ** Auto prefetch URLs on mouse hover** setting is the one that affects this. Please make sure you have it off. When saving the settings, the SPC managed cache should be purged automatically. To be extra sure, purge the SPC Page Cache, Cloudflare cache or any other static cache that might be enabled on the website. If you have any additional caching plugins or systems, they might interfere, and that’s why this might not work. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Turn off instantpage and prefetch](https://wordpress.org/support/topic/turn-off-instantpage-and-prefetch/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [9 months, 2 weeks ago](https://wordpress.org/support/topic/turn-off-instantpage-and-prefetch/#post-18585825) * Hey [@imtino](https://wordpress.org/support/users/imtino/) [@cocoa1](https://wordpress.org/support/users/cocoa1/), * Thank you for reporting this! I’m sorry for the inconvenience. This seems to be a bug on our end. I’ve submitted a fix for it and it will be deployed in the next update. * All the best! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] wp-config.php location](https://wordpress.org/support/topic/wp-config-php-location/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [9 months, 2 weeks ago](https://wordpress.org/support/topic/wp-config-php-location/#post-18585693) * Hey [@telcy](https://wordpress.org/support/users/telcy/) [@abernitz](https://wordpress.org/support/users/abernitz/), * Thank you for reporting this! I have submitted a fix for this situation and we’ll release it in the next update. * All the best! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Cannot edit Cloudflare API Key](https://wordpress.org/support/topic/cannot-edit-cloudflare-api-key/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [10 months ago](https://wordpress.org/support/topic/cannot-edit-cloudflare-api-key/#post-18564407) * Hey [@gaiusjaugustus](https://wordpress.org/support/users/gaiusjaugustus/), Sorry for the slow follow-up. * We’ve released a patch update that should fix exactly this situation if you didn’t already try fixing it with the suggestion [@kushnamdev](https://wordpress.org/support/users/kushnamdev/) provided. * Have a great day! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Error: undefined can’t access property “innerText”…](https://wordpress.org/support/topic/error-undefined-cant-access-property-innertext/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [10 months ago](https://wordpress.org/support/topic/error-undefined-cant-access-property-innertext/#post-18563805) * Hello [@dccorp](https://wordpress.org/support/users/dccorp/), * Hey, thanks a lot for the detailed follow-up! It was really helpful to pinpoint the issue. From what you shared, it looks like your setup (Firefox with NoScript and tight script restrictions) is quite specific. While we totally get the need for that kind of configuration, it’s unfortunately a bit outside what we can realistically support across the board. * That said, I’m glad things are working in Chrome and that you found a workaround. * Let us know if anything else comes up within the usual use cases. * Have a great day! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] Cloudflare security rule blocking connection](https://wordpress.org/support/topic/cloudflare-security-rule-blocking-connection/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [10 months ago](https://wordpress.org/support/topic/cloudflare-security-rule-blocking-connection/#post-18563793) * Hello [@frenchomatic](https://wordpress.org/support/users/frenchomatic/), * Thank you for your message and for sharing your concerns regarding country-level blocking and the plugin’s behavior. I want to clarify that the plugin does not intentionally break or alter its behavior when Cloudflare security rules, such as country blocking, are active. * It does not contain any code or logic that would detect or respond to the presence of Cloudflare’s security rules, nor does it rely on any outbound requests whose failure would break the plugin’s functionality. * Could you please share more specific details about what’s going wrong? The more information you can provide about the issue, the better we’ll be able to assist you. * Have a great day ahead! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] New “Enable Cloudflare CDN & Caching” option](https://wordpress.org/support/topic/new-enable-cloudflare-cdn-caching-option/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [10 months ago](https://wordpress.org/support/topic/new-enable-cloudflare-cdn-caching-option/#post-18557857) * [@masvil](https://wordpress.org/support/users/masvil/), * > - In the same section, “Active Zone” instead of “Active domain” may be confusing > for some, regardless of being technically correct or not. > - On the “Advanced section”, consider replacing “upgrader process” with “update > process” for consistency with the option name containing “Updates” (not “ > Upgrades”). * In the latest release, we also accounted for the suggestions you gave us, so the descriptions have been reworded. Thank you for the valuable feedback! * Have a great day! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Super Page Cache – Cloudflare Cache, Page Speed & Core Web Vitals] New “Enable Cloudflare CDN & Caching” option](https://wordpress.org/support/topic/new-enable-cloudflare-cdn-caching-option/) * Plugin Support [Andrei Baicus](https://wordpress.org/support/users/baicusandrei/) * (@baicusandrei) * [10 months ago](https://wordpress.org/support/topic/new-enable-cloudflare-cdn-caching-option/#post-18557848) * Hey [@vellkan](https://wordpress.org/support/users/vellkan/)! * Thank you for the kind words, and sorry for the confusion! * You are right, both **Page Rules** and **Worker Routes** should be empty. The status of the toggle was an oversight from our part when we migrated settings to the new interface. Previously we accounted for the **Cache Rule** being saved when rendering it as enabled. * We just released an update that should migrate the setting properly from older versions, so the status of the toggle should be enabled now. * > But from today, with that new version of plugin – should we turn on that switch? > I saw that cache was working in Developer Tools, but before turning it on cache > rules were empty for that specific domain, I feel naked without that. * In short, if you enabled the switch and saved settings, the only thing that would have happened is that the plugin would’ve checked if the rule is already set, and updated its own value. Things would have worked the same as they already do, as the rule was properly set up. * In short, this was a rendering logic issue, not a functionality one. * I hope this helps clarify things for you! Please let us know if we can help with anything else. * Have a great day! Viewing 15 replies - 1 through 15 (of 113 total) 1 [2](https://wordpress.org/support/users/baicusandrei/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/baicusandrei/replies/page/3/?output_format=md)… [6](https://wordpress.org/support/users/baicusandrei/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/baicusandrei/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/baicusandrei/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/baicusandrei/replies/page/2/?output_format=md)