Learn step-by-step how to configure Greeny Host Global Edge Cache and server-side web optimisations to skyrocket your Google PageSpeed Insights score and delight both users and AI search tools.
Why Speed Matters for SEO & AI
Fast-loading websites rank higher in Google’s search results and are more likely to be featured in AI overviews (Google’s AI Overviews, ChatGPT, Perplexity). Core Web Vitals—First Contentful Paint (FCP), Largest Contentful Paint (LCP), Total Blocking Time (TBT), and Cumulative Layout Shift (CLS)—are direct ranking signals. Each 100 ms improvement in load time can boost conversions by up to 8 % and lift your PageSpeed Insights score by 10–20 points.
Step 1: Configure Greeny Host Global Edge Cache
- Activate Dynamic Cache
- In your Global Edge Caching settings, turn on Dynamic Cache.
- Ensure your application emits
Cache-Control: public, max-age=...headers on pages you want cached (e.g., homepage, category pages).
- Set TTLs for Static Assets Asset TypeRecommended TTLRationaleImages, CSS, JS30 daysBalances freshness with repeat-visit performanceVersioned Bundles365 daysFingerprinted files can be cached long-term
- Purge & Verify
- After any design or file update, click Purge Cache to force edge servers to fetch the latest versions.
- Check the
X-CDN-Cache-Statusresponse header to confirm a “HIT.”
🔑 Pro Tip: Never cache pages that set cookies (e.g., cart, checkout). Use short TTLs or bypass the CDN for those dynamic endpoints.
Step 2: Apply HTML Optimisations
Reducing HTML payload size and eliminating render-blockers speeds up FCP and LCP.
- Collapse Whitespace
- Removes extra spaces and line breaks.
- Remove Comments & Quotes
- Strips HTML comments and unnecessary quotation marks.
- Trim URLs
- Converts absolute URLs to relative where safe.
- Pre-Resolve DNS
- Adds
<link rel="dns-prefetch" href="//example-cdn.com">hints to resolve third-party domains early.
- Adds
All four filters are Low-Risk and can be enabled in one click on the server side.
Step 3: Tweak CSS Delivery
Proper CSS handling prevents render-blocking and boosts FCP/LCP.
- Move CSS to
<head>- Ensures all critical styles are parsed before body content.
- Combine & Minify CSS
- Bundles multiple files into one, removing comments/whitespace.
- Prioritize Critical CSS (High-Risk)
- Auto‐extracts above-the-fold rules and inlines them into your HTML.
🔑 Pro Tip: Test “Prioritize Critical CSS” on a staging site—high-risk filters may require minor theme tweaks.
Step 4: Optimize JavaScript Loading
Defer or inline scripts to cut Total Blocking Time.
- Minify JavaScript
- Strips comments/whitespace.
- Combine JavaScript
- Reduces HTTP requests by merging files.
- Defer JavaScript (High-Risk)
- Adds
deferattributes so scripts load after HTML parsing.
- Adds
- Move CSS Above Scripts
- Prevents CSS render-blockers when JS is parsing.
Enable Minify, Combine, and Move CSS Above Scripts first (Low/Medium-Risk). Then validate before enabling Defer.
Step 5: Supercharge Image Delivery
Efficient image handling drastically improves LCP.
- Insert Image Dimensions
- Adds
widthandheightattributes to prevent layout shifts.
- Adds
- Lazyload Images
- Defers off-screen images until they enter the viewport.
- Convert to WebP
- Serves next-gen formats to supported browsers.
- Responsive Images (Medium-Risk)
- Adds
srcsetfor multiple resolutions.
- Adds
🔑 Pro Tip: Use Recompress Images to strip metadata and recompress JPEG/PNG for extra KB savings.
Step 6: Cache Busting & Versioning
Prevent stale assets without shortening TTLs.
- Filename Versioning: cssCopyEdit
main.20250803.css app.abcdef1234.js - Query Strings: bashCopyEdit
<link href="style.css?v=20250803" rel="stylesheet"> - Run Purge Cache immediately after deployment if you cannot version filenames.
Step 7: Validate with PageSpeed Insights
- Run a Lighthouse Audit on both Mobile and Desktop.
- Focus on Core Metrics:
- First Contentful Paint (FCP)
- Largest Contentful Paint (LCP)
- Total Blocking Time (TBT)
- Cumulative Layout Shift (CLS)
- Iterate:
- Re-enable one High-Risk filter at a time.
- Purge cache and retest.
Aim for Performance ≥ 90, Accessibility ≥ 90, Best Practices ≥ 90, and SEO ≥ 90.
FAQ
Q: How often should I purge the cache?
A: Purge after every major deployment or theme change. For content updates (e.g., blog posts), rely on versioned URLs.
Q: Will “Prioritize Critical CSS” break my design?
A: It can if your theme relies on global CSS injection. Always test in staging and adjust the critical-CSS selector whitelist if needed.
Q: Do I need a plugin for versioning?
A: No—most build tools (Webpack, Gulp) can append content hashes automatically. For simpler WordPress setups, plugins like WP Rocket handle cache-busting on file changes.
Conclusion
By following this step-by-step guide—configuring Greeny Host Global Edge Cache, activating targeted server-side filters, and employing cache-busting best practices—you’ll unlock top-tier Google PageSpeed Insights scores, faster Core Web Vitals, and improved SEO visibility. Plus, your content will be formatted and structured to be readily consumed by Google’s AI Overviews, ChatGPT, Perplexity, and Rank Math’s Content AI module—maximizing your reach in both human and AI-driven search.
Ready to see your site fly? Enable these optimisations today and watch your metrics soar!