63of 100
48of 100
www.eccouncil.org
DLevel 3 · Average
FLevel 2 · Slow
WordPressNo cache pluginMCP signal presentCloudflare
126msTTFB
61Lighthouse desktop · graded
32Lighthouse mobile
1.4sLCP
0.15CLS
brCompression
HITCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 48 (F) —
Real visitors · Chrome UX Report · desktop · this page ·
fails Core Web Vitals
3.5sLCP (p75)
211msINP (p75)
0.02CLS (p75)
This Lighthouse run passes LCP, but real desktop Chrome users wait 3.5s for the largest paint. Google ranks on the real-user number.
Why is this different from the score in my browser?
The graded score is the desktop run. Lighthouse 13.5.0 runs at Google through the PageSpeed Insights API on a desktop profile with no CPU or network throttling — close to what Chrome DevTools on a laptop, GTmetrix's default test and the PageSpeed API (which defaults to desktop) all measure, so this is the number you should be able to reproduce: run it yourself on PageSpeed Insights.
Google ranks on mobile. That run happens too, on an emulated mid-range Android with a 4× CPU slowdown and a throttled connection, and the same page routinely scores 30–50 points lower there. Neither number is wrong — they are different tests. On this page the mobile run scored 48 (F) against 63 (D) here — to see every check graded on that run.
Lighthouse also varies a few points run to run on the same URL. Treat a trend across several scans as the signal, never a single digit.
Lab data: Google PageSpeed Insights (Lighthouse, desktop). Server probes (TTFB, compression, cache, headers) are measured separately from Vilnius, Lithuania (EU).
126msTTFB
61Lighthouse desktop
32Lighthouse mobile · graded
12.3sLCP
0.02CLS
brCompression
HITCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 63 (D) —
Real visitors · Chrome UX Report · mobile · this page ·
fails Core Web Vitals
4.7sLCP (p75)
1.2sINP (p75)
0.01CLS (p75)
Why is this different from the score in my browser?
This view grades the mobile run. Lighthouse 13.5.0 runs at Google through the PageSpeed Insights API on an emulated mid-range Android with a 4× CPU slowdown and a throttled connection. Chrome DevTools on your own machine, on the Desktop preset, applies almost none of that, and the same page routinely scores 30–50 points higher there. Neither number is wrong — they are different tests.
Mobile is what Google ranks on, so this is the number that affects your
search performance. On this page the desktop run scored 63 (D) against
48 (F) here —
to see every check graded on that run. To reproduce it, open the same run on PageSpeed Insights,
or pass strategy=mobile to the PageSpeed API — it defaults to desktop.
Lighthouse also varies a few points run to run on the same URL. Treat a trend across several scans as the signal, never a single digit.
Lab data: Google PageSpeed Insights (Lighthouse, mobile). Server probes (TTFB, compression, cache, headers) are measured separately from Vilnius, Lithuania (EU).
Lab performance (Lighthouse)D64
2/5 checks passed · 25.5/40 pts Jump to section ↓
Server response & cachingA92
5/6 checks passed · 27.5/30 pts Jump to section ↓
Asset optimizationF40
2/5 checks passed · 8/20 pts Jump to section ↓
Platform & xSpeed readinessF20
1/3 checks passed · 2/10 pts Jump to section ↓
Lab performance (Lighthouse)F27
1/5 checks passed · 10.8/40 pts Jump to section ↓
Server response & cachingB83
5/6 checks passed · 25/30 pts Jump to section ↓
Asset optimizationF50
2/5 checks passed · 10/20 pts Jump to section ↓
Platform & xSpeed readinessF20
1/3 checks passed · 2/10 pts Jump to section ↓
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
This is WordPress — the fixes below are one plugin away
- ✓WordPressDetected
- →xSpeed Cache installedFree on wordpress.org — the setup wizard turns most of this report green.
- ✓MCP signal presentThe report indicates MCP availability. This does not verify client authentication or control.
- →xSpeed Hub signalOptional: review Hub configuration and confirm authorized site membership at app.xspeedcache.com.
9 of these checks map to an xSpeed feature. Install the free xSpeed Cache plugin, connect its built-in MCP server, and your AI assistant can apply every fix and re-verify. If your AI already has access to the site (WP-CLI, SSH or hosting MCP), paste this:
My WordPress site www.eccouncil.org scored 63/100 on xSpeed Scan (https://xspeedcache.com/scan/r/www-eccouncil-org-7fab03ccef). Install and activate the free xSpeed Cache plugin from wordpress.org/plugins/xspeed, run "wp xspeed mcp connect" and give me the MCP URL to paste into my AI client. Then read the failing checks from https://xspeedcache.com/scan/r/www-eccouncil-org-7fab03ccef.md and apply the fixes: enable page caching, compression, minification and lazy loading, warm the cache, and re-scan at https://xspeedcache.com/scan to confirm the score improved.Hosting is the other half.
xSpeed makes any host faster, but a cache is only as fast as the server behind a MISS.
xCloud — managed hosting from the team behind xSpeed — gives the cache an origin tuned for it, with agent/MCP access built in and bring-your-own-server pricing.
Explore xCloud.host →
Run this scan without the form
Plug xSpeed Scan into your agent stack, or test any site from a chat.
Connect this scanner to your AI assistant
Free. No API key, no sign-up. Scan any public site and get the same graded report as this one, with the fix for every failing check.
Endpoint
https://xspeedcache.com/scan/mcpClaude Code — one command
claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcpClaude Desktop, Cursor, or any MCP client — add to your config
{
"mcpServers": {
"xspeed-scan": {
"type": "http",
"url": "https://xspeedcache.com/scan/mcp"
}
}
}run_speed_scanScan any public URL and return this whole graded report.get_speed_scanRead a scan already run, by its id.
D
64/100
Lab performance (Lighthouse)
2/5 checks passed · 25.5/40 pts earned
Partial
Lighthouse performance score (desktop) 11/18 pts
61/100 (Lighthouse 13.5.0, desktop)
The composite Lighthouse score — every fix below moves it.
xSpeed Free
AI Optimize
AI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 1.4s
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Partial
Cumulative Layout Shift ≤ 0.1 2.5/5 pts
CLS 0.149
Reserve space for images/embeds so the page does not jump as it loads.
xSpeed Free
Lazy Load — CLS fix (adds width/height)
AI prompt
Using my site's xSpeed MCP connection: enable lazy loading with the CLS fix so images reserve their space, then re-test CLS.Guidelines: web.dev — Cumulative Layout Shift
Fail
Total Blocking Time ≤ 200ms 0/5 pts
TBT 604ms
Less JavaScript on the main thread: defer scripts and drop unused bundles.
xSpeed Free
JS Minify + Defer
AI prompt
Using my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.Guidelines: web.dev — Total Blocking Time
Pass
A
92/100
Server response & caching
5/6 checks passed · 27.5/30 pts earned
Pass
Time to first byte ≤ 200ms 8/8 pts
TTFB 126ms measured from Vilnius, Lithuania (EU) — your server reported 9ms of that (Server-Timing); the rest is network distance to our prober.
Guidelines: web.dev — Time to First Byte
Pass
Page served from cache 7/7 pts
Cache HIT evidence in response headers
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: br — 173KB on the wire (gzip would be 206KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 7 files: email-decode.min.js, site24x7rum-min.js (static.site24x7rum.com), lftracker_v1_lYNOR8xwpXvaWQJZ.js (sc.lfeeder.com)…
Give your CSS/JS/images long Cache-Control lifetimes. 6 of these are served by another host, so that part will not clear.
xSpeed Free
Browser Cache
AI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Guidelines: Lighthouse — Efficient cache policy
Pass
CDN edge serves the page 3/3 pts
Cloudflare answered this page from its edge (`cf-cache-status: HIT`).
Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
40/100
Asset optimization
2/5 checks passed · 8/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: above-the-fold.min.js, the7-horizontal-menu-widget.min.css, the7-sticky-effects.min.css… · ~100ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed Pro
Critical CSS + Unused CSS removal
AI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.Guidelines: Lighthouse — Render-blocking resources
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Fail
Modern, optimized image formats 0/4 pts
Fails the Lighthouse audit — 2 files: menu-banner-2-1.webp, flags.webp · ~100ms of first paint
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
xSpeed Pro
Image Converter (WebP/AVIF)
AI prompt
Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.Guidelines: Lighthouse — Modern image formats
Pass
LCP image discoverable early 4/4 pts
Passes the Lighthouse audit
Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Fail
Total page weight (≤ 350KB for full marks) 0/3 pts
2.9MB transferred — over 1,500KB
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed Free
Minify + Lazy Load + Image Converter (Pro)
AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Guidelines: Lighthouse — Total byte weight
F
20/100
Platform & xSpeed readiness
1/4 checks passed · 2/10 pts earned
Info
Platform
WordPress detected (Elementor 3.34.0; features: additional_custom_breakpoints; settings: css_print_method-internal, google_font-enabled, font_display-swap)
Informational.
Fail
Caching plugin active 0/4 pts
No caching plugin detected
WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
xSpeed Free
xSpeed Cache (free on wordpress.org)
AI prompt
Install and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.Guidelines: WordPress.org — Optimization: caching
Fail
Powered by xSpeed 0/4 pts
xSpeed not detected
xSpeed bundles caching, minification, lazy-load, image optimization and a built-in MCP endpoint that requires an authenticated client for management actions; it also imports settings from other caching plugins in one click.
xSpeed Free
xSpeed Migration (one-click import)
AI prompt
Install xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Pass
xSpeed MCP route responded 2/2 pts
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Guidelines: Model Context Protocol · xSpeed documentation
F
27/100
Lab performance (Lighthouse)
1/5 checks passed · 10.8/40 pts earned
Fail
Lighthouse performance score (mobile) 5.8/18 pts
32/100 (Lighthouse 13.5.0, mobile)
The composite Lighthouse score — every fix below moves it.
xSpeed Free
AI Optimize
AI prompt
Using my site's xSpeed MCP connection: run optimize_site, then run_benchmark to verify the score improved.Guidelines: Lighthouse performance scoring
Fail
Largest Contentful Paint ≤ 2.5s 0/8 pts
LCP 12.3s
Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
xSpeed Free
Page Cache + Preloader (Critical CSS in Pro)
AI prompt
Using my site's xSpeed MCP connection: enable page caching, start the preloader, and (on Pro) generate critical CSS for this page; then re-test LCP.Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Fail
Total Blocking Time ≤ 200ms 0/5 pts
TBT 1.3s
Less JavaScript on the main thread: defer scripts and drop unused bundles.
xSpeed Free
JS Minify + Defer
AI prompt
Using my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.Guidelines: web.dev — Total Blocking Time
Fail
First Contentful Paint ≤ 1.8s 0/4 pts
FCP 4.8s
First paint is gated on server response and render-blocking CSS.
xSpeed Free
Page Cache + CSS Minify
AI prompt
Using my site's xSpeed MCP connection: enable page caching and CSS minification, then re-test First Contentful Paint.Guidelines: web.dev — First Contentful Paint
B
83/100
Server response & caching
5/6 checks passed · 25/30 pts earned
Pass
Time to first byte ≤ 200ms 8/8 pts
TTFB 126ms measured from Vilnius, Lithuania (EU) — your server reported 9ms of that (Server-Timing); the rest is network distance to our prober.
Guidelines: web.dev — Time to First Byte
Pass
Page served from cache 7/7 pts
Cache HIT evidence in response headers
Guidelines: MDN — HTTP caching
Pass
HTML compression (bytes on the wire) 5/5 pts
Content-Encoding: br — 173KB on the wire (gzip would be 206KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Fail
Efficient cache policy on static assets 0/5 pts
Fails the Lighthouse cache-policy audit — 7 files: email-decode.min.js, site24x7rum-min.js (static.site24x7rum.com), lftracker_v1_lYNOR8xwpXvaWQJZ.js (sc.lfeeder.com)…
Give your CSS/JS/images long Cache-Control lifetimes. 6 of these are served by another host, so that part will not clear.
xSpeed Free
Browser Cache
AI prompt
Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the audit.Guidelines: Lighthouse — Efficient cache policy
Pass
CDN edge serves the page 3/3 pts
Cloudflare answered this page from its edge (`cf-cache-status: HIT`).
Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
50/100
Asset optimization
2/5 checks passed · 10/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: the7-horizontal-menu-widget.min.css, above-the-fold.min.js, the7-sticky-effects.min.css… · ~900ms of first paint
CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
xSpeed Pro
Critical CSS + Unused CSS removal
AI prompt
Using my site's xSpeed MCP connection: generate critical CSS for the top pages and enable unused-CSS removal, then re-test.Guidelines: Lighthouse — Render-blocking resources
Pass
Minified CSS and JavaScript 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Minify CSS · Minify JavaScript
Partial
Modern, optimized image formats 2/4 pts
Lighthouse audit score 50% — 1 file: flags.webp
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
xSpeed Pro
Image Converter (WebP/AVIF)
AI prompt
Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.Guidelines: Lighthouse — Modern image formats
Pass
LCP image discoverable early 4/4 pts
Passes the Lighthouse audit
Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Fail
Total page weight (≤ 350KB for full marks) 0/3 pts
2.8MB transferred — over 1,500KB
Page weight is what decides mobile LCP once the server is fast. Resize images to the size they display at, lazy-load below the fold, and drop scripts the page does not use.
xSpeed Free
Minify + Lazy Load + Image Converter (Pro)
AI prompt
Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.Guidelines: Lighthouse — Total byte weight
F
20/100
Platform & xSpeed readiness
1/4 checks passed · 2/10 pts earned
Info
Platform
WordPress detected (Elementor 3.34.0; features: additional_custom_breakpoints; settings: css_print_method-internal, google_font-enabled, font_display-swap)
Informational.
Fail
Caching plugin active 0/4 pts
No caching plugin detected
WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
xSpeed Free
xSpeed Cache (free on wordpress.org)
AI prompt
Install and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.Guidelines: WordPress.org — Optimization: caching
Fail
Powered by xSpeed 0/4 pts
xSpeed not detected
xSpeed bundles caching, minification, lazy-load, image optimization and a built-in MCP endpoint that requires an authenticated client for management actions; it also imports settings from other caching plugins in one click.
xSpeed Free
xSpeed Migration (one-click import)
AI prompt
Install xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Pass
xSpeed MCP route responded 2/2 pts
The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
Guidelines: Model Context Protocol · xSpeed documentation
Past scans of www.eccouncil.org newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-12 03:59 UTC this report | 63 | D | desktop | 126ms | 61 | |
| 2026-09-30 04:40 UTC | 55 | D | desktop | 126ms | 48 | View report → |
| 2026-09-24 05:04 UTC | 59 | D | desktop | 146ms | 59 | View report → |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()