Technical check group

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. The catalogue currently contains 6 checks in this group.

Operating ledgerEXAMPLE / TRACE

Example evidence, review, and verification states
State	Evidence	Owner
Observed	PerformancePage-level source retained	Audit
Reviewed	Decision recordedScope and value inspected	Human
Verified	Public response readOutcome has separate proof	System

Synthetic product illustration. It demonstrates state meaning and does not represent a customer result.

Rule catalogue

Review each condition before turning it into work.

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.

poor_largest_contentful_paint

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.

needs_improvement_largest_contentful_paint

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_cumulative_layout_shift

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_total_blocking_time

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.

poor_performance_score

Slow Response Time

Slow server response impacts user experience and SEO. Optimize server performance.

slow_response_time