What actually goes wrong
Three failure modes, specific to this kind of site. Everything below is aimed at them.
Search traffic lands on cold pages
Readers arrive from Google spread across your whole archive — not just the homepage. Uncached long-tail posts are slow posts, and slow posts rank worse.
Fonts and images block the first read
Invisible text waiting on a webfont, images shoving the layout around — the classic content-site experience, and exactly what Core Web Vitals punishes.
Years of revisions drag every query
A decade of drafts, revisions, and spam comments makes the database bigger and every uncached request slower.
How xSpeed Cache speeds up content sites
The whole archive cached, warmed, and rebuilt on publish — automatically.
Full-page cache with auto-purge on publish
Articles serve as static HTML in 5–15ms. Publish or update a post and its cache — plus the home page and archives it appears on — rebuilds automatically.
Enable page cacheScheduled cache prewarming
The preloader walks your sitemap on a schedule, so even deep-archive posts serve from cache when search traffic finds them.
Prewarming guideFont optimization
font-display swap plus preloads for above-the-fold fonts: text renders instantly instead of flashing invisible while a webfont downloads.
Font guideLazy load with layout-shift fix
Images, iframes, and embeds load as readers scroll — with the layout shift lazy-loading usually causes fixed automatically.
Lazy-load guideFeed, search & 404 caching
RSS readers, site search, and bot-hammered 404s all hit cache instead of PHP — the long tail of requests most cache plugins ignore.
Feed cache guideDatabase cleanup on a schedule
Revisions, transients, and spam swept automatically, with OPTIMIZE TABLE included — an archive that grows without slowing down.
Cleanup guide6 ways people put xSpeed to work
Each one shows when it applies and what to set up — or what to ask your AI for. Filter by role in the sidebar, or use the chips below.
Ride out a viral post
The best day of your blog’s life is also the day it is most likely to fall over.
WHEN
A post takes off on social or hits a big aggregator and traffic multiplies within the hour.
SETUP
Page cache absorbs the spike as static HTML; start the preloader so the rest of the site stays warm while everyone clicks around.
Keep the deep archive search-fast
Search traffic lands across ten years of posts, not on your homepage — and the long tail is where cold caches live.
WHEN
Always — scheduled, not triggered.
SETUP
Scheduled cache prewarming walks the sitemap so even the 2016 archive serves from cache when Google sends someone.
Stop the invisible-text flash
Readers see a blank paragraph while your webfont downloads — the classic content-site first impression.
WHEN
Your theme uses webfonts (it does).
SETUP
Font optimization applies font-display swap and preloads above-the-fold fonts; text renders instantly in a fallback, then swaps.
Embed videos without the weight
One YouTube embed adds more page weight than the article it sits in.
WHEN
Posts embed YouTube, podcasts, or social content.
SETUP
Click-to-play facades load a thumbnail instead of the player; the real embed arrives only when a reader clicks.
Tame the bot traffic you never see
Feed readers, crawlers, and 404-probing bots quietly consume real server capacity.
WHEN
Server load looks high relative to human traffic.
SETUP
Feed cache, search-results cache, and 404-page cache put the whole non-human long tail on static responses.
Clean up a decade of revisions
Every draft you ever saved is still in the database, slowing every query a reader triggers.
WHEN
The site is years old and has never had a database cleanup.
SETUP
One scheduled cleanup sweeps revisions, transients, and spam, and runs OPTIMIZE TABLE — then keeps doing it weekly.
No scenarios under that role yet — pick “All” to see every one.
The exact prompts to use
Connect via xSpeed MCP or the Hub, then paste any of these into Claude or ChatGPT.
The archive warm-up
Using xSpeed, enable page caching if it isn’t already on, start the preloader across my full sitemap, and schedule prewarming so the whole archive stays cached. Then tell me my cache hit rate.
The reading-experience pass
Using xSpeed, optimize my fonts with swap and preloads, lazy-load images and video embeds with layout-shift protection, and turn YouTube embeds into click-to-play facades. Re-run the benchmark and report LCP and CLS.
Spring cleaning
Using xSpeed, clean up my database — old revisions, expired transients, spam — run OPTIMIZE TABLE, and schedule this cleanup weekly. Tell me how much space was recovered.
Or just ask your AI
Every xSpeed Cache install speaks MCP. Connect Claude or ChatGPT once — directly or through xSpeed Hub — and everything on this page becomes something you ask for instead of something you configure.
you › Traffic doubled after a viral post. Keep the whole site fast.
xspeed · get_cache_status → 71% hit rate
xspeed · start_preloader → warming full sitemap
xspeed · update_settings → fonts preloaded, embeds lazy
xspeed · run_benchmark → 100 · LCP 0.8s
Done — hit rate at 98%, the spike is landing on static HTML.
See the story for your business
Each one is a real scenario — the moment speed bites, the fix, and the exact prompt to hand your AI.
Local news & magazines
The story broke. So did the server.
Read the storyFood bloggers
They came for the recipe. Serve it hot.
Read the storyTravel bloggers
Your readers are on hostel Wi-Fi. Meet them there.
Read the storySchools & universities
Results day is not the day to find out you are slow.
Read the storyPodcasters & audio shows
Two hundred episodes, and a feed that never sleeps.
Read the storyFrequently asked questions
Keep reading
← Previous playbook
Agencies & freelancers
Fleet dashboard, shareable settings profiles, roles for your team, white-label branding — client performance as a product, not a chore.
Next playbook →
Elementor & page builders
Remove unused CSS, inline the critical styles, delay the scripts — same design, a fraction of the weight, zero broken sliders.