83of 100
89of 100
solgar.fi
BLevel 4 · Fast
BLevel 4 · Fast
WordPress⚡ xSpeed v1.4.2Pro v1.3.2MCP signal presentCloudflare
173msTTFB
99Lighthouse desktop · graded
100Lighthouse mobile
841msLCP
0.00CLS
brCompression
HITCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 89 (B) —
Real visitors (Chrome UX Report)
Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
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 89 (B) against 83 (B) 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).
173msTTFB
99Lighthouse desktop
100Lighthouse mobile · graded
764msLCP
0.03CLS
brCompression
HITCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 83 (B) —
Real visitors (Chrome UX Report)
Not enough Chrome traffic for field data on this page or its site, so only the lab run above is available.
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 83 (B) against
89 (B) 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)A+99
5/5 checks passed · 39.8/40 pts Jump to section ↓
Server response & cachingB83
5/6 checks passed · 25/30 pts Jump to section ↓
Asset optimizationF31
1/4 checks passed · 5/16 pts Jump to section ↓
Platform & xSpeed readinessA+100
3/3 checks passed · 10/10 pts Jump to section ↓
Lab performance (Lighthouse)A+100
5/5 checks passed · 40/40 pts Jump to section ↓
Server response & cachingA92
5/6 checks passed · 27.5/30 pts Jump to section ↓
Asset optimizationF50
2/4 checks passed · 8/16 pts Jump to section ↓
Platform & xSpeed readinessA+100
3/3 checks passed · 10/10 pts Jump to section ↓
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
MCP status reported — verify client access
- ✓WordPressDetected
- ✓xSpeed Cache installedv1.4.2 + Pro v1.3.2
- ✓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.
5 of these checks map to an xSpeed feature. solgar.fi's report indicates that xSpeed MCP is available. This scan did not verify client credentials; if your client is configured and authenticated, use this prompt:
If you are authenticated to my site's xSpeed MCP server, read the failing checks from https://xspeedcache.com/scan/r/solgar-fi-5f3dbe61c4.md, apply the fixes: enable page caching, compression, minification and lazy loading, warm the cache, then run a benchmark 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.
A+
99/100
Lab performance (Lighthouse)
5/5 checks passed · 39.8/40 pts earned
Pass
Lighthouse performance score (desktop) 17.8/18 pts
99/100 (Lighthouse 13.5.0, desktop)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 841ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
Pass
B
83/100
Server response & caching
5/6 checks passed · 25/30 pts earned
Pass
Time to first byte ≤ 200ms 8/8 pts
TTFB 173ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 10ms from its own network — the gap between the two numbers is distance, not your server.
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 — 74KB on the wire (gzip would be 84KB)
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Fail
Efficient cache policy on static assets 0/5 pts
Fails the Lighthouse cache-policy audit — 8 files: Solgar_Brand_Equity_Campaign_US_Still_Images_kitchen_80_square-scaled.jpg, 12420-Prenatal-Multivitamin-with-Phytonutrients-768x1097.png, 12400-Male-Multivitamin-with-Phytonutrients-768x1097.png…
Give CSS/JS/images long Cache-Control lifetimes so repeat views are free.
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
31/100
Asset optimization
1/5 checks passed · 5/16 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: popup.min.css, b1c3bc909b2b26ae994e264f1c48c16b.css, jquery.min.js… · ~500ms 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 — 1 file: 12420-Prenatal-Multivitamin-with-Phytonutrients-768x1097.png · ~50ms 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
Info
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Resource Hints (preload) + Lazy Load exclusions
AI prompt
Using my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Partial
Total page weight (≤ 350KB for full marks) 1/3 pts
1374KB transferred — heavy: most WordPress pages this size fail mobile LCP
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
A+
100/100
Platform & xSpeed readiness
3/4 checks passed · 10/10 pts earned
Info
Platform
WordPress detected
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.4.2 + Pro v1.3.2)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.4.2 + Pro v1.3.2
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
A+
100/100
Lab performance (Lighthouse)
5/5 checks passed · 40/40 pts earned
Pass
Lighthouse performance score (mobile) 18/18 pts
100/100 (Lighthouse 13.5.0, mobile)
Guidelines: Lighthouse performance scoring
Pass
Largest Contentful Paint ≤ 2.5s 8/8 pts
LCP 764ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Pass
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 173ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time. Google measured your server responding in 1ms from its own network — the gap between the two numbers is distance, not your server.
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 — 74KB on the wire (gzip would be 84KB)
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: main.css, t128.jpg (5bav82-m.ns1pcdn.net), t128.jpg (kgnvry-ns1p.b-cdn.net)…
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 · 8/16 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 1 file: main.css · ~150ms 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
Pass
Modern, optimized image formats 4/4 pts
Passes the Lighthouse audit
Guidelines: Lighthouse — Modern image formats
Info
LCP image discoverable early —
Audit not reported for this page
Re-run when Lighthouse is available.
xSpeed Free
Resource Hints (preload) + Lazy Load exclusions
AI prompt
Using my site's xSpeed MCP connection: preload the LCP image for this page and exclude it from lazy loading, then re-test LCP.Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Fail
Total page weight (≤ 350KB for full marks) 0/3 pts
1539KB 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
A+
100/100
Platform & xSpeed readiness
3/4 checks passed · 10/10 pts earned
Info
Platform
WordPress detected
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.4.2 + Pro v1.3.2)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.4.2 + Pro v1.3.2
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 solgar.fi newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-13 13:36 UTC | 79 | C | desktop | 113ms | 97 | View report → |
| 2026-10-13 13:28 UTC | 77 | C | desktop | 146ms | 87 | View report → |
| 2026-10-13 13:28 UTC | 73 | C | desktop | 252ms | 87 | View report → |
| 2026-10-13 13:12 UTC | 83 | B | desktop | 244ms | 100 | View report → |
| 2026-10-13 13:04 UTC | 83 | B | desktop | 259ms | 100 | View report → |
| 2026-10-13 12:55 UTC | 83 | B | desktop | 127ms | 99 | View report → |
| 2026-10-13 10:26 UTC this report | 83 | B | desktop | 173ms | 99 |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()