speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

wordpress.com

https://wordpress.com/

60 86 73 100 AXE CWV

Data from Aug 25, 2026, 1:51 PM UTC 6h old

Overall #1,463 Website Builders #8 · 1 measurement · since Aug 25, 2026

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

WordPress Built with WordPress
Self-hosted · nginx Hosted by Self-hosted

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-27 → 2026-08-23). This is what Google measures you on.

LCP 5.63 s poor
INP 248 ms needs-improvement
CLS 0.020 good

Scores

60
Performance
no change
86
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.96 s 4.96 s 4.96 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 600 ms 600 ms 600 ms
FCP First Contentful Paint 3.16 s 3.16 s 3.16 s
Speed Index 3.16 s 3.16 s 3.16 s
TTFB Time to First Byte 611 ms 611 ms 611 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 4.96 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 115 ms
time to first byte 25 ms
resource load duration 18 ms
resource load delay 11 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-27 → 2026-08-23). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 5.63 s poor 43% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 248 ms needs-improvement 66.6% good
CLS CWV 0.020 good 88.3% good
FCP 1.73 s good 76.6% good
TTFB 994 ms needs-improvement 64.9% good

Lab vs field

Lab LCP 4.96 s · field p75 5.63 s · real users are 1.14× slower than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-22 5.62 s 248 ms 0.030 1.73 s 994 ms
2026-08-15 5.53 s 245 ms 0.030 1.71 s 979 ms
2026-08-08 5.44 s 239 ms 0.040 1.69 s 966 ms
2026-08-01 5.37 s 236 ms 0.040 1.66 s 951 ms
2026-07-25 5.35 s 230 ms 0.050 1.63 s 939 ms
2026-07-18 5.41 s 229 ms 0.040 1.63 s 937 ms
2026-07-11 5.42 s 228 ms 0.040 1.63 s 933 ms
2026-07-04 5.44 s 228 ms 0.040 1.63 s 930 ms
2026-06-27 5.45 s 228 ms 0.040 1.64 s 939 ms
2026-06-20 5.45 s 230 ms 0.040 1.61 s 924 ms
2026-06-13 5.45 s 229 ms 0.040 1.58 s 899 ms
2026-06-06 5.45 s 228 ms 0.040 1.56 s 874 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.85 MB 1.85 MB 1.85 MB
Requests 68 68 68
Third-party Weight 730 kB 730 kB 730 kB
Third-party CPU 276 ms 276 ms 276 ms
Unused JS 328 kB 328 kB 328 kB
Unused CSS 43.1 kB 43.1 kB 43.1 kB

By resource type

script 879 kB · 27 req
image 458 kB · 27 req
font 380 kB · 2 req
document 69.6 kB · 2 req
stylesheet 55.9 kB · 4 req
other 7.7 kB · 6 req
third party 1.82 MB · 62 req

Third parties 10 entities

730 kB transferred, 276 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Tag Manager 330 kB · 133 ms CPU
Facebook 186 kB · 82 ms CPU
Other Google APIs/SDKs 99.2 kB · 9 ms CPU
Hotjar 64.8 kB · 25 ms CPU
Parse.ly 21.8 kB · 11 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.37 s 3.37 s 3.37 s
Long Tasks 9 9 9
DOM Elements 1,433 1,433 1,433
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 10 10 10
A11y Failures 5 5 5
A11y Failing Nodes 10 10 10

Main thread work

style layout 1.37 s
script evaluation 1.25 s
other 361 ms
script parse compile 244 ms
parse HTML 74 ms
paint composite render 41 ms
garbage collection 38 ms

Axe violations axe-core 4.13.0, full rule set

10 violating nodes across 6 rules, 1295 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 3 nodes
  • serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 2 nodes
  • minor presentation-role-conflict — Elements marked as presentational should be consistently ignored 2 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 1 node
  • serious label-title-only — Form elements should have a visible label 1 node
  • critical label — Form elements must have labels 1 node

Accessibility failures 5 of 33 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • aria-allowed-attr — `[aria-*]` attributes do not match their roles 3 nodes
  • aria-prohibited-attr — Elements use prohibited ARIA attributes 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 2 nodes
  • presentation-role-conflict — Elements with `role="none"` or `role="presentation"` have conflicts 2 nodes
  • label — Form elements do not have associated labels 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 25, 2026, 1:51 PM UTC 60 4.96 s 0 600 ms 1.85 MB 3/3 ±4 3,230 30.6s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show wordpress.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://wordpress.com/"></speedlify2-score>