# Website Speed Report, proactivepersonnel.net

> **What this document is.** A point-in-time speed audit of https://proactivepersonnel.net/,
> 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 (50/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.
>
> **xSpeed is detected (v1.4.2).** 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.
>
> 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://proactivepersonnel.net/","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: 72/100. Grade C · Level 3 (Average) — graded on the desktop run**

- Scanned: 2026-10-13T15:03:14.079Z
- Requested URL: https://proactivepersonnel.net/
- Final URL: https://proactivepersonnel.net/
- Requested strategy: both
- Visibility: listed; an unlisted report is still accessible to anyone holding its link
- Lighthouse analysis (desktop): 2026-10-13T15:02:25.281Z
- Report (HTML): https://xspeedcache.com/scan/r/proactivepersonnel-net-66978baf5b
- Report (JSON): https://xspeedcache.com/api/scan/proactivepersonnel-net-66978baf5b
- Rubric: v2026.10.1
- Platform: WordPress 7.1.3 · xSpeed Cache v1.4.2 · xSpeed MCP reported available (authentication not tested) · CDN: Cloudflare
## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 149ms |
| Lighthouse performance (desktop) — graded | 89/100 |
| Lighthouse performance (mobile) | 48/100 |
| Reproduce the desktop run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fproactivepersonnel.net%2F&form_factor=desktop |
| Largest Contentful Paint | 1.8s |
| Cumulative Layout Shift | 0.000 |
| Total Blocking Time | 96ms |
| HTML compression | br (on the wire: gzip 49KB, br 49KB) |
| Served from cache | yes (HIT) |
| CDN edge | passed this page through to the origin |
| Redirects before final URL | 0 |

## Real visitors (Chrome UX Report)

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

| Metric | p75 | Verdict |
|---|---|---|
| Largest Contentful Paint | 1.1s | good |
| Interaction to Next Paint | 59ms | good |
| Cumulative Layout Shift | 0.00 | good |

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 95/100 | A | 38/40 |
| Server response & caching | 81/100 | B | 22/27 |
| Asset optimization | 0/100 | F | 0/20 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

## Lab performance (Lighthouse): 95/100 (A) · 38/40 pts

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

- Evidence: 89/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.8s
- 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 96ms
- Guidelines: [web.dev — Total Blocking Time](https://web.dev/articles/tbt)

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

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

## Server response & caching: 81/100 (B) · 22/27 pts

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

- Evidence: TTFB 149ms 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 7ms 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: br — 49KB on the wire (gzip would be 49KB)
- 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: Clients.jpg, icofont.woff2, On-Site-Images-3.png…
- 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: Cloudflare forwarded this request upstream (`cf-cache-status: DYNAMIC`).
- Suggested investigation: Let Cloudflare cache HTML for visitors who are not logged in: a Cache Rule set to "Eligible for cache" that bypasses the logged-in, cart and comment cookies. The edge then answers pages near the visitor instead of sending each one to your server.
- Candidate xSpeed feature (Free): **Cloudflare integration** — 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: 0/100 (F) · 0/20 pts

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

- Evidence: Fails the Lighthouse audit — 8 files: fontawesome.min.css, gravity-forms-theme-framework.min.css, solid.min.css… · ~950ms of first paint
- 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)

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

- Evidence: Fails the Lighthouse audit — 3 files: embedpress.css, icofont.css, trace.js (app.usetrace.io)
- Suggested investigation: Ship minified assets. Note that one of these comes from another host and is not yours to minify — that part of the audit will not clear.
- 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 — 3 files: Clients.jpg, On-Site-Images-3.png, proactive-personnel-logo.png · ~150ms of first paint
- 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)

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

- Evidence: Fails the Lighthouse audit
- Suggested investigation: The largest image must be in the HTML and preloaded — never lazy-loaded or script-injected.
- 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: 5.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 + 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.3)
- Suggested investigation: Informational.

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

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

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

- Evidence: X-XSpeed-Cache: BYPASS
- 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: 50/100 (F) · Level 2 (Slow)

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

Lighthouse analysis: 2026-10-13T15:01:25.839Z; replayed: no.

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Lab performance (Lighthouse) | 40/100 | F | 16.1/40 |
| Server response & caching | 81/100 | B | 22/27 |
| Asset optimization | 0/100 | F | 0/20 |
| Platform & xSpeed readiness | 100/100 | A+ | 10/10 |

### Checks that differ from the desktop run

- [FAIL] S1 · Lighthouse performance score (mobile) (8.6/18 pts) — 48/100 (Lighthouse 13.5.0, mobile) (desktop: PARTIAL)
- [FAIL] S2 · Largest Contentful Paint ≤ 2.5s (0/8 pts) — LCP 24.2s (desktop: PASS)
- [PARTIAL] S4 · Total Blocking Time ≤ 200ms (2.5/5 pts) — TBT 351ms (desktop: PASS)
- [FAIL] S5 · First Contentful Paint ≤ 1.8s (0/4 pts) — FCP 8.3s (desktop: PASS)
- [FAIL] A1 · No render-blocking resources (0/5 pts) — Fails the Lighthouse audit — 8 files: post-1432.css, mSupport-main.css, style.min.css… · ~8.0s of first paint (desktop: FAIL)
- [FAIL] A5 · Total page weight (≤ 350KB for full marks) (0/3 pts) — 4.6MB 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/proactivepersonnel-net-66978baf5b.md for requested URL https://proactivepersonnel.net/ and final URL https://proactivepersonnel.net/, selected desktop device, scanned 2026-10-13T15:03:14.079Z, 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://proactivepersonnel.net/","visibility":"listed","strategy":"both","fresh":true}`

## Optional product routes, not measured diagnoses or approval

- **xSpeed Hub** — review suitability and current configuration before choosing a product. 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 proactivepersonnel-net-66978baf5b · rubric v2026.10.1 · xSpeed Scan, https://xspeedcache.com/scan