Technical checks
Performance checks
Google treats LCP over 4 seconds as poor. The usual causes are an oversized hero image, render-blocking CSS, or a slow server response. You’ll find 6 checks in this group.
| State | Evidence | Owner |
|---|---|---|
| Found | PerformanceOriginal page and available evidence recorded | Audit |
| Reviewed | Decision recordedA person checked the target and proposed value | Human |
| Checked | Public page readLive result recorded separately | Netrix |
All checks in this group
Open a check to see what triggered it and what to do next.
Poor Largest Contentful Paint
Google treats LCP over 4 seconds as poor. The usual causes are an oversized hero image, render-blocking CSS, or a slow server response.
Slow Largest Contentful Paint
Google's "good" threshold for LCP is 2.5 seconds. This page is past it but not yet in the poor band.
Poor Cumulative Layout Shift
Content jumping as the page loads. Most often images or ads with no reserved space — declaring width and height fixes the common case.
Poor Total Blocking Time
Long JavaScript tasks block the main thread, so the page looks ready but does not respond to taps or clicks.
Poor Performance Score
Lighthouse scores under 50 are "poor". Work the individual Core Web Vitals findings on this page rather than chasing the score itself.
Slow Response Time
Slow server response impacts user experience and SEO. Optimize server performance.