webdriver.io

Data from Aug 23, 2026, 6:30 PM UTC 3h old

Test Runners #9 · 3 measurements · since Aug 21, 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.

Built with Docusaurus 3.9.2

Hosted by Amazon S3

Core Web Vitals field data, url-level

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

LCP 2.02 s good

INP 225 ms needs-improvement

CLS 0.010 good

Scores

Performance

↑ +2 (+5.1%)

Accessibility

no change

Best Practices

no change

100

SEO

no change

Filmstrip Lighthouse, mobile

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

492 ms
984 ms
1.48 s
1.97 s
2.46 s
2.95 s
3.44 s
3.94 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	15.10 s	21.36 s	↓ -6258 ms (-29.3%) significant	15.10 s	21.36 s
CLS Cumulative Layout Shift	0.093	0.002	↑ +0.091 (+4550%) significant	0.002	0.093
TBT Total Blocking Time	795 ms	891 ms	↓ -96 ms (-10.8%)	795 ms	930 ms
FCP First Contentful Paint	4.89 s	4.48 s	↑ +403 ms (+9%)	4.48 s	4.94 s
Speed Index	4.89 s	6.92 s	↓ -2030 ms (-29.3%)	4.89 s	6.92 s
TTFB Time to First Byte	605 ms	607 ms	↓ -2 ms (-0.3%)	603 ms	607 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

15.10 s

21.36 s

↓ -6258 ms (-29.3%) significant

15.10 s

21.36 s

CLS Cumulative Layout Shift

0.093

0.002

↑ +0.091 (+4550%) significant

0.002

0.093

TBT Total Blocking Time

795 ms

891 ms

↓ -96 ms (-10.8%)

795 ms

930 ms

FCP First Contentful Paint

4.89 s

4.48 s

↑ +403 ms (+9%)

4.48 s

4.94 s

Speed Index

4.89 s

6.92 s

↓ -2030 ms (-29.3%)

4.89 s

6.92 s

TTFB Time to First Byte

605 ms

607 ms

↓ -2 ms (-0.3%)

603 ms

607 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 15.10 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 346 ms

time to first byte 40 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	2.02 s	good	81.7% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	225 ms	needs-improvement	71.2% good
CLS CWV	0.010	good	96.1% good
FCP	1.75 s	good	77.1% good
TTFB	615 ms	good	83.4% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.02 s

good

81.7% good

INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run

225 ms

needs-improvement

71.2% good

CLS CWV

0.010

good

96.1% good

FCP

1.75 s

good

77.1% good

TTFB

615 ms

good

83.4% good

Lab vs field

Lab LCP 15.10 s · field p75 2.02 s · real users are 0.13× faster than the lab.

Field history 25 weeks

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

Week ending	LCP	INP	CLS	FCP	TTFB
2026-08-15	2.07 s	252 ms	0.020	1.79 s	591 ms
2026-08-08	2.11 s	277 ms	0.010	1.79 s	570 ms
2026-08-01	2.19 s	186 ms	0.010	2.03 s	655 ms
2026-07-25	1.98 s	186 ms	0.010	1.71 s	510 ms
2026-07-18	2.13 s	171 ms	0.010	1.76 s	529 ms
2026-07-11	2.13 s	188 ms	0.010	1.76 s	514 ms
2026-07-04	2.17 s	195 ms	0.010	1.76 s	527 ms
2026-06-27	2.24 s	194 ms	0.010	1.94 s	764 ms
2026-06-20	1.93 s	239 ms	0.010	1.66 s	725 ms
2026-06-13	1.91 s	256 ms	0.010	1.72 s	689 ms
2026-06-06	1.95 s	256 ms	0.010	1.78 s	689 ms
2026-05-30	1.94 s	274 ms	0.010	1.65 s	505 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

2.07 s

252 ms

0.020

1.79 s

591 ms

2026-08-08

2.11 s

277 ms

0.010

1.79 s

570 ms

2026-08-01

2.19 s

186 ms

0.010

2.03 s

655 ms

2026-07-25

1.98 s

186 ms

0.010

1.71 s

510 ms

2026-07-18

2.13 s

171 ms

0.010

1.76 s

529 ms

2026-07-11

2.13 s

188 ms

0.010

1.76 s

514 ms

2026-07-04

2.17 s

195 ms

0.010

1.76 s

527 ms

2026-06-27

2.24 s

194 ms

