This guide is for Texo SuperCache 8.5.x. Need help? Submit a support ticket.
Quick Start
Build your site first. SuperCache is for when you are ready to go live (or want maximum speed) — not while you are still designing pages.
- Install and activate Texo SuperCache (on Texo hosting we install it when you ask — or it may already be included on WordPress MAX)
- Open SuperCache and run the Setup Wizard — click Start setup and let it finish
- Read the Setup complete summary, then click Continue to Advanced
- Use View as Visitor to check the live site; use the Advanced tabs only when you need them
The Wizard follows a safe order: server checks, page cache, Redis, images, soft optimisations, then Cloudflare if Texo already has your domain.
What Texo SuperCache Does
When a visitor lands on your WordPress site, WordPress normally has to load PHP, query the database, run plugins, and build the page on every request. On a busy site that can take seconds.
Texo SuperCache controls the page cache on the server. It pre-builds ready-to-serve copies of your pages, then serves those copies so visitors are not waiting for a full WordPress rebuild every time.
It also optimises what those pages load: leaner CSS and JavaScript, modern image formats, lazy-loading, and related Core Web Vitals improvements — without needing a pile of extra speed plugins.
Setup Wizard (first install)
From version 8.5, a new SuperCache install opens the Setup Wizard instead of the full Advanced menu. That prepares the server and warms a safe first cache before you touch advanced toggles.
Click Start setup. You will see progress and an activity log. You can close the tab during long steps — work continues on the server.
In order, the Wizard typically: checks the server; handles conflicting plugins; applies safe page-cache basics; enables Redis when available; optimises images and applies optimised URLs; warms the page cache; turns on soft optimisations (minify) and rebuilds; optionally connects Cloudflare.
Remove Unused CSS stays off until you choose it later under Optimization. After setup, click Continue to Advanced to open the full tab bar. Re-run the Wizard anytime from Troubleshooting.
View as Visitor
In the SuperCache header (and the WordPress admin bar) use View as Visitor. It opens your site as a logged-out visitor so you see the real cached page — not the admin view.
Always use this after preload, design changes, or optimisation toggles. The session lasts about 30 minutes.
Dashboard
Home base after Advanced is unlocked. Tab bar: Dashboard · Vitals · Optimization · Images · Caching · CDN · Database · Troubleshooting · Settings.
- Cache status — pages cached and queue depth
- Preload Cache — fills missing pages only; leaves good cache alone. Choose preload speed (Steady / Normal / Fast)
- Rebuild Cache — refreshes every page with current settings, one URL at a time (other pages stay cached until their turn)
- Purge Page Cache & Preload — wipes local HTML page cache (keeps optimised CSS/JS files), purges Cloudflare when connected, then full preload. Use after big design / theme / plugin changes
- Core Web Vitals — summary cards with a link to the full Vitals tab
Vitals
Full Core Web Vitals analytics from real visitors (last 30 days). Open this when speed "feels off" after a change. Tracking can be toggled under Settings.
Optimization
Page-level optimisations once basic page cache works. Safe Wizard defaults leave heavy options off until you are ready.
- CSS & JavaScript — minify; Remove Unused CSS (turn on last); delay / third-party script controls; self-host external CSS/JS
- Images, Videos & Iframes — lazy-load, properly size images, lightweight YouTube, self-host Gravatars (bulk media conversion is on the Images tab)
- Fonts — preload, self-host Google Fonts, system-font fallback
- Rendering — lazy-render below-the-fold sections
- Remove WordPress Bloat — optional switches for block CSS, emojis, embeds, and similar
- WooCommerce (shops) — optional non-store asset / cart-fragment controls when Woo is active
- Script Manager — scan a URL and disable scripts/styles only where they are not needed
Change one option at a time, then View as Visitor. If something breaks, undo that toggle.
Images
Image library tools now have their own tab (they used to sit with page optimisations).
- Optimize Images — run once after setup; button locks when complete
- Image format / compression — WebP, AVIF, or original; lossless or lossy
- Auto-optimize new uploads — convert as media is uploaded
- Apply optimised URLs — rewrite content to point at optimised files after a bulk run
- Danger Zone — restore originals or permanently delete originals (only when you are sure)
Do not re-run bulk Optimize "just to be sure" — it mainly wastes time and re-warms the page cache.
Caching
- Basic Caching — preload links on hover, separate mobile cache, cache for logged-in roles
- Advanced Caching — exclude paths, query-string variants, cookie bypass, Gravity Forms source URL option
- Object cache — Redis / Memcached status when available on the host
- Danger Zone — Purge entire cache — deletes all SuperCache files (including optimised CSS/JS assets) without starting preload; purges Cloudflare when connected. Only use if you will Preload or Purge Page Cache & Preload immediately after
CDN (Cloudflare, Security & DNS)
There is no separate Security or DNS tab in the Advanced menu. Those panels live on CDN once Cloudflare is connected.
- Enable CDN — turn on after origin preload/rebuild is healthy
- Cloudflare credentials — often pre-filled on Texo-managed hosting; connect with API token or global key + zone
- Enable Page Caching — edge caching of finished pages (after origin is ready)
- Cloudflare tools — purge edge, temporary Development Mode, emergency controls
- Security — Bot Fight Mode and WAF rules (Texo suggested + custom). Free plans have limited custom rule slots
- DNS — list, add, edit, and bulk-delete zone records without leaving WordPress
No Cloudflare? Skip this tab. Your site still benefits from SuperCache on the server.
Database
- Backup — download a database backup before cleanup
- Cleanup tools — revisions, expired transients, spam, and similar (manual or scheduled)
- Autoload — large options that slow every page load
Always take a backup first. Prefer small cleanups over aggressive one-click "fix everything."
Troubleshooting
- Re-run Setup Wizard — start guided setup again
- Page-cache-only preload — warm plain HTML without the optimisation pipeline (useful when diagnosing layout issues)
- Regenerate Elementor CSS — rebuild Elementor kit/page CSS on disk, then purge page cache (Elementor sites)
- Shortcuts to purge/preload when you need them outside the Dashboard
Settings
- Preload Scope — which content types are included when preloading (posts, pages, products, taxonomies, authors)
- Core Web Vitals Tracking — collect real-user metrics for Dashboard/Vitals
- Import / export — move SuperCache settings between sites
- Plugin updates — check for SuperCache updates from here (or Plugins)
- Debug log / Recommendations — when present: temporary logging and system cron tips
After updates & site changes
SuperCache already handles a lot of this — you only need a full clear after bigger changes.
Do this
Builder CSS first → Purge Page Cache & Preload → View as Visitor → Cloudflare only if still stale.
- Finish your edits or updates
- If you use Elementor: regenerate its CSS (Elementor → Tools, or SuperCache → Troubleshooting → Regenerate Elementor CSS)
- Dashboard → Purge Page Cache & Preload
- Check key pages with View as Visitor
- Only if the world still sees an old page: CDN → purge Cloudflare
Quick answers
| Situation | What to do |
|---|---|
| Normal page or post edit | Usually nothing — SuperCache updates that page for you. Optional: Preload Cache if you added many new URLs. |
| Plugin or theme update | Yes — Purge Page Cache & Preload when the front end can change. Security-only updates: spot-check with View as Visitor. |
| Theme switch or big design change | Purge Page Cache & Preload (Elementor: regenerate CSS first). |
| Elementor / layout wrong for guests | Regenerate Elementor CSS → Purge Page Cache & Preload → View as Visitor. Cloudflare last if still stale. |
| Elementor cache, then Texo? | Yes — Elementor first, then Texo. |
Which button?
| Button | Where | Use when |
|---|---|---|
| Preload Cache | Dashboard | Fill missing pages only — new content, light changes. |
| Rebuild Cache | Dashboard | Refresh every page with current settings without a full cold wipe first. |
| Purge Page Cache & Preload | Dashboard | Wipe HTML page cache and rebuild after updates, theme, or design changes. Also refreshes Cloudflare when connected. |
| Purge entire cache | Caching → Danger Zone | Rare. Deletes all cache files without rebuilding — always Preload right after. |
| Purge Cloudflare | CDN | Edge still old after origin is correct. |
| Regenerate Elementor CSS | Troubleshooting | Unstyled layout / missing Elementor styles. |
| View as Visitor | Header / admin bar | Always — check the real guest page. |
What SuperCache already does
| You do this… | SuperCache usually… |
|---|---|
| Publish or update a page/post | Refreshes that URL (and related archives) for you |
| Save Elementor templates / Theme Builder | Clears the site page cache and re-warms home (and shop if WooCommerce) |
| Activate or deactivate a plugin | Clears the page cache automatically |
| Update plugin/theme files (stay active) | Does not always full-clear — use Purge Page Cache & Preload if the front end can change |
Avoid
- Running another full-page cache plugin next to SuperCache
- Judging the live site only while logged in as admin
- Purging Cloudflare first for Elementor/layout issues — fix Elementor + SuperCache first
- Using Danger Zone purge without Preload afterward
Frequently Asked Questions
How long does preload take? Depends on page count and whether heavy optimisations (like Remove Unused CSS) are on. Hundreds of pages can take a while — let it finish.
Will the site be slow during preload? Only pages not yet cached may be slower until the runner reaches them. Already-cached pages stay fast.
After a theme or big design change? Use Purge Page Cache & Preload. See After updates.
After a plugin update? Purge Page Cache & Preload when the front end can change. Check with View as Visitor.
Elementor first, then Texo? Yes. Regenerate Elementor CSS, then Purge Page Cache & Preload.
Where did Security / DNS go? On the CDN tab (after Cloudflare is connected).
Where did Image Optimizer go? Its own Images tab.
After a new post? Preload Cache is enough (fills gaps).
Can I use another page-cache plugin with SuperCache? No — SuperCache should control the page cache.
Stuck overnight? Background tasks need reliable WP-Cron / server cron. Open a ticket if preload or image optim never finishes.
What’s Changed Recently
Guide layout pass for SuperCache 8.5.x Advanced UI:
- New tabs: Vitals, Images, Troubleshooting
- CDN now holds Cloudflare connection plus Security (WAF) and DNS (no separate Security/DNS menu items)
- Dashboard buttons: Preload Cache, Rebuild Cache, Purge Page Cache & Preload
- Settings includes Preload Scope and Vitals tracking
- Fresh unredacted screenshots from lab install v8.5.14
Questions? Submit a support ticket.