# Website Speed Report, militariabuecher.com

> **What this document is.** A point-in-time speed audit of https://militariabuecher.com/de/,
> 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 (44/100,
> grade F). 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.
>
> **WordPress is detected; xSpeed is not detected.** The free plugin is one possible route when
> its capabilities fit a measured issue. Review an approved installation and its setup wizard;
> installation or activation alone does not prove caching is configured or that speed improved.
>
> 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://militariabuecher.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: 48/100. Grade F · Level 2 (Slow) — graded on the desktop run**

- Scanned: 2026-10-15T12:10:38.036Z
- Requested URL: https://militariabuecher.com/
- Final URL: https://militariabuecher.com/de/
- Requested strategy: both
- Visibility: listed; an unlisted report is still accessible to anyone holding its link
- Lighthouse analysis (desktop): 2026-10-15T12:10:17.982Z
- Report (HTML): https://xspeedcache.com/scan/r/militariabuecher-com-7e62964f08
- Report (JSON): https://xspeedcache.com/api/scan/militariabuecher-com-7e62964f08
- Rubric: v2026.10.1
- Platform: WordPress 7.1.3 · CDN: IONOS edge signal
## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 173ms |
| Lighthouse performance (desktop) — graded | 55/100 |
| Lighthouse performance (mobile) | 63/100 |
| Reproduce the desktop run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fmilitariabuecher.com%2Fde%2F&form_factor=desktop |
| Largest Contentful Paint | 2.7s |
| Cumulative Layout Shift | 0.113 |
| Total Blocking Time | 736ms |
| HTML compression | gzip (on the wire: gzip 32KB) |
| Served from cache | yes (HIT) |
| CDN edge | present, outcome not reported |
| Redirects before final URL | 1 |

## Real visitors (Chrome UX Report)

Not enough Chrome traffic for field data on this page or its site. The grade above is lab data only.

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 51/100 | F | 20.4/40 |
| Server response & caching | 78/100 | C | 21/27 |
| Asset optimization | 13/100 | F | 2/16 |
| Platform & xSpeed readiness | 0/100 | F | 0/8 |

## Lab performance (Lighthouse): 51/100 (F) · 20.4/40 pts

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

- Evidence: 55/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)

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

- Evidence: LCP 2.7s
- Suggested investigation: Serve the hero content faster: cache the page, preload the LCP image, and ship critical CSS.
- Candidate xSpeed feature (Free): **Page Cache + Preloader + LCP image preload** — verify the installed catalog and current settings first.
- Review prompt: `Review S2 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 — Largest Contentful Paint](https://web.dev/articles/lcp) · [Optimize LCP](https://web.dev/articles/optimize-lcp)

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

- Evidence: CLS 0.113
- Suggested investigation: Reserve space for images/embeds so the page does not jump as it loads.
- Candidate xSpeed feature (Free): **Lazy Load — CLS fix (adds width/height)** — verify the installed catalog and current settings first.
- Review prompt: `Review S3 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 — Cumulative Layout Shift](https://web.dev/articles/cls)

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

- Evidence: TBT 736ms
- 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 531ms
- Guidelines: [web.dev — First Contentful Paint](https://web.dev/articles/fcp)

## Server response & caching: 78/100 (C) · 21/27 pts

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

- Evidence: TTFB 173ms 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.
- 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: gzip — 32KB on the wire
- 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)

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

- Evidence: Fails the Lighthouse cache-policy audit — 8 files: fa-solid-900.woff2, robotocondensed-ff1f75d6.woff2, roboto-0f7fcdc8.woff2…
- Suggested investigation: Give CSS/JS/images long Cache-Control lifetimes so repeat views are free.
- Candidate xSpeed feature (Free): **Browser Cache** — verify the installed catalog and current settings first.
- Review prompt: `Review D4 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 — Efficient cache policy](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl)

### [INFO] D5 · CDN edge serves the page (not graded)

- Evidence: IONOS edge signal detected, but its headers do not say whether it served this page from the edge.
- Suggested investigation: 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](https://web.dev/articles/content-delivery-networks)

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

- Evidence: 1 redirect(s) before the final URL: 301→https://militariabuecher.com/de/
- Suggested investigation: Each redirect adds a full round-trip before the page can even start.
- Guidelines: [Lighthouse — Avoid redirects](https://developer.chrome.com/docs/lighthouse/performance/redirects)

## Asset optimization: 13/100 (F) · 2/16 pts

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

- Evidence: Fails the Lighthouse audit — 4 files: main.min.js, she-header.js, jquery.min.js (c0.wp.com)… · ~150ms of first paint
- Suggested investigation: Inline the critical CSS and defer the rest. Note that 2 of these come from another host, so deferring them is the only lever you have.
- 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)

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

- Evidence: Lighthouse audit score 50% — 4 files: fontawesome.css, jsonrepair.js, she-header.js…
- Suggested investigation: Ship minified assets — whitespace and comments are pure transfer waste.
- Candidate xSpeed feature (Free): **HTML/CSS/JS Minify** — verify the installed catalog and current settings first.
- Review prompt: `Review A2 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 — Minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css) · [Minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript)

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

