70of 100
39of 100
206msTTFB
72Lighthouse desktop · graded
37Lighthouse mobile
811msLCP
0.00CLS
brCompression
MISSCache
Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 39 (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.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 39 (F) against 70 (C) 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).
206msTTFB
72Lighthouse desktop
37Lighthouse mobile · graded
11.5sLCP
0.00CLS
brCompression
MISSCache
Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗ · Desktop: 70 (C) —
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 70 (C) against
39 (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).
Top fixes ranked by points recovered · desktop
Top fixes ranked by points recovered · mobile
Act on this report with your AI assistant
- ✓Platform detectedNot conclusively identified — every check below links the official guideline for its fix, valid on any stack.
- →Act on it with your AIThe machine-readable twin of this report gives an agent every failing check with its evidence, remediation and guideline link.
- →Check the originHosting sets the floor on TTFB. xCloud hosts any stack — agent/MCP access built in, bring-your-own-server pricing.
This does not look like a WordPress site, so xSpeed cannot automate the fixes directly — but Every check below links its official guideline, and the machine-readable twin of this report gives an AI everything it needs to plan the work (7 checks name a concrete remediation):
Read the speed report at https://xspeedcache.com/scan/r/www-boatrentalskeywest-fun-4ac0f8122c.md — it lists every failing check with evidence and the official guideline for the fix. Produce a prioritized fix plan for my stack, apply what you can, then re-test by POSTing {"url":"https://www.boatrentalskeywest.fun/"} to https://xspeedcache.com/api/scan and compare the scores.Hosting is half of every score.
Whatever the stack, the server behind it sets the floor on TTFB. xCloud — from the team behind xSpeed — hosts any platform (this site's own scanner runs on 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.
C
75/100
Lab performance (Lighthouse)
3/5 checks passed · 30/40 pts earned
Partial
Lighthouse performance score (desktop) 13/18 pts
72/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 811ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Pass
Fail
Total Blocking Time ≤ 200ms 0/5 pts
TBT 859ms
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
C
72/100
Server response & caching
3/6 checks passed · 16.5/23 pts earned
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 206ms measured from Vilnius, Lithuania (EU) — your server reported 111ms of that (Server-Timing); the rest is network distance to our prober.
Your server is already fast; what this check measures is dominated by the distance to our prober. Send Server-Timing (you already do) and compare against a prober near your audience.
xSpeed Free
Page Cache
AI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.Guidelines: web.dev — Time to First Byte
N/A
Page served from cache —
Correctly per-visitor — this response is marked `private, no-cache, max-age=0`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
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% — 5 files: fbevents.js (connect.facebook.net), 269422440140811 (connect.facebook.net), v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495 (static.cloudflareinsights.com)…
Every asset with a short cache lifetime here is served by another host (connect.facebook.net, static.cloudflareinsights.com, facebook.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
D
60/100
Asset optimization
2/5 checks passed · 12/20 pts earned
Partial
No render-blocking resources 2.5/5 pts
Lighthouse audit score 50% — 2 files: jquery.min.js, d22864aabfcbacc2d303b7f889d8315c.js
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: key-west-sandbar-and-kayak-tour-1536x865.png.webp · ~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
Pass
LCP image discoverable early 4/4 pts
Passes the Lighthouse audit
Guidelines: web.dev — Optimize LCP · Lighthouse — LCP request discovery
Partial
Total page weight ≤ 1.5MB 1.5/3 pts
2.7MB 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
F
29/100
Lab performance (Lighthouse)
1/5 checks passed · 11.7/40 pts earned
Fail
Lighthouse performance score (mobile) 6.7/18 pts
37/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 11.5s
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 916ms
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 7.7s
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
D
61/100
Server response & caching
3/6 checks passed · 14/23 pts earned
Partial
Time to first byte ≤ 200ms 4/8 pts
TTFB 206ms measured from Vilnius, Lithuania (EU) — your server reported 111ms of that (Server-Timing); the rest is network distance to our prober.
Your server is already fast; what this check measures is dominated by the distance to our prober. Send Server-Timing (you already do) and compare against a prober near your audience.
xSpeed Free
Page Cache
AI prompt
Using my site's xSpeed MCP connection: enable page caching and warm this page with the preloader, then re-check TTFB.Guidelines: web.dev — Time to First Byte
N/A
Page served from cache —
Correctly per-visitor — this response is marked `private, no-cache, max-age=0`, so it must not be held in a shared cache.
Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
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 — 5 files: fbevents.js (connect.facebook.net), 269422440140811 (connect.facebook.net), v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495 (static.cloudflareinsights.com)…
Every asset with a short cache lifetime here is served by another host (connect.facebook.net, static.cloudflareinsights.com, facebook.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
34/100
Asset optimization
1/5 checks passed · 5.5/16 pts earned
Fail
No render-blocking resources 0/5 pts
Fails the Lighthouse audit — 3 files: d22864aabfcbacc2d303b7f889d8315c.js, jquery.min.js, v1 (fareharbor.com) · ~300ms of first paint
Inline the critical CSS and defer the rest. Note that one of these comes from another host, so deferring it 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 — 2 files: tiki-barge-beach-key-west-2-768x576.jpg.webp, sandbar-mangrove-beach-768x576.jpeg.webp · ~300ms 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 ≤ 1.5MB 1.5/3 pts
2.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
Past scans of www.boatrentalskeywest.fun newest first · every report keeps its link
| Scanned | Score | Grade | Graded on | TTFB | Lighthouse | |
|---|---|---|---|---|---|---|
| 2026-10-01 20:41 UTC | 80 | B | desktop | 98ms | 73 | View report → |
| 2026-09-30 01:59 UTC | 77 | C | desktop | 224ms | 78 | View report → |
| 2026-09-29 23:00 UTC | 69 | D | desktop | 213ms | 71 | View report → |
| 2026-09-29 22:44 UTC | 69 | D | desktop | 210ms | 73 | View report → |
| 2026-09-29 22:42 UTC | 74 | C | desktop | 220ms | 82 | View report → |
| 2026-09-29 22:29 UTC this report | 70 | C | desktop | 206ms | 72 | |
| 2026-09-29 21:29 UTC | 75 | C | desktop | 130ms | 68 | View report → |
| 2026-09-29 21:28 UTC | 72 | C | desktop | 146ms | 67 | View report → |
| 2026-09-29 21:11 UTC | 66 | D | desktop | 203ms | 70 | View report → |
| 2026-09-29 20:37 UTC | 64 | D | desktop | 214ms | 70 | View report → |
Recently scanned public reports All public scans →
Click anywhere or press Esc to close![Full-size screenshot]()