# Website Speed Report, easy.jobs

> **What this document is.** A point-in-time speed audit of https://easy.jobs/,
> 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 (45/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 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: WordPress, xSpeed not installed.**
> 1) Install the free xSpeed Cache plugin (https://wordpress.org/plugins/xspeed/) and run
> its setup wizard. That alone turns most of this report green.
> 2) Connect its MCP server: `wp xspeed mcp connect` (or wp-admin → xSpeed → MCP Server →
> Connect) and paste the URL into the AI client.
> 3) Run the per-check prompts below: or the one-shot prompt at the end: then 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: 58/100. Grade D · Level 2 (Slow) — graded on the desktop run**

- Scanned: 2026-09-20T07:26:02.335Z
- Report (HTML): https://xspeedcache.com/scan/r/easy-jobs-bcdc8f2d2f
- Report (JSON): https://xspeedcache.com/api/scan/easy-jobs-bcdc8f2d2f
- Rubric: v2026.09.4
- Platform: ThinkRank 2.5.0
## Headline measurements

| Metric | Value |
|---|---|
| Time to first byte | 119ms |
| Lighthouse performance (desktop) — graded | 68/100 |
| Lighthouse performance (mobile) | 49/100 |
| Reproduce the desktop run | https://pagespeed.web.dev/analysis?url=https%3A%2F%2Feasy.jobs%2F&form_factor=desktop |
| Largest Contentful Paint | 1.5s |
| Cumulative Layout Shift | 0.197 |
| Total Blocking Time | 283ms |
| HTML compression | br |
| Served from cache | no (MISS) |
| Redirects before final URL | 0 |

## Dimension scores

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Core Web Vitals & lab metrics | 73/100 | C | 29.2/40 |
| Server response & caching | 88/100 | B | 17.5/20 |
| Asset optimization | 20/100 | F | 4/20 |
| Platform & xSpeed readiness | 0/100 | F | 0/8 |

## Core Web Vitals & lab metrics: 73/100 (C) · 29.2/40 pts

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

- Evidence: 68/100 (Lighthouse 13.4.1, desktop)
- 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)

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

- Evidence: LCP 1.5s
- 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.197
- 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)

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

- Evidence: TBT 283ms
- Remediation: Less JavaScript on the main thread: defer scripts and drop unused bundles.
- xSpeed fix (Free): **JS Minify + Defer**
- AI prompt: `Using my site's xSpeed MCP connection: enable JS minification and deferred loading, then re-test Total Blocking Time.`
- Guidelines: [web.dev — Total Blocking Time](https://web.dev/articles/tbt)

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

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

## Server response & caching: 88/100 (B) · 17.5/20 pts

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

- Evidence: TTFB 119ms measured from Vilnius, Lithuania (EU) (best of 2 requests). This includes the network round trips between us and your origin, not just server time.
- Guidelines: [web.dev — Time to First Byte](https://web.dev/articles/ttfb)

### [NA] D2 · Page served from cache (not graded)

- Evidence: Correctly per-visitor — this response is marked `no-cache, no-store, must-revalidate`, so it must not be held in a shared cache.
- Remediation: Nothing to fix. If parts of this page are the same for everyone, they can still be cached separately — but the page as a whole is right to opt out.
- 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)

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

- Evidence: Lighthouse cache-policy audit score 50% — 2 files: easy.jobs-hero-section-video-1.webm, a (googletagmanager.com)
- Remediation: Give your CSS/JS/images long Cache-Control lifetimes. One of these is served by another host, so that part will not clear.
- xSpeed fix (Free): **Browser Cache**
- AI prompt: `Using my site's xSpeed MCP connection: enable browser-cache headers for static assets, then re-run the 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: 20/100 (F) · 4/20 pts

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

- Evidence: Fails the Lighthouse audit — 8 files: jquery-migrate.min.js, flexia-core-public.js, jquery.min.js… · ~900ms 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)

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

- Evidence: Fails the Lighthouse audit — 1 file: embedpress.css
- Remediation: Ship minified assets — whitespace and comments are pure transfer waste.
- xSpeed fix (Free): **HTML/CSS/JS Minify**
- AI prompt: `Using my site's xSpeed MCP connection: enable HTML, CSS and JS minification, purge the cache, and re-test.`
- 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 — 4 files: Frame-2147240334-2.png, WPDeveloper-BG1-1-scaled-1.png, round.png… · ~50ms of first paint
- Remediation: Serve WebP/AVIF at the right compression — usually the single largest byte saving.
- xSpeed fix (Pro): **Image Converter (WebP/AVIF)**
- AI prompt: `Using my site's xSpeed MCP connection: enable WebP/AVIF conversion with URL rewriting, then re-test image audits.`
- 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)

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

