A clearer picture of performance.
Follow-up run · 06 Sept 2026, 10:00 UTC · mobile
https://example.com/fictional-studio/What this tells us
This review summarizes one mobile Lighthouse navigation test of https://example.com/fictional-studio/. The imported performance score is 89/100. Largest Contentful Paint was 2.30 s. A baseline is included for a comparison of the recorded test results. Prioritize the observed audit findings, validate the cause, and repeat the test under consistent conditions. These lab results do not establish real-user experience or business impact.
The measured picture
Follow-up scores / 0–100| Lab metric | Baseline | Follow-up | Change |
|---|---|---|---|
| First Contentful PaintFCP | 2.80 s | 1.50 s | −1.30 s (46.4% lower) |
| Largest Contentful PaintLCP | 5.10 s | 2.30 s | −2.80 s (54.9% lower) |
| Speed IndexSI | 5.80 s | 2.80 s | −3.00 s (51.7% lower) |
| Total Blocking TimeTBT | 610 ms | 130 ms | −480 ms (78.7% lower) |
| Cumulative Layout ShiftCLS | 0.180 | 0.045 | −0.135 (75.0% lower) |
Missing or unsupported values are shown as “Not supplied,” never as zero. Lower values in these lab metrics generally indicate faster loading or less blocking/layout movement. Changes describe these test runs; they do not establish causation.
Matching recorded settings do not prove identical test conditions. Repeat runs and review variability before attributing a change to your work.
These are Lighthouse lab results. Field data from PageSpeed/CrUX is not included. TBT is not INP, and this report cannot establish a Core Web Vitals pass.
Where to investigate
Follow-up audit findingsUp to six flagged audits, ordered by estimated time savings when supplied, then audit score. The investigation notes below are suggested next steps.
Reduce unused JavaScript
ObservedImported audit score: 70/100. Potential savings of 94 KiB. Lighthouse estimates 220 ms of potential savings. This is a model estimate, not a promised reduction. Estimated byte savings: 94 KiB.
InvestigateInspect the trace and script ownership. Test reducing unnecessary execution; this audit alone does not establish which change is safe.
Audit: unused-javascriptEliminate render-blocking resources
ObservedImported audit score: 80/100. Potential savings of 160 ms. Lighthouse estimates 160 ms of potential savings. This is a model estimate, not a promised reduction.
InvestigateInspect critical resources and their dependencies. Test a narrow change in staging and check for rendering regressions.
Audit: render-blocking-resourcesImprove image delivery
ObservedImported audit score: 70/100. Potential savings of 76 KiB. Estimated byte savings: 76 KiB.
InvestigateInspect image dimensions, formats and loading priority. Verify which assets are on the critical rendering path before changing them.
Audit: image-delivery-insight
Your action plan
Consultant-authored prioritiesThe owner and priorities below are editorial decisions, separate from measured evidence.
- High priorityOwner: To assign
Investigate: Reduce unused JavaScript
Evidence / reference: unused-javascript - Medium priorityOwner: To assign
Investigate: Eliminate render-blocking resources
Evidence / reference: render-blocking-resources - Medium priorityOwner: To assign
Investigate: Improve image delivery
Evidence / reference: image-delivery-insight
Context & method
Baseline
- Page
- https://example.com/fictional-studio/
- Captured
- 01 Sept 2026, 10:00 UTC
- Lighthouse
- 13.0.0
- Device / mode
- mobile / navigation
- Throttling
- simulate
- Storage reset
- Enabled
Follow-up
- Page
- https://example.com/fictional-studio/
- Captured
- 06 Sept 2026, 10:00 UTC
- Lighthouse
- 13.0.0
- Device / mode
- mobile / navigation
- Throttling
- simulate
- Storage reset
- Enabled
Scope: the imported page and recorded test conditions. Lighthouse may not cover all content, routes, assistive technology needs or production behavior. Scores can vary between runs and tool versions. No ranking, conversion, revenue or score outcome is guaranteed. Confirm findings before changing production.