embl.org

https://www.embl.org/

Data from Aug 21, 2026, 11:42 AM UTC — 7h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 7h

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.

Hosted by Self-hosted

Core Web Vitals field data, url-level

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

LCP 2.66 s needs-improvement

INP 97 ms good

CLS 0.160 needs-improvement

Scores

Performance

no change

Accessibility

no change

Best Practices

no change

100

SEO

no change

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	3.64 s	—	—	3.64 s	3.64 s
CLS Cumulative Layout Shift	1.041	—	—	1.041	1.041
TBT Total Blocking Time	70 ms	—	—	70 ms	70 ms
FCP First Contentful Paint	2.42 s	—	—	2.42 s	2.42 s
Speed Index	3.68 s	—	—	3.68 s	3.68 s
TTFB Time to First Byte	1.28 s	—	—	1.28 s	1.28 s

What LCP is made of

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

time to first byte 899 ms

resource load delay 236 ms

resource load duration 55 ms

element render delay 32 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	2.66 s	needs-improvement	71.7% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	97 ms	good	93.7% good
CLS CWV	0.160	needs-improvement	68.2% good
FCP	1.97 s	needs-improvement	70.7% good
TTFB	1.18 s	needs-improvement	60% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.66 s

needs-improvement

71.7% good

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

97 ms

good

93.7% good

CLS CWV

0.160

needs-improvement

68.2% good

FCP

1.97 s

needs-improvement

70.7% good

TTFB

1.18 s

needs-improvement

60% good

Lab vs field

Lab LCP 3.64 s · field p75 2.66 s · real users are 0.73× 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.65 s	96 ms	0.150	1.91 s	1.13 s
2026-08-08	2.54 s	94 ms	0.140	1.82 s	1.08 s
2026-08-01	2.52 s	91 ms	0.130	1.76 s	1.05 s
2026-07-25	2.49 s	89 ms	0.120	1.74 s	1.09 s
2026-07-18	2.49 s	90 ms	0.130	1.75 s	1.10 s
2026-07-11	2.54 s	89 ms	0.140	1.83 s	1.15 s
2026-07-04	2.57 s	90 ms	0.150	1.84 s	1.16 s
2026-06-27	2.56 s	90 ms	0.160	1.86 s	1.10 s
2026-06-20	2.53 s	92 ms	0.160	1.86 s	1.06 s
2026-06-13	2.49 s	92 ms	0.150	1.73 s	1.01 s
2026-06-06	2.53 s	95 ms	0.160	1.88 s	1.14 s
2026-05-30	2.56 s	96 ms	0.160	1.90 s	1.19 s

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

2.65 s

96 ms

0.150

1.91 s

1.13 s

2026-08-08

2.54 s

94 ms

0.140

1.82 s

1.08 s

2026-08-01

2.52 s

91 ms

0.130

1.76 s

1.05 s

2026-07-25

2.49 s

89 ms

0.120

1.74 s

1.09 s

2026-07-18

2.49 s

90 ms

0.130

1.75 s

1.10 s

2026-07-11

2.54 s

89 ms

0.140

1.83 s

1.15 s

2026-07-04

2.57 s

90 ms

0.150

1.84 s

1.16 s

2026-06-27

2.56 s

90 ms

0.160

1.86 s

1.10 s

2026-06-20

2.53 s

92 ms

0.160

1.86 s

1.06 s

2026-06-13

2.49 s

92 ms

0.150

1.73 s

1.01 s

2026-06-06

2.53 s

95 ms

0.160

1.88 s

1.14 s

2026-05-30

2.56 s

96 ms

0.160

1.90 s

1.19 s

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	2.11 MB	—	—	2.11 MB	2.11 MB
Requests	34	—	—	34	34
Third-party Weight	619.7 kB	—	—	619.7 kB	619.7 kB
Third-party CPU	69 ms	—	—	69 ms	69 ms
Unused JS	76.5 kB	—	—	76.5 kB	76.5 kB
Unused CSS	19.7 kB	—	—	19.7 kB	19.7 kB

By resource type

image 1.45 MB · 13 req

font 316.9 kB · 4 req

script 236.4 kB · 3 req

other 63.4 kB · 11 req

stylesheet 24.0 kB · 1 req

document 6.8 kB · 1 req

third party 604.2 kB · 12 req

Third parties 7 entities

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

cloudimg.io 391.7 kB · 0 ms CPU

Google Tag Manager 190.8 kB · 62 ms CPU

Cloudflare CDN 19.1 kB · 7 ms CPU

emblstatic.net 16.3 kB · 0 ms CPU

GitHub 702 B · 0 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	843 ms	—	—	843 ms	843 ms
Long Tasks	2	—	—	2	2
DOM Elements	342	—	—	342	342
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	45	—	—	45	45
A11y Failures	1	—	—	1	1
A11y Failing Nodes	1	—	—	1	1

Main thread work

script evaluation 283 ms

other 269 ms

style layout 160 ms

script parse compile 65 ms

paint composite render 44 ms

parse HTML 22 ms

Axe violations axe-core 4.13.0, full rule set

45 violating nodes across 3 rules, 536 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.

moderate region — All page content should be contained by landmarks 43 nodes
moderate landmark-one-main — Document should have one main landmark 1 node
moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 of 17 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.

landmark-one-main — Document does not have a main landmark. 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 21, 2026, 11:42 AM UTC	61	3.64 s	1.041	70 ms	2.11 MB	3/3	±23	2,494	37.7s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 21, 2026, 11:42 AM UTC

3.64 s

1.041

70 ms

2.11 MB

3/3

±23

2,494

37.7s

Embed this score

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

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://www.embl.org/"></speedlify-score>