xSpeed Cache is officially live! Get 50% OFF during Launch Week — Lifetime starts at just $79Lifetime from $79 — 50% OFF, Launch Week! See Plans →

See Plans →
Get Plugin xSpeed Hub
All features Cloudflare EnterpriseAdd-on

By what you run

WooCommerce storesAgencies & freelancersBlogs & publishersElementor & page buildersMembership & LMSAI & agents

By your business

Home & trade services 3 Food & hospitality 4 Health & wellness 5 Professional services 5 Retail & ecommerce 5 Creative & events 4 Publishing & media 4 Learning & community 4 Tech & agencies 3 With your AI agent All use cases & industries
xSpeed Hub Pricing Docs Blog Scan
Free vs Pro Compare Showcase Coverage Support Community
Appearance
Get Plugin
89of 100

homeneatliving.com

Scanned Sat, 26 Sep 2026 00:29:19 GMT · https://homeneatliving.com/ · scanned 4 times — see history

BLevel 4 · Fast
WordPress 7.1.2⚡ xSpeed v1.3.5MCP signal presentCloudflare
Scan a different site ›
Desktop view of homeneatliving.com at scan time. Click for full size
As Lighthouse saw it · click to enlarge
129msTTFB
76Lighthouse desktop · graded
82Lighthouse mobile
531msLCP
0.80CLS
brCompression
HITCache

Lab data: Lighthouse 13.5.0 desktop run, graded above · Reproduce this run on PageSpeed Insights ↗ · Mobile: 90 (A) —

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 90 (A) against 89 (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).

Lab performance (Lighthouse)C77 3/5 checks passed · 30.7/40 pts Jump to section ↓ Server response & cachingA+100 6/6 checks passed · 30/30 pts Jump to section ↓ Asset optimizationA90 4/5 checks passed · 18/20 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

MCP status reported — verify client access

  1. ✓WordPressWordPress 7.1.2
  2. ✓xSpeed Cache installedv1.3.5
  3. ✓MCP signal presentThe report indicates MCP availability. This does not verify client authentication or control.
  4. →xSpeed Hub signalOptional: review Hub configuration and confirm authorized site membership at app.xspeedcache.com (this xSpeed version does not report Hub status).

3 of these checks map to an xSpeed feature. homeneatliving.com'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/homeneatliving-com-b63723d57a.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.
Get xSpeed Cache Explore the features
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 →

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/mcp

Claude Code — one command

claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcp

Claude Desktop, Cursor, or any MCP client — add to your config

{ "mcpServers": { "xspeed-scan": { "type": "http", "url": "https://xspeedcache.com/scan/mcp" } } }
  • run_speed_scan Scan any public URL and return this whole graded report.
  • get_speed_scan Read a scan already run, by its id.
Read the MCP documentation →
C

Lab performance (Lighthouse)

3/5 checks passed · 30.7/40 pts earned
77/100
Partial
Lighthouse performance score (desktop) 13.7/18 pts
76/100 (Lighthouse 13.5.0, desktop)
The composite Lighthouse score — every fix below moves it.
xSpeed Free AI Optimize
AI promptUsing 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 531ms
Guidelines: web.dev — Largest Contentful Paint · Optimize LCP
Fail
Cumulative Layout Shift ≤ 0.1 0/5 pts
CLS 0.799
Reserve space for images/embeds so the page does not jump as it loads.
xSpeed Free Lazy Load — CLS fix (adds width/height)
AI promptUsing 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
Pass
Total Blocking Time ≤ 200ms 5/5 pts
TBT 0ms
Guidelines: web.dev — Total Blocking Time
Pass
First Contentful Paint ≤ 1.8s 4/4 pts
FCP 416ms
Guidelines: web.dev — First Contentful Paint
A+

Server response & caching

6/6 checks passed · 30/30 pts earned
100/100
Pass
Time to first byte ≤ 200ms 8/8 pts
TTFB 129ms 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
Pass
Efficient cache policy on static assets 5/5 pts
Passes the Lighthouse cache-policy audit
Guidelines: Lighthouse — Efficient cache policy
Pass
CDN / edge network 3/3 pts
Cloudflare detected
Guidelines: web.dev — Content delivery networks
Pass
Clean redirect chain 2/2 pts
No redirects — the URL answers directly
Guidelines: Lighthouse — Avoid redirects
A

Asset optimization

4/5 checks passed · 18/20 pts earned
90/100
Pass
No render-blocking resources 5/5 pts
Passes the Lighthouse audit
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% — 8 files: New-Project-2026-08-26T051139.558-1024x576.webp, New-Project-2026-08-27T041550.722-768x432.webp, New-Project-2026-08-25T041704.051-768x432.webp…
Serve WebP/AVIF at the right compression — usually the single largest byte saving.
xSpeed Pro Image Converter (WebP/AVIF)
AI promptUsing 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
Pass
Total page weight ≤ 1.5MB 3/3 pts
0.6MB transferred
Guidelines: Lighthouse — Total byte weight
A+

Platform & xSpeed readiness

3/4 checks passed · 10/10 pts earned
100/100
Info
Platform
WordPress detected (WordPress 7.1.2)
Informational.
Pass
Caching plugin active 4/4 pts
xSpeed Cache (xSpeed signature: v1.3.5)
Guidelines: WordPress.org — Optimization: caching
Pass
Powered by xSpeed 4/4 pts
xSpeed signature: v1.3.5
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 homeneatliving.com newest first · every report keeps its link

ScannedScoreGradeGraded onTTFBLighthouse
2026-09-26 00:29 UTC 93 A desktop 130ms 100 View report →
2026-09-26 00:29 UTC this report 89 B desktop 129ms 76
2026-09-26 00:28 UTC 89 B desktop 112ms 76 View report →
2026-09-26 00:24 UTC 85 B desktop 283ms 76 View report →

Share your score a card for X, LinkedIn, Slack — anywhere

Every check here has a one-click fix in xSpeed Cache

Page caching, compression, image optimization and a built-in MCP server, so your AI assistant can run this playbook for you.

Get xSpeed Cache Scan another site
Scan homeneatliving-com-b63723d57a · rubric v2026.09.5 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the desktop run; the mobile run is graded on its tab · Server probes from xspeedcache.com. Scores vary run to run; treat trends, not single digits, as the signal. Markdown for AI agents · JSON
Own homeneatliving.com and would rather this report were not public? Email support@wpdeveloper.com and we will remove it.