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 ·

2019.nejsconf.com

https://2019.nejsconf.com/

92 94 100 100 CWV 12AXE

Data from Aug 20, 2026, 3:36 PM UTC — 27h old.

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

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

92
Performance
no change
94
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 3.31 s 3.31 s 3.31 s
CLS Cumulative Layout Shift 0.059 0.059 0.059
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 816 ms 816 ms 816 ms
Speed Index 816 ms 816 ms 816 ms
TTFB Time to First Byte 609 ms 609 ms 609 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.

element render delay 98 ms
resource load duration 30 ms
resource load delay 29 ms
time to first byte 10 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 490.4 kB 490.4 kB 490.4 kB
Requests 32 32 32
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 400.1 kB · 26 req
font 77.4 kB · 3 req
script 7.0 kB · 1 req
document 3.9 kB · 1 req
stylesheet 2.0 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 536 ms 536 ms 536 ms
Long Tasks 1 1 1
DOM Elements 228 228 228
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 12 12 12
A11y Failures 2 2 2
A11y Failing Nodes 2 2 2

Main thread work

other 281 ms
style layout 164 ms
paint composite render 43 ms
script evaluation 35 ms
parse HTML 10 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 4 rules, 556 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 9 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node

Accessibility failures 2 of 14 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.

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • 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, 3:36 PM UTC 92 3.31 s 0.059 0 ms 490.4 kB 3/3 ±8 2,344 25s

Embed this score

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