Table of Contents
How do I enable caching to speed up my CBSplit site?
Draft. No cache switch is documented. The public wiki does not describe a page cache, an object cache, a TTL, or a clear-cache button. Do not add those steps from another CMS. CBSplit is described as a lightweight, fast alternative to WordPress, but that sentence is not a configuration guide. Until a control is confirmed in the admin, you cannot “enable caching” from this article.
Before You Begin
Log in to the admin. The documented top-menu area to inspect first is Options. The written Options guide covers Production (ClickBank keys) and the Meta tab. A Google services screenshot is also on that page. A cache tab is not mentioned.
You also need to know which layout the slow page uses. Phone HTML may come from the layout mobile tab, which is a different body, not a cached copy of the desktop body.
Verification required: look through Options and any site or system screen for the word “cache”. If it is absent, stop. Do not create a plugin or edit a server file. No plugin installer and no FTP access are documented. Assets states there is no FTP.
Step-by-Step Instructions
- Open Options from the admin top menu and review the tabs that are actually on screen.
- If you find a cache control, stop and record its exact label, what it stores, and how it is cleared before you turn it on. Those facts are verification required. This article will not invent them.
- If you do not find a cache control, leave the site as it is. Enabling a cache you cannot flush is a good way to serve a stale sales page.
- For large images, the documented upload path is still Content > Assets. Putting the file in Assets does not, by itself, enable a CDN cache.
- The hotlinking article talks about loading images from outside CBSplit to reduce bandwidth. It also tells you to enable “Hotlinking Protection” under an
/appsSetup tab, and it says DOSarrest blocks that feature. Those instructions conflict. Verification required: do not use that page as a cache setup. Ask whoever runs the site which image host is actually in use. - A snippet inserted at the head or the bottom of every page runs on those requests. The Snippets article warns that site-wide third-party pixels slow pages and leak traffic data. Remove or gate pixels with snippet logic when a page feels slow. That is a documented performance issue, and it is not a cache.
- Mobile and desktop can be different HTML. Compare the correct layout before you call the phone view “stale cache.”
Example
The offer page feels slow on the first click and on later clicks. Options has Production, Meta, and the Google services area, and no cache control.
You do not flip a cache on. You check the page source for a site-wide pixel snippet, and you confirm the product image is the Assets file you expect rather than a multi-megabyte original. You load the page once in a private window and once again. Similar speed does not prove a CBSplit cache, and a faster second load does not prove one either. The browser has its own cache. CBSplit does not document a response header that separates the two.
Only after someone with product access names a real control should that control be turned on, and only on a staging host if the product has one. A staging switch is verification required.
How to Verify
- Record whether any admin screen contains a cache setting. “Not present in Options, Assets, or the page editor” is a valid result.
- If a control is found later, verify it by a documented flush. There is no documented flush in the wiki today, so a test procedure cannot be copied from here.
- View the offer URL with the browser cache disabled when you are judging the page itself. A normal reload can show a browser-cached stylesheet or image.
- Confirm phone and desktop separately when a mobile layout exists. Different HTML is not a stale cache entry.
- After you remove a heavy snippet, reload the public page and confirm the script is gone from the source. That verifies the snippet change, not a cache setting.
Troubleshooting
A cleared browser cache did not change the page
The HTML is what CBSplit is publishing now. Look at the page, the layout, and snippet insertions. Do not keep clearing a cache the product docs do not mention.
The phone page looks like an old desktop page
Check the mobile tab before you blame cache. An empty tab loads the default layout. A filled tab loads only what is in that tab.
Visitors still see yesterday's headline
Possible causes that are documented: the wrong page or variation is live, a redirect still points at the old URL, or the editor is looking at the admin while the public URL is another page. A hidden cache is possible and unconfirmed. Verification required: compare the public source with the page editor before you escalate.
Turning on Cloudflare changed the page
Cloudflare is mentioned only on the conflicting hotlinking page, as an alternative when DOSarrest is in front of the site. It is not documented as CBSplit's cache button. Purge rules belong to that Cloudflare account, not to a CBSplit menu this wiki describes.
Assets 404 after a file replace
The page may point at the old file name. CBSplit does not document an asset cache-busting query string. Update the URL used in the layout. Verification required: whether the file manager keeps the same address when a file is replaced.
Frequently Asked Questions
Which menu enables caching?
None is documented. Check Options and stop if the control is not there.
Does CBSplit cache HTML, images, or both?
Unknown. The wiki does not say. Do not pick one in a runbook.
Will a cache hide A/B test changes?
Not documented. Getting Started says tests can run on autopilot or be judged manually, and a winner can become the live primary page. It never mentions bypassing a cache. Verification required: if a cache exists, confirm that test assignments are not stored as one page for every visitor.
How do I clear the cache?
No clear-cache button is documented. Do not invent one.
