Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Lighthouse Audit History Block for Svelte

Six Lighthouse runs of one page with four scores each and, for the chosen run, the audits that newly fail, are fixed or still fail against the previous run or any other run, and bars of estimated savings.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

See what changed since the last audit with this Lighthouse history for Svelte with Ark UI. It is Glowledger, an audit history tool, keeping six typed runs of one page. A list cell shows the runs newest first: the date, the four scores (Performance, Accessibility, Best practices, SEO) and the Performance change from the run before with an arrow and a sign; on a phone the list is a select. For the chosen run the detail sorts every failing audit against a baseline, the previous run by default or any other run picked in a select: Newly failing (audits that passed there), Fixed (failed there, pass now) and Still failing, each with its category and its impact ("+420 ms", "2 elements"). Under them the performance audits' estimated savings are bars on one scale shared by all six runs. The header sentence is worked out from the newest run and the one before it ("Performance 92, down 6: 2 audits newly fail."). Guides draw the frame and its bands; the entrance is CSS only. For release reviews, regression hunts and any history that has to say why a score moved.

FAQ

How do I load my own runs?

Edit RAW, newest first: each run has an id, an ISO date, the four scores and its fails, one audit:size string per failing audit (milliseconds, elements or a CLS number, as the audit's unit in AUDITS says). The three lists, the changes, the header and the bars are all worked out from those strings.

How does the comparison work?

An audit is Newly failing if it fails in the chosen run and not in the baseline, Fixed if it failed in the baseline and passes now, and Still failing if it fails in both. The baseline is the run before by default; the select offers the other runs, so you can compare with last month's run too. The oldest run has no baseline and lists its audits as failing.

What are the savings bars?

The performance audits that fail in the chosen run, largest first, up to four. Each bar is the audit's impact in milliseconds on a scale from 0 to 800 ms shared by every run, so a smaller bar in a later run really is smaller. The number is also in text beside the name.

What stays local in the demo?

Everything. The runs are typed, nothing is audited and nothing is requested. The chosen run and baseline are local state. In your app store each run's Lighthouse result and map it to the same fields.

How does it look on a phone?

The list becomes a select with the date and Performance score, the scores sit in a two-column grid and the three lists and the bars scroll inside one region of fixed height, so choosing a run never moves the page.