# 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.5.0, 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 (71/100,
> grade C). 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 xSpeed assessment.
> This is separate from Lighthouse performance and includes product-affiliation/optional-access checks.
> Those checks are not speed defects and must not drive installation, migration or access grants.
> Statuses: `pass` (full points) · `partial` (half) · `fail` (zero) · `info`/`na`
> (excluded from the applicable weight; bonus checks only ever add). Every non-passing
> check retains its evidence and references. Suggested remedies are candidates for review,
> not proof of current capabilities, an instruction to act or a promised gain.
>
> **Access and permission.** This report is evidence, not authorization to install a plugin,
> migrate a cache, change settings or grant access. Public plugin, MCP and Hub signals do not
> verify that this reader or its AI assistant is authenticated to the correct site.
> Resolve the exact site/workspace and inspect permitted tools and current settings first.
> Explain each proposed change and obtain approval before applying it.
>
> **xSpeed is detected (v1.3.6).** Do not install it again.
> Inspect its current configuration and measured cache behavior before proposing a change.
> The public xSpeed MCP route returned an unauthenticated challenge; client authentication and control were not tested.
> A public Hub attachment signal was reported. Verify account authorization and exact site access; do not assume control of this or sibling sites.
>
> Connection guide: https://xspeedcache.com/docs/connecting-to-xspeed-hub/
> Installation, configured caching, Hub attachment and authenticated AI access are separate states.
> Server-side HTML verification cannot execute JavaScript. Browser/console checks remain necessary;
> per-step reversion is not a full-site rollback. No target score is guaranteed.
> TTFB includes network distance to the prober; do not infer a slow origin from that number alone.
>
> **How to re-test.** Public API (no auth): `POST https://xspeedcache.com/api/scan`
> with body `{"url":"https://embedpress.com/","visibility":"listed","strategy":"both","fresh":true}`, then poll `GET /api/scan/{scanId}` for the
> JSON report. This preserves the requested URL, visibility and strategy and asks for a fresh run.
> Unlisted reports remain accessible to anyone holding their link. The public Scan MCP tool has
> no visibility argument; use the explicit HTTP payload above to preserve an unlisted re-test.
> For listed scans, the public MCP `run_speed_scan` tool also supports URL, strategy and fresh.
> Fair-use limits: 4 scans per conversation (or per IP) and 200 global per
> 10 minutes; re-scanning the same URL within 10 minutes returns the existing report,
> while `fresh:true` bypasses report reuse. Google may still replay a Lighthouse analysis; compare timestamps.
>
> **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: 78/100. Grade C · Level 4 (Fast) — graded on the desktop run**

- Scanned: 2026-10-01T16:47:44.879Z
- Requested URL: https://embedpress.com/
- Final URL: https://embedpress.com/
- Requested strategy: both
- Visibility: listed; an unlisted report is still accessible to anyone holding its link
- Lighthouse analysis (desktop): 2026-10-01T16:47:18.091Z
- Report (HTML): https://xspeedcache.com/scan/r/embedpress-com-3199a463a6
- Report (JSON): https://xspeedcache.com/api/scan/embedpress-com-3199a463a6
- Rubric: v2026.10.1
- Platform: WordPress 7.1.2 · xSpeed Cache v1.3.6 + Pro v1.2.7 · xSpeed MCP reported available (authentication not tested) · public Hub signal reported (access unverified)
## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 446ms |
| Lighthouse performance (desktop) — graded | 68/100 |
| Lighthouse performance (mobile) | 73/100 |
| Reproduce the desktop run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fembedpress.com%2F&form_factor=desktop |
| Largest Contentful Paint | 1.1s |
| Cumulative Layout Shift | 0.004 |
| Total Blocking Time | 842ms |
| HTML compression | br (on the wire: gzip 70KB, br 69KB) |
| Served from cache | yes (HIT) |
| Redirects before final URL | 0 |

## Real visitors (Chrome UX Report)

