dsev.dk
Data from Aug 21, 2026, 5:36 PM UTC 2d old
Built Awesome #1,060 · 1 measurement · since Aug 21, 2026
https://dsev.dk/.
Lighthouse follows the redirect, so the numbers below describe the destination page, not this one. Not yet confirmed as a move; it needs to lead to the same place on several consecutive runs first.
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.
Scores
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 5.74 s | — | — | 5.74 s | 5.74 s | |
| CLS Cumulative Layout Shift | 0.183 | — | — | 0.183 | 0.183 | |
| TBT Total Blocking Time | 78 ms | — | — | 78 ms | 78 ms | |
| FCP First Contentful Paint | 3.66 s | — | — | 3.66 s | 3.66 s | |
| Speed Index | 3.66 s | — | — | 3.66 s | 3.66 s | |
| TTFB Time to First Byte | 605 ms | — | — | 605 ms | 605 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 5.74 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.
Page weight
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Page Weight | 987 kB | — | — | 987 kB | 987 kB | |
| Requests | 29 | — | — | 29 | 29 | |
| Third-party Weight | 454 kB | — | — | 454 kB | 454 kB | |
| Third-party CPU | 270 ms | — | — | 270 ms | 270 ms | |
| Unused JS | 412 kB | — | — | 412 kB | 412 kB | |
| Unused CSS | 21.3 kB | — | — | 21.3 kB | 21.3 kB |
By resource type
Third parties 7 entities
454 kB transferred, 270 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 1.85 s | — | — | 1.85 s | 1.85 s | |
| Long Tasks | 7 | — | — | 7 | 7 | |
| DOM Elements | 597 | — | — | 597 | 597 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 9 | — | — | 9 | 9 | |
| A11y Failures | 3 | — | — | 3 | 3 | |
| A11y Failing Nodes | 8 | — | — | 8 | 8 |
Main thread work
Axe violations axe-core 4.13.0, full rule set
9 violating nodes across 4 rules, 389 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 4 nodes -
serious
aria-hidden-focus— ARIA hidden element must not be focusable or contain focusable elements 3 nodes -
critical
button-name— Buttons must have discernible text 1 node -
moderate
landmark-unique— Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
Accessibility failures 3 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.
-
color-contrast— Background and foreground colors do not have a sufficient contrast ratio. 4 nodes -
aria-hidden-focus— `[aria-hidden="true"]` elements contain focusable descendents 3 nodes -
button-name— Buttons do not have an accessible name 1 node
Hygiene
Changes rarely — which is exactly why a change is worth noticing.
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, 5:36 PM UTC | 62 | 5.74 s | 0.183 | 78 ms | 987 kB | 3/3 | ±10 | 2,430 | 33.2s |
Embed this score
Live below, then the markup that produces it. Drop that on any page to show
dsev.dk'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://www.dsev.dk/"></speedlify2-score>