66of 100
48of 100
www.boatrentalskw.us
DLevel 3 · Average
FLevel 2 · Slow
WordPress 7.1.1⚡ xSpeed v1.3.3Cloudflare
111msTTFB
59Lighthouse desktop · graded
25Lighthouse mobile
2.1sLCP
0.41CLS
brCompression
HITCache
Lab data: Lighthouse 13.4.1 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 48 (F) —
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.4.1 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 66 (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).
111msTTFB
59Lighthouse desktop
25Lighthouse mobile · graded
20.0sLCP
0.29CLS
brCompression
HITCache
Lab data: Lighthouse 13.4.1 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 66 (D) —
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.4.1 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 66 (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)D63
2/5 checks passed · 25.1/40 pts Jump to section ↓
Server response & cachingA92
5/6 checks passed · 27.5/30 pts Jump to section ↓
Asset optimizationF20
1/5 checks passed · 4/20 pts Jump to section ↓
Platform & xSpeed readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Lab performance (Lighthouse)F11
0/5 checks passed · 4.5/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 readinessA+100
2/2 checks passed · 8/8 pts Jump to section ↓
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
xSpeed is installed — verify its MCP endpoint before automating
- ✓WordPressWordPress 7.1.1
- ✓xSpeed Cache installedv1.3.3
- →MCP signal presentThe scan did not confirm MCP availability. Configure it in xSpeed → MCP Server, then verify authenticated access from an MCP client.
- –xSpeed Hub signalOptional: review Hub configuration and confirm authorized site membership at app.xspeedcache.com (this xSpeed version does not report Hub status).
www.boatrentalskw.us already runs xSpeed Cache v1.3.3, but the report did not confirm its MCP availability. In wp-admin open xSpeed → MCP Server → Connect (or run `wp xspeed mcp connect`), then verify the endpoint and authenticated client access before using this prompt:
My WordPress site www.boatrentalskw.us runs xSpeed Cache and scored 66/100 (https://xspeedcache.com/scan/r/www-boatrentalskw-us-2708c9a9c5). Once I've configured and authenticated your MCP connection, read the failing checks from https://xspeedcache.com/scan/r/www-boatrentalskw-us-2708c9a9c5.md and 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.
D
63/100
Lab performance (Lighthouse)
2/5 checks passed · 25.1/40 pts earned
Partial
Lighthouse performance score (desktop) 10.6/18 pts
59/100 (Lighthouse 13.4.1, 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 2.1s
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Fail
Cumulative Layout Shift ≤ 0.1 0/5 pts
CLS 0.408
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
Partial
Total Blocking Time ≤ 200ms 2.5/5 pts
TBT 240ms
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 111ms 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 3ms 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 (Brotli/GZIP) 5/5 pts
Content-Encoding: br
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Partial
Efficient cache policy on static assets 2.5/5 pts
Lighthouse cache-policy audit score 50% — 1 file: v2 (fh-kit.com)
Every asset with a short cache lifetime here is served by another host (fh-kit.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
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
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
F
20/100
Asset optimization
1/5 checks passed · 4/20 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 8 files: kb-glightbox.min.css, header.min.css, content.min.css… · ~400ms of first paint
Inline the critical CSS and defer the rest. Note that 3 of these come from another host, so deferring them is the only lever you have.
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 — 7 files: P7080083process-2-3-1024x768.jpg, 298222913_2257661824393419_3521876998923381711_n-2-768x960.jpg, 426164764_18423053155004169_5145819475631310642_n-2-768x768.jpg… · ~150ms of first paint
Serve WebP/AVIF at the right compression. 2 of these come from another host and will not clear.
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
Fail
LCP image discoverable early 0/4 pts
Fails the Lighthouse audit
The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
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 ≤ 1.5MB 0/3 pts
3.8MB transferred
Heavy pages are slow on every connection — compress, lazy-load, and trim.
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
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected (WordPress 7.1.1)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.3.3)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.3.3
Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Info
xSpeed MCP route response not confirmed —
This scan did not confirm an xSpeed MCP route response. Client authentication and control were not tested.
Configure an MCP client for this endpoint and verify authenticated access before relying on it to inspect or change the site.
xSpeed Free
MCP Server (built into xSpeed Free)
AI prompt
In xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.Guidelines: Model Context Protocol · xSpeed documentation
F
11/100
Lab performance (Lighthouse)
0/5 checks passed · 4.5/40 pts earned
Fail
Lighthouse performance score (mobile) 4.5/18 pts
25/100 (Lighthouse 13.4.1, 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 20.0s
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
Fail
Cumulative Layout Shift ≤ 0.1 0/5 pts
CLS 0.289
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 632ms
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 15.6s
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 111ms 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 4ms 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 (Brotli/GZIP) 5/5 pts
Content-Encoding: br
Guidelines: MDN — Content-Encoding · RFC 7932 — Brotli
Fail
Efficient cache policy on static assets 0/5 pts
Fails the Lighthouse cache-policy audit — 1 file: v2 (fh-kit.com)
Every asset with a short cache lifetime here is served by another host (fh-kit.com). Their Cache-Control is not yours to set — this check will not clear while you load them.
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
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: 0580a29617141834c75b8fbfb19fe041.css, global.min.css, 789975193528dd63b3944f3998216b9d.css… · ~950ms of first paint
Inline the critical CSS and defer the rest. Note that 3 of these come from another host, so deferring them is the only lever you have.
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% — 3 files: lI77MDUzTqHhqlAerewA/convert (cdn.filestackcontent.com), MGTl85wpQigPfkMAInkM/convert (cdn.filestackcontent.com), fZtWfrsfTpiFnkFPbQH5/convert (cdn.filestackcontent.com)
Every image flagged here is served from another host (cdn.filestackcontent.com), so converting them is not yours to do — the fix is to host them yourself, or load fewer.
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 ≤ 1.5MB 0/3 pts
3.6MB transferred
Heavy pages are slow on every connection — compress, lazy-load, and trim.
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
2/4 checks passed · 8/8 pts earned
Info
Platform
WordPress detected (WordPress 7.1.1)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.3.3)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.3.3
Guidelines: xSpeed — feature overview · xSpeed vs other cache plugins
Info
xSpeed MCP route response not confirmed —
This scan did not confirm an xSpeed MCP route response. Client authentication and control were not tested.
Configure an MCP client for this endpoint and verify authenticated access before relying on it to inspect or change the site.
xSpeed Free
MCP Server (built into xSpeed Free)
AI prompt
In xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.Guidelines: Model Context Protocol · xSpeed documentation
Past scans of www.boatrentalskw.us newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-09-24 17:04 UTC | 76 | C | desktop | 123ms | 84 | View report → |
| 2026-09-19 16:13 UTC this report | 66 | D | desktop | 111ms | 59 | |
| 2026-09-19 16:05 UTC | 62 | D | desktop | 118ms | 51 | View report → |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()