# Website Speed Report, demo.ai2wp.site

> **What this document is.** A point-in-time speed audit of https://demo.ai2wp.site/replit-pricing/,
> produced by xSpeed Scan (https://xspeedcache.com/scan). Evidence comes from two sources:
> server probes run from xspeedcache.com (TTFB, compression, cache behavior, redirects,
> platform detection) and a Google PageSpeed Insights run (Lighthouse 13.4.1, desktop).
> **Two graded runs.** The score below is graded on the **desktop** run — the one a reader can reproduce
> in their own browser. The mobile run is graded on the same rubric further down (88/100,
> grade B). Google ranks on mobile, so when the two differ, report both and act on the mobile failures too.
>
> **How to read it.** Weighted checks roll up into four dimensions and one 0-100 score.
> Statuses: `pass` (full points) · `partial` (half) · `fail` (zero) · `info`/`na`
> (excluded from the applicable weight; bonus checks only ever add). Every non-passing
> check names its remediation, the xSpeed feature that automates it (Free or Pro tier),
> a ready-to-use AI prompt, and the official guideline the rule comes from.
>
> **How to act on it, detected state: xSpeed installed, MCP live.**
> Connect to the site's own MCP endpoint and run the per-check prompts below: or the
> one-shot prompt at the end of this document.
> Optional: attach the site to xSpeed Hub (https://app.xspeedcache.com) to manage every site from one MCP connection.
>
> **How to re-test.** Public API (no auth): `POST https://xspeedcache.com/api/scan`
> with body `{"url": "https://example.com"}`, then poll `GET /api/scan/{scanId}` for the
> JSON report. Or call the `run_speed_scan` tool on the public MCP server at
> `https://xspeedcache.com/scan/mcp`. Fair-use limits: 4 scans per caller and 200 global per
> 10 minutes; re-scanning the same URL within 10 minutes returns the existing report,
> so scan → fix → wait ~10 minutes → re-scan is the intended loop.
>
> **Connect this scanner as an MCP server (free, no API key).**
> Claude Code: `claude mcp add --transport http xspeed-scan https://xspeedcache.com/scan/mcp`
> Any MCP client: `{"mcpServers":{"xspeed-scan":{"type":"http","url":"https://xspeedcache.com/scan/mcp"}}}`
> Tools: `run_speed_scan` (url, fresh?, strategy?) and `get_speed_scan` (scanId). `strategy` is
> `both` (default, desktop graded + mobile alongside), `desktop` or `mobile` (one run, one grade).
> Docs: https://xspeedcache.com/docs/scan-mcp/

**Score: 91/100. Grade A · Level 5 (Instant) — graded on the desktop run**

- Scanned: 2026-09-20T11:12:36.143Z
- Report (HTML): https://xspeedcache.com/scan/r/demo-ai2wp-site-983acc18f8
- Report (JSON): https://xspeedcache.com/api/scan/demo-ai2wp-site-983acc18f8
- Rubric: v2026.09.5
- Platform: WordPress 7.1.1 · xSpeed Cache v1.3.3 · xSpeed MCP endpoint live · CDN: Cloudflare
## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 542ms |
| Lighthouse performance (desktop) — graded | 100/100 |
| Lighthouse performance (mobile) | 98/100 |
| Reproduce the desktop run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fdemo.ai2wp.site%2Freplit-pricing%2F&form_factor=desktop |
| Largest Contentful Paint | 414ms |
| Cumulative Layout Shift | 0.000 |
| Total Blocking Time | 0ms |
| HTML compression | br |
| Served from cache | yes (HIT) |
| Redirects before final URL | 0 |

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Core Web Vitals & lab metrics | 100/100 | A+ | 40/40 |
| Server response & caching | 87/100 | B | 26/30 |
| Asset optimization | 69/100 | D | 11/16 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

## Core Web Vitals & lab metrics: 100/100 (A+) · 40/40 pts

### [PASS] S1 · Lighthouse performance score (desktop) (18/18 pts)

- Evidence: 100/100 (Lighthouse 13.4.1, desktop)
- Guidelines: [Lighthouse performance scoring](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring)

### [PASS] S2 · Largest Contentful Paint ≤ 2.5s (8/8 pts)

- Evidence: LCP 414ms
- Guidelines: [web.dev — Largest Contentful Paint](https://web.dev/articles/lcp) · [Optimize LCP](https://web.dev/articles/optimize-lcp)

### [PASS] S3 · Cumulative Layout Shift ≤ 0.1 (5/5 pts)

- Evidence: CLS 0.000
- Guidelines: [web.dev — Cumulative Layout Shift](https://web.dev/articles/cls)

### [PASS] S4 · Total Blocking Time ≤ 200ms (5/5 pts)

- Evidence: TBT 0ms
- Guidelines: [web.dev — Total Blocking Time](https://web.dev/articles/tbt)

### [PASS] S5 · First Contentful Paint ≤ 1.8s (4/4 pts)

- Evidence: FCP 414ms
- Guidelines: [web.dev — First Contentful Paint](https://web.dev/articles/fcp)

## Server response & caching: 87/100 (B) · 26/30 pts

### [PARTIAL] D1 · Time to first byte ≤ 200ms (4/8 pts)

- Evidence: TTFB 542ms 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.
- Remediation: The server rebuilds the page on every request. A page cache answers in 5–15ms.
- xSpeed fix (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](https://web.dev/articles/ttfb)

### [PASS] D2 · Page served from cache (7/7 pts)

- Evidence: Cache HIT evidence in response headers
- Guidelines: [MDN — HTTP caching](https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching)

### [PASS] D3 · HTML compression (Brotli/GZIP) (5/5 pts)

- Evidence: Content-Encoding: br
- Guidelines: [MDN — Content-Encoding](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding) · [RFC 7932 — Brotli](https://www.rfc-editor.org/rfc/rfc7932)

### [PASS] D4 · Efficient cache policy on static assets (5/5 pts)

- Evidence: Passes the Lighthouse cache-policy audit
- Guidelines: [Lighthouse — Efficient cache policy](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl)

### [PASS] D5 · CDN / edge network (3/3 pts)

- Evidence: Cloudflare detected
- Guidelines: [web.dev — Content delivery networks](https://web.dev/articles/content-delivery-networks)

### [PASS] D6 · Clean redirect chain (2/2 pts)

- Evidence: No redirects — the URL answers directly
- Guidelines: [Lighthouse — Avoid redirects](https://developer.chrome.com/docs/lighthouse/performance/redirects)

## Asset optimization: 69/100 (D) · 11/16 pts

### [FAIL] A1 · No render-blocking resources (0/5 pts)

- Evidence: Fails the Lighthouse audit — 1 file: public.css · ~150ms of first paint
- Remediation: CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
- xSpeed fix (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](https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources)

### [PASS] A2 · Minified CSS and JavaScript (4/4 pts)

- Evidence: Passes the Lighthouse audit
- Guidelines: [Lighthouse — Minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css) · [Minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript)

### [PASS] A3 · Modern, optimized image formats (4/4 pts)

- Evidence: Passes the Lighthouse audit
- Guidelines: [Lighthouse — Modern image formats](https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images)

### [INFO] A6 · LCP image discoverable early (not graded)

- Evidence: Audit not reported for this page
- Remediation: Re-run when Lighthouse is available.
- xSpeed fix (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](https://web.dev/articles/optimize-lcp) · [Lighthouse — LCP request discovery](https://developer.chrome.com/docs/lighthouse/performance/prioritize-lcp-image)

### [PASS] A5 · Total page weight ≤ 1.5MB (3/3 pts)

- Evidence: 0.2MB transferred
- Guidelines: [Lighthouse — Total byte weight](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight)

## Platform & xSpeed readiness: 100/100 (A+) · 10/10 pts

### [INFO] W1 · Platform

- Evidence: WordPress detected (WordPress 7.1.1)
- Remediation: Informational.

### [PASS] W2 · Caching plugin active (4/4 pts)

- Evidence: xSpeed Cache (xSpeed signature: v1.3.3)
- Guidelines: [WordPress.org — Optimization: caching](https://wordpress.org/documentation/article/optimization/#Caching)

### [PASS] W3 · Powered by xSpeed (4/4 pts)

- Evidence: xSpeed signature: v1.3.3
- Guidelines: [xSpeed — feature overview](https://xspeedcache.com/features) · [xSpeed vs other cache plugins](https://xspeedcache.com/comparison)

### [PASS] W4 · AI-controllable (xSpeed MCP) (2/2 pts)

- Evidence: xSpeed MCP endpoint answers at https://demo.ai2wp.site/xspeed/mcp
- Guidelines: [Model Context Protocol](https://modelcontextprotocol.io/) · [xSpeed documentation](https://xspeedcache.com/docs)

## The mobile run: 88/100 (B) · Level 4 (Fast)

Same rubric, graded on the mobile Lighthouse run (performance 98/100). Reproduce it: https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fdemo.ai2wp.site%2Freplit-pricing%2F&form_factor=mobile

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Core Web Vitals & lab metrics | 94/100 | A | 37.6/40 |
| Server response & caching | 87/100 | B | 26/30 |
| Asset optimization | 69/100 | D | 11/16 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

### Checks that differ from the desktop run

- [PASS] S1 · Lighthouse performance score (mobile) (17.6/18 pts) — 98/100 (Lighthouse 13.4.1, mobile) (desktop: PASS)
- [PASS] S2 · Largest Contentful Paint ≤ 2.5s (8/8 pts) — LCP 1.9s (desktop: PASS)
- [PARTIAL] S5 · First Contentful Paint ≤ 1.8s (2/4 pts) — FCP 1.9s (desktop: PASS)
- [PARTIAL] D1 · Time to first byte ≤ 200ms (4/8 pts) — TTFB 542ms 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. (desktop: PARTIAL)
- [FAIL] A1 · No render-blocking resources (0/5 pts) — Fails the Lighthouse audit — 1 file: public.css · ~950ms of first paint (desktop: FAIL)

## Fix everything with one prompt

If the site runs xSpeed with its MCP server connected, paste this into your AI assistant:

```
Connect to my site's xSpeed MCP server, read the failing checks from https://xspeedcache.com/scan/r/demo-ai2wp-site-983acc18f8, and apply the fixes: enable page caching, compression, minification and lazy loading, warm the cache, then run a benchmark to confirm the score improved.
```

Then re-test here: `POST https://xspeedcache.com/api/scan {"url": "https://demo.ai2wp.site/replit-pricing/"}`

## What xSpeed recommends for this site

- **xSpeed Hub**, xSpeed and its MCP are live here. Attaching the site to the Hub drives this and every sibling site from one connection. https://app.xspeedcache.com

## Scan any site yourself (free MCP)

Free, no API key. Scan any public site and get the same graded report as this one, with the fix for every failing check. These are the same tools that produced this report.

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

Or in any MCP client:

```json
{
  "mcpServers": {
    "xspeed-scan": {
      "type": "http",
      "url": "https://xspeedcache.com/scan/mcp"
    }
  }
}
```

Tools: `run_speed_scan` · `get_speed_scan` · Docs: https://xspeedcache.com/docs/scan-mcp/

No MCP client? The same scan runs from Telegram: https://t.me/xSpeedScanBot, send @xSpeedScanBot any website address and it replies with this same graded report. Free, no signup.

---
Scan demo-ai2wp-site-983acc18f8 · rubric v2026.09.5 · xSpeed Scan, https://xspeedcache.com/scan