Can I track Lighthouse scores over time?

Yes. NEKTIQA stores repeated Lighthouse results for each project page and shows Performance, Accessibility, Best Practices, and SEO scores in charts and dated run history.

How long is performance history available?

Compact RunSummary history is retained for 180 days. It includes category scores, LCP, CLS, FCP, TBT, and a compact issue preview. Full private Lighthouse report data is retained for 30 days.

Are mobile and desktop results combined?

No. Mobile and desktop use different Lighthouse test strategies and are filtered separately, so one environment does not distort the baseline for the other.

Is Lighthouse history the same as Core Web Vitals field data?

No. These are repeated Lighthouse lab measurements from Google PageSpeed Insights. Field data such as CrUX describes experiences collected from eligible real users and should be interpreted separately.

Can release markers prove what caused a regression?

No. A release marker records timing and notes next to a performance change. It can narrow the investigation, but timing alone does not prove that a release caused the regression.

Website performance history

Track Lighthouse scores over time

A one-off score is a snapshot. NEKTIQA keeps repeated Lighthouse results in one history, so you can see the baseline, spot a change, and open the run that needs attention.

Run a free Lighthouse test View pricing

Google PageSpeed Insights lab data · Mobile and desktop kept separate · No code to install

Analyticshttps://storefront.example

Example data

Category Score Trends

Latest Run Summary

Latest successful run

Performance

935

Accessibility

Best Practices

SEO

Agentic Browsing

2/3

Experimental

Category Score Trends

Performance trend: repeated runs turn an isolated score into a visible baseline.

7 / 30 / 90day views

180 daysof compact history

2 strategiesmobile and desktop

Why history matters

A score can move. The useful question is when — and by how much.

Lighthouse results vary between runs, and websites change between releases. A saved timeline gives each new result a baseline instead of asking your team to remember what the number used to be.

One test

A result without a reference point

Useful for diagnosing the page now, but too isolated to show whether a lower score is new, recurring, or ordinary variation.

Repeated tests

A change you can place in time

Compare like with like, follow the direction of the trend, and narrow the investigation to the runs around the change.

Every run, one record

Keep the score, the metrics, and the surrounding context together

Filter one project page by mobile or desktop and scan the same measurements across recent manual and scheduled runs.

Historyhttps://storefront.example

Example data

Manual testRelease Marker

Date	Status	Perf	SEO	A11y	Best	LCP	CLS	TBT
	Success	93	97	95	98	1980ms	0.030	100ms
	Success	88	97	95	98	2470ms	0.040	160ms
	Success	85	96	94	97	2840ms	0.050	210ms
	Success	82	96	94	97	3110ms	0.060	250ms
	Success	83	96	94	97	3020ms	0.060	240ms
	Success	77	96	93	97	3610ms	0.080	330ms
	Success	70	95	92	96	4320ms	0.100	440ms
	Success	66	95	92	96	4860ms	0.120	520ms
Aug 4, 6:00 PMv2.4.0Checkout image delivery update
	Success	87	96	93	97	2580ms	0.050	170ms
	Success	89	96	93	97	2360ms	0.040	140ms

Run history: dated scores and lab metrics stay comparable across repeated tests.

Category score trends

Follow Performance, Accessibility, Best Practices, and SEO without losing the individual result behind each point.

Lab metric history

Review LCP, CLS, FCP, and TBT alongside the category scores produced by the same Lighthouse run.

Separate device baselines

Switch between mobile and desktop history instead of treating two different test environments as one trend.

Release context

Add release markers to charts and history to record what shipped near a change, without claiming that correlation proves the cause.

Detail view • / • Desktophttps://storefront.example

Example data

93/100

Aug 17, 2026, 09:00 AM

Performance score

0-49 — critical50-89 — needs work90-100 — excellent

Performance Breakdown

A detailed view of key metrics that show how your site loads, responds, and stays stable for users.

FCP

0.9 s

34/35

LCP

2.0 s

24/25

TBT

100 ms

9/10

CLS

0.03

25/25

2.4 s

12/15

Emulated form factorDesktop

Lighthouse version13.4.1

Localeen-US

Run detail: inspect the measurements and test context behind a point in the history.

From trend to evidence

Open the run behind the change

A trend shows where to look. Open a recent result to review the performance breakdown, audit details, and environment behind that point in the timeline.

History and detail have different retention windows.

Full private reports remain available for 30 days. Compact score, metric, and issue summaries power the performance history for 180 days.

Interpret the trend honestly

Lighthouse history is lab data, not real-user monitoring

NEKTIQA runs Lighthouse through Google PageSpeed Insights in a controlled test environment. Repeating that lab test is useful for comparisons, but it is not CrUX, RUM, uptime monitoring, or direct evidence of what every visitor experienced.

See how Lighthouse monitoring works

Questions

Common questions about Lighthouse score history

Create the first reference point

Your next Lighthouse score is more useful when the first one is already saved

Run a free test now. When you are ready to build a performance history, choose a plan and keep the pages that matter on a repeatable testing rhythm.

Run a free Lighthouse test View pricing

Track Lighthouse scores over time

Latest Run Summary

A score can move. The useful question is when — and by how much.

A result without a reference point

A change you can place in time

Keep the score, the metrics, and the surrounding context together

Category score trends

Lab metric history

Separate device baselines

Release context

Performance score

Performance Breakdown

Open the run behind the change

Lighthouse history is lab data, not real-user monitoring

Common questions about Lighthouse score history

Your next Lighthouse score is more useful when the first one is already saved

Your privacy choices