40of 100

www.2m7.ca

Scanned Tue, 13 Oct 2026 10:57:16 GMT · https://www.2m7.ca/ · scanned 3 times — see history

FLevel 2 · Slow

Graded on mobileCloudflare

Scan a different site ›

Mobile view of www.2m7.ca at scan time. Click for full size — As Lighthouse saw it · click to enlarge

108msTTFB

38Lighthouse mobile · graded

12.6sLCP

0.11CLS

gzipCompression

HITCache

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

Real visitors · Chrome UX Report · mobile · whole site (this page has too little traffic of its own) · fails Core Web Vitals

1.6sLCP (p75)

78msINP (p75)

0.17CLS (p75)

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)F23 0/5 checks passed · 9.3/40 pts Jump to section ↓ Server response & cachingC75 4/6 checks passed · 22.5/30 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 (11 checks name a concrete remediation):

Read the speed report at https://xspeedcache.com/scan/r/www-2m7-ca-f7ccbb0da8.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.2m7.ca/"} 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 · 9.3/40 pts earned

23/100

Fail

Lighthouse performance score (mobile) 6.8/18 pts

38/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 12.6s

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.113

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

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 4.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

Server response & caching

4/6 checks passed · 22.5/30 pts earned

75/100

Pass

Time to first byte ≤ 200ms 8/8 pts

TTFB 108ms 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

Partial

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

Served as gzip: 25KB. The same page as Brotli is 21KB — 4.2KB smaller on every uncached view.

Your server can produce a much smaller Brotli response but serves gzip. Prefer Brotli for HTML.

xSpeed Free GZIP (Brotli in Pro)

AI prompt

Using my site's xSpeed MCP connection: check how the HTML is compressed, make sure the served encoding is the smaller of gzip and Brotli, then confirm the response size.

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: mg__7979.png (d10w4s0jex8wby.cloudfront.net), stat.js (clickcease.com), swap.js (cdn.callrail.com)…

Every asset with a short cache lifetime here is served by another host (d10w4s0jex8wby.cloudfront.net, clickcease.com, cdn.callrail.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

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

Asset optimization

1/5 checks passed · 4/20 pts earned

20/100

Fail

No render-blocking resources 0/5 pts

Fails the Lighthouse audit — 3 files: swap.js (cdn.callrail.com), 2m7.webflow.shared.8f92c9d23.min.css (cdn.prod.website-files.com), countup.min.js (cdn.jsdelivr.net) · ~2.8s of first paint

Everything blocking first paint here is loaded from another host (cdn.callrail.com, cdn.prod.website-files.com, cdn.jsdelivr.net). You cannot inline or minify those — the fix is to defer them, or load fewer of them.

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 — 3 files: mg__7979.png (d10w4s0jex8wby.cloudfront.net), 675b0451d72660bae50e0fdf_Frame%2080%20(1).avif (cdn.prod.website-files.com), 675afa82e520105f77b09db9_picture%20(1).avif (cdn.prod.website-files.com) · ~150ms of first paint

Every image flagged here is served from another host (d10w4s0jex8wby.cloudfront.net, cdn.prod.website-files.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

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

1932KB 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

Past scans of www.2m7.ca newest first · every report keeps its link

Scanned	Score	Grade	Graded on	TTFB	Lighthouse
2026-10-13 12:22 UTC	46	F	mobile	192ms	42	View report →
2026-10-13 11:42 UTC	46	F	mobile	161ms	53	View report →
2026-10-13 10:57 UTC this report	40	F	mobile	108ms	38

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 www-2m7-ca-f7ccbb0da8 · 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 www.2m7.ca and would rather this report were not public? Email support@wpdeveloper.com and we will remove it.

www.2m7.ca

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

Past scans of www.2m7.ca newest first · every report keeps its link

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 →