speedlify2

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

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

2018.nejsconf.com

https://2018.nejsconf.com/

76 98 100 100 –CWV 13AXE

Data from Aug 20, 2026, 4:24 PM UTC — 26h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 26h

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.

Netlify Hosted by Netlify

Scores

76
Performance
no change
98
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 7.68 s — — 7.68 s 7.68 s
CLS Cumulative Layout Shift 0.010 — — 0.010 0.010
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 826 ms — — 826 ms 826 ms
Speed Index 826 ms — — 826 ms 826 ms
TTFB Time to First Byte 634 ms — — 634 ms 634 ms

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.

resource load duration 172 ms
time to first byte 35 ms
element render delay 24 ms
resource load delay 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.57 MB — — 1.57 MB 1.57 MB
Requests 28 — — 28 28
Third-party Weight 84.6 kB — — 84.6 kB 84.6 kB
Third-party CPU 1 ms — — 1 ms 1 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 1.48 MB · 23 req
font 77.4 kB · 3 req
script 7.0 kB · 1 req
document 6.6 kB · 1 req
third party 84.6 kB · 5 req

Third parties 1 entities

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

Adobe TypeKit 84.6 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 422 ms — — 422 ms 422 ms
Long Tasks 0 — — 0 0
DOM Elements 233 — — 233 233
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 13 — — 13 13
A11y Failures 1 — — 1 1
A11y Failing Nodes 1 — — 1 1

Main thread work

other 208 ms
style layout 117 ms
paint composite render 47 ms
script evaluation 34 ms
parse HTML 12 ms
script parse compile 4 ms

Axe violations axe-core 4.13.0, full rule set

13 violating nodes across 2 rules, 511 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 12 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 22 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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 4:24 PM UTC 76 7.68 s 0.010 0 ms 1.57 MB 3/3 ±1 2,486 25.6s

Embed this score

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