- Evidence: Fails the Lighthouse audit — 1 file: Logo-Militaria-Buecher-hell-1.png (i0.wp.com) · ~50ms of first paint
- Suggested investigation: Every image flagged here is served from another host (i0.wp.com), so converting them is not yours to do — the fix is to host them yourself, or load fewer.
- 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)

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

- Evidence: Audit not reported for this page
- Suggested investigation: Re-run when Lighthouse is available.
- Candidate xSpeed feature (Free): **Resource Hints (preload) + Lazy Load exclusions** — verify the installed catalog and current settings first.
- Review prompt: `Review A6 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 — Optimize LCP](https://web.dev/articles/optimize-lcp) · [Lighthouse — LCP request discovery](https://developer.chrome.com/docs/lighthouse/performance/prioritize-lcp-image)

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

- Evidence: 2.1MB transferred — over 1,500KB
- 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** — verify the installed catalog and current settings first.
- What Pro adds: **Image Converter (WebP/AVIF)** (up to 1 more pts) — only if xSpeed Pro is active.
- 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: 0/100 (F) · 0/8 pts

### [INFO] W1 · Platform

- Evidence: WordPress detected (WordPress 7.1.3)
- Suggested investigation: Informational.

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

- Evidence: No caching plugin detected
- Suggested investigation: WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
- Candidate xSpeed feature (Free): **xSpeed Cache (free on wordpress.org)** — verify the installed catalog and current settings first.
- Review prompt: `Review W2 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: [WordPress.org — Optimization: caching](https://wordpress.org/documentation/article/optimization/#Caching)

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

- Evidence: xSpeed not detected
- 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)

### [INFO] W4 · xSpeed MCP route response not confirmed (not graded)

- Evidence: This scan did not confirm an xSpeed MCP route response. 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: 44/100 (F) · Level 2 (Slow)

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

Lighthouse analysis: 2026-10-15T12:10:16.984Z; replayed: no.

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 47/100 | F | 18.8/40 |
| Server response & caching | 78/100 | C | 21/27 |
| Asset optimization | 0/100 | F | 0/16 |
| Platform & xSpeed readiness | 0/100 | F | 0/8 |

### Checks that differ from the desktop run

- [PARTIAL] S1 · Lighthouse performance score (mobile) (11.3/18 pts) — 63/100 (Lighthouse 13.5.0, mobile) (desktop: PARTIAL)
- [FAIL] S2 · Largest Contentful Paint ≤ 2.5s (0/8 pts) — LCP 11.9s (desktop: PARTIAL)
- [PASS] S3 · Cumulative Layout Shift ≤ 0.1 (5/5 pts) — CLS 0.000 (desktop: PARTIAL)
- [PARTIAL] S4 · Total Blocking Time ≤ 200ms (2.5/5 pts) — TBT 277ms (desktop: FAIL)
- [FAIL] S5 · First Contentful Paint ≤ 1.8s (0/4 pts) — FCP 3.0s (desktop: PASS)
- [PASS] D1 · Time to first byte ≤ 200ms (8/8 pts) — TTFB 173ms 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 14ms from its own network — the gap between the two numbers is distance, not your server. (desktop: PASS)
- [FAIL] A1 · No render-blocking resources (0/5 pts) — Fails the Lighthouse audit — 4 files: she-header.js, main.min.js, jquery-migrate.min.js (c0.wp.com)… · ~300ms of first paint (desktop: FAIL)
- [FAIL] A2 · Minified CSS and JavaScript (0/4 pts) — Fails the Lighthouse audit — 4 files: fontawesome.css, jsonrepair.js, she-header.js… (desktop: PARTIAL)
- [FAIL] A3 · Modern, optimized image formats (0/4 pts) — Fails the Lighthouse audit — 1 file: regal-mit-buechern.png (i0.wp.com) · ~1.9s of first paint (desktop: FAIL)
- [FAIL] A5 · Total page weight (≤ 350KB for full marks) (0/3 pts) — 1764KB transferred — over 1,500KB (desktop: FAIL)

## 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/militariabuecher-com-7e62964f08.md for requested URL https://militariabuecher.com/ and final URL https://militariabuecher.com/de/, selected desktop device, scanned 2026-10-15T12:10:38.036Z, 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://militariabuecher.com/","visibility":"listed","strategy":"both","fresh":true}`

## Optional product routes, not measured diagnoses or approval

- **xSpeed Cache (free)** — review suitability and current configuration before choosing a product. https://wordpress.org/plugins/xspeed/

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