40of 100

jetmateservices.au

Scanned Wed, 14 Oct 2026 19:08:31 GMT · https://jetmateservices.au/

FLevel 2 · Slow

Graded on mobileCloudflare

Scan a different site ›

Mobile view of jetmateservices.au at scan time. Click for full size — As Lighthouse saw it · click to enlarge

208msTTFB

59Lighthouse mobile · graded

14.2sLCP

0.16CLS

gzipCompression

MISSCache

Lab data: Lighthouse 13.5.0 mobile run, graded above · Reproduce this run on PageSpeed Insights ↗

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. 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)F44 0/5 checks passed · 17.6/40 pts Jump to section ↓ Server response & cachingF50 2/5 checks passed · 13.5/27 pts Jump to section ↓ Asset optimizationF20 1/5 checks passed · 4/20 pts Jump to section ↓

Top fixes ranked by points recovered

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 (12 checks name a concrete remediation):

Read the speed report at https://xspeedcache.com/scan/r/jetmateservices-au-ab341dddc0.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://jetmateservices.au/"} to https://xspeedcache.com/api/scan and compare the scores.

How the checks are graded Scan another site

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.

Use the MCP server →One line in Claude Code or Cursor to scan any site from your agent. Chat with the Telegram bot →Anyone can scan any site and get the fixes right from @xSpeedScanBot. Free, no signup.

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 →

Lab performance (Lighthouse)

0/5 checks passed · 17.6/40 pts earned

44/100

Partial

Lighthouse performance score (mobile) 10.6/18 pts

59/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 14.2s

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

Partial

Cumulative Layout Shift ≤ 0.1 2.5/5 pts

CLS 0.155

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 289ms

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

Partial

First Contentful Paint ≤ 1.8s 2/4 pts

FCP 2.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

Server response & caching

2/6 checks passed · 13.5/27 pts earned

50/100

Partial

Time to first byte ≤ 200ms 4/8 pts

TTFB 208ms 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 5ms from its own network — the gap between the two numbers is distance, not your server.

The server rebuilds the page on every request. A page cache answers in 5–15ms.

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

Fail

Page served from cache 0/7 pts

No cache evidence in headers or HTML

Serve HTML from a static cache instead of rebuilding it per visitor.

xSpeed Free Page Cache + Preloader

AI prompt

Using my site's xSpeed MCP connection: enable page caching, start the preloader so pages are pre-warmed, and confirm get_cache_status reports hits.

Guidelines: MDN — HTTP caching

Pass

HTML compression (bytes on the wire) 5/5 pts

Content-Encoding: gzip — 12KB on the wire

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: ~flock.js, fbevents.js (connect.facebook.net), 1732993667941235 (connect.facebook.net)…

Give your CSS/JS/images long Cache-Control lifetimes. 4 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

Info

CDN edge serves the page —

Cloudflare detected, but its headers do not say whether it served this page from the edge.

Check your CDN’s cache status for HTML; if pages pass through to the origin, enable HTML caching for anonymous visitors.

Guidelines: web.dev — Content delivery networks

Pass

Clean redirect chain 2/2 pts

No redirects — the URL answers directly

Guidelines: Lighthouse — Avoid redirects

Asset optimization

1/5 checks passed · 4/20 pts earned

20/100

Fail

No render-blocking resources 0/5 pts

Fails the Lighthouse audit — 2 files: styles-DwxjI6Rj.css, css2 (fonts.googleapis.com) · ~1.3s 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 — 8 files: patio-before.jpg, patio-after.jpg, jetmate-logo-blue.png… · ~3.5s 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

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 (≤ 350KB for full marks) 0/3 pts

5.1MB 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

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 jetmateservices-au-ab341dddc0 · rubric v2026.10.1 · Lab data: Google PageSpeed Insights (Lighthouse 13.5.0), graded on the mobile run · Server probes from xspeedcache.com. Scores vary run to run; treat trends, not single digits, as the signal. Markdown for AI agents · JSON
Own jetmateservices.au and would rather this report were not public? Email support@wpdeveloper.com and we will remove it.

jetmateservices.au

Top fixes ranked by points recovered

Act on this report with your AI assistant

Run this scan without the form

Connect this scanner to your AI assistant

Lab performance (Lighthouse)

Server response & caching

Asset optimization

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

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

Recently scanned public reports All public scans →