Field data for desktop Chrome users, 75th percentile, this page. **Fails Core Web Vitals.** This is what Google ranks on; the lab grade above is a single Lighthouse run.

| Metric | p75 | Verdict |
|---|---|---|
| Largest Contentful Paint | 2.7s | needs-improvement |
| Interaction to Next Paint | 54ms | good |
| Cumulative Layout Shift | 0.06 | good |

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 73/100 | C | 29.2/40 |
| Server response & caching | 85/100 | B | 23/27 |
| Asset optimization | 68/100 | D | 13.5/20 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

## Lab performance (Lighthouse): 73/100 (C) · 29.2/40 pts

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

- Evidence: 68/100 (Lighthouse 13.5.0, desktop)
- Suggested investigation: The composite Lighthouse score — every fix below moves it.
- Candidate xSpeed feature (Free): **AI Optimize** — verify the installed catalog and current settings first.
- Review prompt: `Review S1 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- 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 1.1s
- 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.004
- Guidelines: [web.dev — Cumulative Layout Shift](https://web.dev/articles/cls)

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

- Evidence: TBT 842ms
- Suggested investigation: Less JavaScript on the main thread: defer scripts and drop unused bundles.
- Candidate xSpeed feature (Free): **JS Minify + Defer** — verify the installed catalog and current settings first.
- Review prompt: `Review S4 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- Guidelines: [web.dev — Total Blocking Time](https://web.dev/articles/tbt)

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

- Evidence: FCP 681ms
- 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 446ms 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 176ms from its own network — the gap between the two numbers is distance, not your server.
- Suggested investigation: Compare response timing with server-reported time and a probe near the audience. Inspect cache evidence before changing the origin; network distance is included in TTFB.
- Candidate xSpeed feature (Free): **Page Cache** — verify the installed catalog and current settings first.
- Review prompt: `Review D1 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- 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 (bytes on the wire) (5/5 pts)

- Evidence: Content-Encoding: br — 69KB on the wire (gzip would be 70KB)
- 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 serves the page (not graded)

- Evidence: No CDN signature detected
- Suggested investigation: Optional: put a CDN or Cloudflare in front for global edge delivery.
- Candidate xSpeed feature (Free): **Cloudflare integration / CDN rewriter** — verify the installed catalog and current settings first.
- Review prompt: `Review D5 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- 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: 68/100 (D) · 13.5/20 pts

### [PARTIAL] A1 · No render-blocking resources (2.5/5 pts)

- Evidence: Lighthouse audit score 50% — 3 files: jquery-migrate.min.js, jquery.min.js, 77720e06378e61b9a0e1367aa2bcf58c.js
- Suggested investigation: CSS/JS in <head> blocks first paint. Inline the critical CSS and defer the rest.
- Candidate xSpeed feature (Pro): **Critical CSS + Unused CSS removal** — verify the installed catalog and current settings first.
- Review prompt: `Review A1 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- 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)

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

- Evidence: Lighthouse audit score 50% — 2 files: Container.png, c9e0e191-vector-smart-object@2x.png
- Suggested investigation: Serve WebP/AVIF at the right compression — usually the single largest byte saving.
- Candidate xSpeed feature (Pro): **Image Converter (WebP/AVIF)** — verify the installed catalog and current settings first.
- Review prompt: `Review A3 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- Guidelines: [Lighthouse — Modern image formats](https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images)

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

- Evidence: Passes the Lighthouse audit
- 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)

### [PARTIAL] A5 · Total page weight (≤ 350KB for full marks) (1/3 pts)

- Evidence: 1474KB transferred — heavy: most WordPress pages this size fail mobile LCP
- Suggested investigation: 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.
- Candidate xSpeed feature (Free): **Minify + Lazy Load + Image Converter (Pro)** — verify the installed catalog and current settings first.
- Review prompt: `Review A5 for this exact URL and device. Inspect current configuration and authorized tool access. Explain a safe reversible remedy and ask before applying it. Re-test afterward and report improvement, regression or unavailable evidence honestly.`
- 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.2)
- Suggested investigation: Informational.

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

