# Website Speed Report, embedpress.com

> **What this document is.** A point-in-time speed audit of https://embedpress.com/,
> 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, mobile).
>
> **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, attached to xSpeed Hub.**
> 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.
> The site is attached to xSpeed Hub (https://app.xspeedcache.com), so one Hub MCP connection can drive this and every sibling site, including run_speed_scan for the re-test.
>
> **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: 60/100. Grade D · Level 3 (Average) — graded on the mobile run**

- Scanned: 2026-09-18T16:34:21.124Z
- Report (HTML): https://xspeedcache.com/scan/r/embedpress-com-6e164aa3f6
- Report (JSON): https://xspeedcache.com/api/scan/embedpress-com-6e164aa3f6
- Rubric: v2026.09.2
- Platform: Site Kit by Google 1.187.0 · xSpeed Cache v1.3.3 + Pro v1.2.3 · xSpeed MCP endpoint live · attached to xSpeed Hub
## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 386ms |
| Lighthouse performance (desktop) | 98/100 |
| Lighthouse performance (mobile) — graded | 53/100 |
| Reproduce the mobile run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fembedpress.com%2F&form_factor=mobile |
| Largest Contentful Paint | 5.9s |
| Cumulative Layout Shift | 0.386 |
| Total Blocking Time | 52ms |
| HTML compression | br |
| Served from cache | yes (HIT) |
| Redirects before final URL | 0 |

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Core Web Vitals & lab metrics | 36/100 | F | 14.5/40 |
| Server response & caching | 85/100 | B | 23/27 |
| Asset optimization | 55/100 | D | 11/20 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

## Core Web Vitals & lab metrics: 36/100 (F) · 14.5/40 pts

### [PARTIAL] S1 · Lighthouse performance score (mobile) (9.5/18 pts)

- Evidence: 53/100 (Lighthouse 13.4.1, mobile)
- Remediation: The composite Lighthouse score — every fix below moves it.
- xSpeed fix (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](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring)

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

- Evidence: LCP 5.9s
- Remediation: Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
- xSpeed fix (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](https://web.dev/articles/lcp) · [Optimize LCP](https://web.dev/articles/optimize-lcp)

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

- Evidence: CLS 0.386
- Remediation: Reserve space for images/embeds so the page does not jump as it loads.
- xSpeed fix (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](https://web.dev/articles/cls)

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

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

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

- Evidence: FCP 3.2s
- Remediation: First paint is gated on server response and render-blocking CSS.
- xSpeed fix (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](https://web.dev/articles/fcp)

## Server response & caching: 85/100 (B) · 23/27 pts

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

- Evidence: TTFB 386ms 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 252ms 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)

### [INFO] D5 · CDN / edge network (not graded)

- Evidence: No CDN signature detected
- Remediation: Optional: put a CDN or Cloudflare in front for global edge delivery.
- xSpeed fix (Free): **Cloudflare integration / CDN rewriter**
- AI prompt: `Using my site's xSpeed MCP connection: connect Cloudflare (or configure the CDN rewriter) and purge, then re-scan.`
- 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: 55/100 (D) · 11/20 pts

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

- Evidence: Fails the Lighthouse audit — 8 files: v4-shims.min.js, fadeInRight.min.css, jquery.min.js… · ~4.0s 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)

### [FAIL] A6 · LCP image discoverable early (0/4 pts)

- Evidence: Fails the Lighthouse audit
- Remediation: The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
- 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: 1.0MB 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 (Site Kit by Google 1.187.0)
- Remediation: Informational.

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

- Evidence: xSpeed Cache (xSpeed signature: v1.3.3 + Pro v1.2.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 + Pro v1.2.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://embedpress.com/xspeed/mcp
- Guidelines: [Model Context Protocol](https://modelcontextprotocol.io/) · [xSpeed documentation](https://xspeedcache.com/docs)

## 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/embedpress-com-6e164aa3f6, 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://embedpress.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 embedpress-com-6e164aa3f6 · rubric v2026.09.2 · xSpeed Scan, https://xspeedcache.com/scan