LCP
Largest Contentful Paint
3.92 s
good ≤ 2.50 s · poor > 4.00 s
Need these fixes handled?
NY8 · technical consulting and web development — from a prioritised plan to implementation.
// the plan // checklist
75
audited: 75
grade C → C
0 of 54 fixed
0%
Tick an issue once it is fixed. Each tick counts that check as passed, and the score moves with it.
The top 3 alone would reach 80 · grade B.
Largest Contentful Paint (LCP)Core Web Vitals
Prioritise the LCP element: preload the hero image or font, remove render-blocking CSS/JS, and cut server response time.
+2.3
Consent managementPrivacy
Add a consent management platform and block trackers until the visitor opts in.
+1.6
Content Security PolicySecurity
Start with a report-only policy, fix the violations, then enforce a script-src that avoids unsafe-inline.
+1.3
after that
0 / 5 fixed
Select a module to see its checks
75/100
band 70–79
5 points to reach B
Scores are weighted across the eight categories shown in the report.
Every rule that ran, with its evidence and fix. Tick an issue as fixed and the checklist score moves with it.
// deep dive
Thresholds follow Google’s published good / needs-improvement / poor bands.
LCP
Largest Contentful Paint
3.92 s
good ≤ 2.50 s · poor > 4.00 s
INP
Interaction to Next Paint
130 ms
good ≤ 200 ms · poor > 500 ms
CLS
Cumulative Layout Shift
0.000
good ≤ 0.100 · poor > 0.250
FCP
First Contentful Paint
2.12 s
good ≤ 1.80 s · poor > 3.00 s
TTFB
Time to First Byte
818 ms
good ≤ 800 ms · poor > 1.80 s
TBT
Total Blocking Time
49 ms
good ≤ 200 ms · poor > 600 ms
generated // checks run against www.spacejam.com