- Evidence: xSpeed Cache (xSpeed signature: v1.3.6 + Pro v1.2.7)
- 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.6 + Pro v1.2.7
- Interpretation: product affiliation or optional connectivity, not a measured speed defect. No installation, migration or access grant is required by this check.
- Guidelines: [xSpeed — feature overview](https://xspeedcache.com/features) · [xSpeed vs other cache plugins](https://xspeedcache.com/comparison)

### [PASS] W4 · xSpeed MCP route responded (2/2 pts)

- Evidence: The public xSpeed MCP route returned its expected unauthenticated challenge. This confirms route responsiveness only; client authentication and control were not tested.
- Interpretation: product affiliation or optional connectivity, not a measured speed defect. No installation, migration or access grant is required by this check.
- Guidelines: [Model Context Protocol](https://modelcontextprotocol.io/) · [xSpeed documentation](https://xspeedcache.com/docs)

## The mobile run: 71/100 (C) · Level 3 (Average)

Same rubric, graded on the mobile Lighthouse run (performance 73/100). Reproduce it: https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fembedpress.com%2F&form_factor=mobile

Lighthouse analysis: 2026-10-01T16:47:17.772Z; replayed: no.

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 58/100 | D | 23.1/40 |
| Server response & caching | 85/100 | B | 23/27 |
| Asset optimization | 65/100 | D | 13/20 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

### Checks that differ from the desktop run

- [PARTIAL] S1 · Lighthouse performance score (mobile) (13.1/18 pts) — 73/100 (Lighthouse 13.5.0, mobile) (desktop: PARTIAL)
- [FAIL] S2 · Largest Contentful Paint ≤ 2.5s (0/8 pts) — LCP 5.0s (desktop: PASS)
- [PASS] S3 · Cumulative Layout Shift ≤ 0.1 (5/5 pts) — CLS 0.000 (desktop: PASS)
- [PASS] S4 · Total Blocking Time ≤ 200ms (5/5 pts) — TBT 26ms (desktop: FAIL)
- [FAIL] S5 · First Contentful Paint ≤ 1.8s (0/4 pts) — FCP 3.6s (desktop: PASS)
- [PARTIAL] D1 · Time to first byte ≤ 200ms (4/8 pts) — TTFB 446ms 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 183ms 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 — 3 files: 77720e06378e61b9a0e1367aa2bcf58c.js, jquery-migrate.min.js, jquery.min.js · ~250ms of first paint (desktop: PARTIAL)
- [PASS] A3 · Modern, optimized image formats (4/4 pts) — Passes the Lighthouse audit (desktop: PARTIAL)
- [PARTIAL] A5 · Total page weight (≤ 350KB for full marks) (1/3 pts) — 1245KB transferred — heavy: most WordPress pages this size fail mobile LCP (desktop: PARTIAL)

## Review a fix plan before applying changes

Copy this brief only after checking the report URL and device. It does not authorize changes:

```
Review https://xspeedcache.com/scan/r/embedpress-com-3199a463a6.md for requested URL https://embedpress.com/ and final URL https://embedpress.com/, selected desktop device, scanned 2026-10-01T16:47:44.879Z, rubric 2026.10.1. Preserve both devices and analysis timestamps. Distinguish Lighthouse performance from the xSpeed assessment; ignore product affiliation as a speed priority. Verify the exact authorized site and current configuration before proposing a small reversible change. Ask before applying changes. Do not assume optimize_site accepts a scan ID or report URL. Its HTML checks are not browser verification or a full rollback. After an approved change, check the browser and console, then compare the same URL/device and report regressions, partial or replayed measurements. Do not promise 100.
```

Then re-test here: `POST https://xspeedcache.com/api/scan {"url":"https://embedpress.com/","visibility":"listed","strategy":"both","fresh":true}`

## 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-3199a463a6 · rubric v2026.10.1 · xSpeed Scan, https://xspeedcache.com/scan