0.010

1.94 s

764 ms

2026-06-20

1.93 s

239 ms

0.010

1.66 s

725 ms

2026-06-13

1.91 s

256 ms

0.010

1.72 s

689 ms

2026-06-06

1.95 s

256 ms

0.010

1.78 s

689 ms

2026-05-30

1.94 s

274 ms

0.010

1.65 s

505 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	11.43 MB	11.43 MB	↑ +7.4 kB (+0.1%)	11.43 MB	11.43 MB
Requests	191	190	↑ +1 (+0.5%)	190	191
Third-party Weight	5.26 MB	5.26 MB	↑ +2.2 kB	5.26 MB	5.26 MB
Third-party CPU	118 ms	130 ms	↓ -13 ms (-9.7%) significant	118 ms	132 ms
Unused JS	1.01 MB	1.01 MB	↓ -703 B (-0.1%)	1.01 MB	1.01 MB
Unused CSS	72.8 kB	72.8 kB	→ no change	72.8 kB	72.8 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

11.43 MB

↑ +7.4 kB (+0.1%)

11.43 MB

Requests

191

190

↑ +1 (+0.5%)

190

191

Third-party Weight

5.26 MB

↑ +2.2 kB

5.26 MB

Third-party CPU

118 ms

130 ms

↓ -13 ms (-9.7%) significant

118 ms

132 ms

Unused JS

1.01 MB

↓ -703 B (-0.1%)

1.01 MB

Unused CSS

72.8 kB

→ no change

72.8 kB

By resource type

image 7.86 MB · 137 req

script 3.12 MB · 18 req

stylesheet 177 kB · 5 req

document 141 kB · 2 req

font 95.2 kB · 4 req

other 34.0 kB · 19 req

third party 6.36 MB · 131 req

Third parties 6 entities

5.26 MB transferred, 118 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

GitHub 4.80 MB · 2 ms CPU

Unpkg 204 kB · 39 ms CPU

Google Tag Manager 172 kB · 63 ms CPU

Google Fonts 62.4 kB · 0 ms CPU

Google Analytics 21.9 kB · 14 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	5.18 s	5.43 s	↓ -241 ms (-4.4%)	5.15 s	5.43 s
Long Tasks	11	13	↓ -2 (-15.4%)	11	13
DOM Elements	1,187	1,187	→ no change	1,187	1,187
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	54	54	→ no change	54	54
A11y Failures	4	4	→ no change	4	4
A11y Failing Nodes	107	108	↓ -1 (-0.9%)	107	108

Main thread work

script evaluation 2.06 s

other 1.64 s

style layout 776 ms

paint composite render 336 ms

script parse compile 318 ms

parse HTML 43 ms

garbage collection 14 ms

Axe violations axe-core 4.13.0, full rule set

54 violating nodes across 9 rules, 2266 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.

serious color-contrast — Elements must meet minimum color contrast ratio thresholds 45 nodes
moderate heading-order — Heading levels should only increase by one 2 nodes
critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
serious aria-prohibited-attr — Elements must only use permitted ARIA attributes 1 node
critical button-name — Buttons must have discernible text 1 node
serious frame-title — Frames must have an accessible name 1 node
moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 4 of 27 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.

target-size — Touch targets do not have sufficient size or spacing. 61 nodes
color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 43 nodes
heading-order — Heading elements are not in a sequentially-descending order 2 nodes
frame-title — `<frame>` or `<iframe>` elements do not have a title 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

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	Perf	LCP	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 6:30 PM UTC	41	15.10 s	0.093	795 ms	11.43 MB	3/3	±1	2,482	53.5s
Aug 22, 2026, 5:24 PM UTC	39	21.36 s	0.002	891 ms	11.43 MB	3/3	±6	2,289	53s
Aug 21, 2026, 5:12 PM UTC	40	21.34 s	0.002	930 ms	11.43 MB	3/3	±8	2,490	54.4s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 6:30 PM UTC

15.10 s

0.093

795 ms

11.43 MB

3/3

±1

2,482

53.5s

Aug 22, 2026, 5:24 PM UTC

21.36 s

0.002

891 ms

11.43 MB

3/3

±6

2,289

53s

Aug 21, 2026, 5:12 PM UTC

21.34 s

0.002

930 ms

11.43 MB

3/3

±8

2,490

54.4s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show webdriver.io'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://webdriver.io/"></speedlify2-score>