Built for 2G and slow networks
Most cricket sites send megabytes of ads and scripts before you see the score. This site sends the score first. Here are the measured numbers, not marketing ones.
Score readable after
36 KB
Full T20 scorecard: HTML, CSS and JS, compressed
Lighthouse performance (mobile)
99/100
Match centre, simulated slow 4G
Works offline
Yes
Last saved scores, clearly marked
Measured results
| Page | Performance | First paint | Largest paint | HTML |
|---|---|---|---|---|
| Match centre (full T20 scorecard with ball by ball) | 99 | 1.4 s | 1.7 s | 21.7 KB |
| Home page | 96 | 1.8 s | 2.5 s | 12.9 KB |
Measured 30 October 2026 on the live site with Lighthouse 12.8 (mobile: simulated slow 4G, 4× slower CPU). Shared files, cached after the first visit: CSS 10.2 KB, JavaScript 3.9 KB, Inter font 47.8 KB. Google Analytics is loaded after the page has finished loading and is not counted above.
How it stays light
- Server-rendered pages. The score, scorecard, ball-by-ball and graphs arrive as plain HTML. Graphs are SVG drawn on the server, so there is no chart library to download.
- Small live updates. While a match is live the page refreshes only the parts that change, every 15 seconds, and pauses when you switch tabs.
- No ads, no ad scripts. Nothing competes with the score for your bandwidth.
- Offline copy. A service worker keeps the pages you opened, so a dropped signal at the ground does not mean a blank screen.
- One font, from this site. No extra connections to font services before the page can draw.
Questions
Does Cricket Match Scorecard work on 2G?
Yes. A full match scorecard needs about 36 KB before the score is readable, small enough to load on 2G and weak 3G networks. The font (47.8 KB) loads in the background and is cached after the first visit.
Does it work offline?
Pages you have opened are saved on your phone. If the network drops, you see the last saved scores with a note saying they are not live, and they update when you reconnect.
How much data does following a live match use?
Live updates re-download only the page, about 20 KB compressed, every 15 seconds while a match is live, and stop when the tab is in the background. Following a 3-hour T20 with the screen on uses roughly 15 MB.