LCP
Largest Contentful Paint
651 ms
good ≤ 2.50 s · poor > 4.00 s
- scanned
- duration
- 696 ms
- requests
- ≈1
- page weight
- 0 B
- ttfb
- 138 ms
https://cnn.com/
Page title
Need these fixes handled?
NY8 · technical consulting and web development — from a prioritised plan to implementation.
- Failed
- 28
- Warnings
- 15
- Passed
- 80
- Checks
- 124
// the plan // checklist
The plan, as a checklist
75
audited: 75
grade C → C
0 of 43 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 79 · grade C.
Start here
the biggest gains, largest first0 / 3 fixed- 1
Page titleSEO
Add a unique title of 50–60 characters that leads with the primary keyword and includes the brand.
+1.7
- 2
Privacy policy linkPrivacy
Publish a privacy policy and link it from the site footer.
+1.5
- 3
Responsive viewportMobile & UX
Set <meta name="viewport" content="width=device-width, initial-scale=1">.
+1.3
after that
0 / 5 fixed
- Security header coverage across site surfacesSecurity+1.2
- Content Security PolicySecurity+1.2
- Text compressionPerformance+1.2
- H1 headingSEO+1.0
- Mobile viewportSEO+1.0
Module scores
Select a module to see its checks
Grade band
C
75/100
band 70–79
5 points to reach B
F0–59
D60–69
C70–79
B80–89
A90–94
A+95–100
Scores are weighted across the eight categories shown in the report.
All checks
Every rule that ran, with its evidence and fix. Tick an issue as fixed and the checklist score moves with it.
// deep dive
Measurements and evidence
Core Web Vitals
Thresholds follow Google’s published good / needs-improvement / poor bands.
INP
Interaction to Next Paint
110 ms
good ≤ 200 ms · poor > 500 ms
CLS
Cumulative Layout Shift
0.000
good ≤ 0.100 · poor > 0.250
FCP
First Contentful Paint
471 ms
good ≤ 1.80 s · poor > 3.00 s
TTFB
Time to First Byte
138 ms
good ≤ 800 ms · poor > 1.80 s
TBT
Total Blocking Time
0 ms
good ≤ 200 ms · poor > 600 ms
generated // checks run against cnn.com