Core Web Vitals for Sportsbooks: A Technical Checklist

Sportsbooks are among the heaviest pages on the web. Between live odds updates, betslip state, personalisation scripts and affiliate tracking, hitting 'good' Core Web Vitals on field data is genuinely hard — but the commercial payoff is real, and Google does apply it as a tiebreaker.

The usual suspects

• LCP: hero banners and carousel images served unoptimised, often through a CMS that adds render-blocking markup
• INP: odds-tick WebSocket updates re-rendering large DOM trees, and heavy main-thread JS during interaction
• CLS: dynamically injected odds boosts, banners and cookie/consent layers that shift layout on load

The checklist we run

• Audit third-party scripts by main-thread cost; defer or facade everything non-critical
• Reserve layout space for every dynamic module — odds cells, boosts, banners
• Serve hero images with fetchpriority=high and preload; kill the carousel
• Move odds updates to targeted DOM patches, not full component re-renders
• Measure with CrUX/RUM data by page template, not Lighthouse on the homepage

The sportsbooks that fix this don't just satisfy a Google metric — faster event pages convert meaningfully better in the minutes before kick-off, when traffic is densest.