What actually goes wrong
Three failure modes, specific to this kind of site. Everything below is aimed at them.
Every page carries every widget
Builders enqueue their full CSS and JS library site-wide. A simple landing page ships hundreds of kilobytes of styles for widgets it never uses.
Render-blocking assets delay first paint
Stylesheets and scripts loaded up front push your Largest Contentful Paint back — visitors stare at a blank canvas while the builder’s runtime arrives.
"Optimizing" usually breaks the design
Aggressive minification and blind CSS removal are how sliders stop sliding. Most people turn optimization off after the first breakage.
How xSpeed Cache fixes builder bloat
Ship only the CSS and JS each page actually uses — and never break the layout doing it.
Remove unused CSS
Each page keeps only the styles it actually renders. Builder sites routinely drop the large majority of their CSS payload.
Unused CSS guideCritical CSS generation
Above-the-fold styles are inlined so the page paints immediately; the rest loads asynchronously without blocking render.
Critical CSS guideDefer & delay JavaScript
Builder runtimes, sliders, and tracking scripts wait until they’re needed — or until the visitor interacts — instead of blocking first paint.
JS defer/delay guideSafe minify with automatic fallback
Minify and combine with a fallback that auto-skips any file that could break the page. Optimization that never costs you a working slider.
Minification guidePage cache for the rendered result
However heavy the builder is in the editor, visitors get the finished page as static HTML in 5–15ms — the builder’s PHP never runs for them.
Enable page cacheSelf-healing cache
If an optimization conflicts with a plugin or theme update, xSpeed detects and resolves it automatically instead of leaving a broken page cached.
How self-healing works6 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.
Get an Elementor site out of the red
The design is beautiful; the mobile score is 52. Builders ship every widget’s CSS to every page.
WHEN
PageSpeed flags "reduce unused CSS" and "eliminate render-blocking resources" — the builder-site signature.
SETUP
Enable Remove Unused CSS and Critical CSS; each page keeps only the styles it renders and paints immediately.
Optimize without touching the design
You were asked to make it fast, not to rebuild it — and most speed advice starts with "use fewer widgets".
WHEN
The client signs off on the design as-is.
SETUP
Everything operates on the builder’s output — CSS, JS, images, fonts — and caches the rendered page. The design file never changes.
Make ad landing pages instant
You pay per click, then greet visitors with a spinner while tracking scripts load.
WHEN
Paid campaigns point at builder-made landing pages.
SETUP
Delay third-party scripts until interaction, inline critical CSS, and let the page cache serve the landing page in milliseconds.
Recover from a broken optimizer
The last optimization plugin broke the slider, so optimization has been off ever since.
WHEN
You have been burned before and trust is the blocker.
SETUP
Safe-minify auto-skips anything that could break, and self-healing cache resolves conflicts instead of caching a broken page.
Survive a theme or builder update
Updates re-shuffle asset handles, and yesterday’s hand-tuned exclusion list silently stops matching.
WHEN
A major theme, builder, or plugin update ships.
SETUP
Self-healing cache detects the conflict, resolves it, and re-caches — no 2am rollback.
Green Core Web Vitals by asking
You know the score needs to be green; you do not know which of forty toggles gets it there.
WHEN
The Vitals report shows red and the deadline is real.
SETUP
Connect your AI via MCP and ask it to get the site green without breaking the design — it benchmarks, tunes, and re-tests.
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 builder de-bloat
My site is built with Elementor. Using xSpeed, benchmark it, then remove unused CSS, generate critical CSS, and defer or delay JavaScript — but do not break the design: use safe-minify and verify the page still renders correctly. Show me the before/after scores and CSS payload.
The ad landing page
Using xSpeed, make [landing page URL] as fast as possible for paid traffic: delay all third-party and tracking scripts until interaction, inline the critical CSS, cache the page, and warm it. Report its LCP afterwards.
After a theme update
I just updated my theme and builder plugins. Using xSpeed, check for any optimization conflicts or broken assets, let self-healing resolve what it can, purge and re-warm the cache, and re-run the benchmark to confirm nothing regressed.
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 › This Elementor site scores 52 on mobile. Get it green without breaking the design.
xspeed · run_benchmark → 52 · LCP 4.6s · 610KB CSS
xspeed · remove unused CSS → 88KB kept
xspeed · critical CSS inlined · JS delayed
xspeed · run_benchmark → 94 · LCP 1.2s
Done — same design, a third of the weight, green Core Web Vitals.
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.
Plumbers & home services
The 2am burst pipe doesn’t wait for your slider to load.
Read the storyRestaurants & cafés
Hungry people check the menu. Once..
Read the storyReal estate agencies
Buyers scroll forty listings. Slow ones get skipped.
Read the storyLaw firms
Clients judge the firm by the first three seconds.
Read the storyDental & medical clinics
Patients book where the booking button loads.
Read the storyGyms & fitness studios
January brings the traffic. Don’t make it wait.
Read the storyPhotographers
Your portfolio is stunning. If it ever loads.
Read the storyWedding & event planners
You’re shortlisted at midnight, on a couch, on a phone.
Read the storyHotels & B&Bs
Slow sites pay OTA commissions.
Read the storyNonprofits & churches
The appeal went out. Now the site has to hold.
Read the storySalons & spas
From Instagram bio to booked, before the scroll resumes.
Read the storyAuto repair shops
The car died. The search is happening right now.
Read the storyBuilders & contractors
Your best argument is a photo of the finished kitchen. Let them see it.
Read the storyVeterinary clinics
Nobody visits a vet’s website calmly. Answer in one screen.
Read the storyTherapists & counsellors
Someone is deciding whether to send that message. Do not make them wait.
Read the storyAccountants & bookkeepers
A year of traffic arrives in three weeks. Be ready for it.
Read the storyInsurance agencies
You paid for that click. Don’t lose it to a spinner.
Read the storyMusicians & bands
You announce the tour, and everyone arrives at once.
Read the storyFrequently asked questions
Keep reading
← Previous playbook
Blogs & publishers
Articles served as static HTML, the archive prewarmed on schedule, and auto-purge on publish — first impressions at 5–15ms.
Next playbook →
Membership & LMS
Object caching for the logged-in side, full-page speed for the public side, and precise rules for the line between them.