- Evidence: 4.1MB transferred
- Remediation: Heavy pages are slow on every connection — compress, lazy-load, and trim.
- xSpeed fix (Free): **Minify + Lazy Load + Image Converter (Pro)**
- AI prompt: `Using my site's xSpeed MCP connection: enable minification and lazy loading (and image conversion on Pro), then re-check page weight.`
- 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 (ThinkRank 2.5.0)
- Remediation: Informational.

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

- Evidence: No caching plugin detected
- Remediation: WordPress rebuilds every page in PHP unless a caching plugin serves it statically.
- xSpeed fix (Free): **xSpeed Cache (free on wordpress.org)**
- AI prompt: `Install and activate the xSpeed plugin from wordpress.org, run its setup wizard, and enable page caching.`
- Guidelines: [WordPress.org — Optimization: caching](https://wordpress.org/documentation/article/optimization/#Caching)

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

- Evidence: xSpeed not detected
- Remediation: xSpeed bundles caching, minification, lazy-load, image optimization and an AI-controllable MCP server in one plugin — and imports settings from other caching plugins in one click.
- xSpeed fix (Free): **xSpeed Migration (one-click import)**
- AI prompt: `Install xSpeed and use its Migration tool to import your current caching settings, then deactivate the old plugin.`
- Guidelines: [xSpeed — feature overview](https://xspeedcache.com/features) · [xSpeed vs other cache plugins](https://xspeedcache.com/comparison)

### [INFO] W4 · AI-controllable (xSpeed MCP) (not graded)

- Evidence: xSpeed MCP endpoint not reachable
- Remediation: Optional: connect xSpeed's built-in MCP server and your AI assistant can apply every fix in this report for you.
- xSpeed fix (Free): **MCP Server (built into xSpeed Free)**
- AI prompt: `In xSpeed → MCP Server, click Connect and paste the config into your AI client — then ask it to fix this report.`
- Guidelines: [Model Context Protocol](https://modelcontextprotocol.io/) · [xSpeed documentation](https://xspeedcache.com/docs)

## The mobile run: 45/100 (F) · Level 2 (Slow)

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

| Dimension | Score | Grade | Points |
|---|---|---|---|
| Core Web Vitals & lab metrics | 41/100 | F | 16.3/40 |
| Server response & caching | 88/100 | B | 17.5/20 |
| Asset optimization | 30/100 | F | 6/20 |
| Platform & xSpeed readiness | 0/100 | F | 0/8 |

### Checks that differ from the desktop run

- [FAIL] S1 · Lighthouse performance score (mobile) (8.8/18 pts) — 49/100 (Lighthouse 13.4.1, mobile) (desktop: PARTIAL)
- [FAIL] S2 · Largest Contentful Paint ≤ 2.5s (0/8 pts) — LCP 12.8s (desktop: PASS)
- [PASS] S3 · Cumulative Layout Shift ≤ 0.1 (5/5 pts) — CLS 0.006 (desktop: PARTIAL)
- [PARTIAL] S4 · Total Blocking Time ≤ 200ms (2.5/5 pts) — TBT 341ms (desktop: PARTIAL)
- [FAIL] S5 · First Contentful Paint ≤ 1.8s (0/4 pts) — FCP 8.1s (desktop: PASS)
- [PARTIAL] D4 · Efficient cache policy on static assets (2.5/5 pts) — Lighthouse cache-policy audit score 50% — 1 file: easy.jobs-hero-section-video-1.webm (desktop: PARTIAL)
- [FAIL] A1 · No render-blocking resources (0/5 pts) — Fails the Lighthouse audit — 8 files: flexia-core-public.js, element.js, jquery.min.js… · ~6.0s of first paint (desktop: FAIL)
- [PARTIAL] A2 · Minified CSS and JavaScript (2/4 pts) — Lighthouse audit score 50% — 1 file: embedpress.css (desktop: FAIL)
- [FAIL] A3 · Modern, optimized image formats (0/4 pts) — Fails the Lighthouse audit — 4 files: Frame-2147240334-2.png, WPDeveloper-BG1-1-scaled-1.png, round-1-768x767.png… · ~300ms of first paint (desktop: FAIL)
- [FAIL] A5 · Total page weight ≤ 1.5MB (0/3 pts) — 4.0MB transferred (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/easy-jobs-bcdc8f2d2f, 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://easy.jobs/"}`

## What xSpeed recommends for this site

- **xSpeed Cache (free)**, WordPress with no xSpeed detected. The free plugin plus its setup wizard turns most of the failing checks in this report green. 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 easy-jobs-bcdc8f2d2f · rubric v2026.09.4 · xSpeed Scan, https://xspeedcache.com/scan