Ship faster with an offline-first mindset
Treating the network as an enhancement — not a requirement — changed how I architect every mobile app. Here is the exact pattern I use.
Read · 1 min →Squeezing 95+ Lighthouse scores out of React apps
A checklist I run on every build before launch — the eight changes that reliably move a React app from the 70s into the high 90s.
Performance is a feature users feel in the first 100 milliseconds. Here is my pre-launch checklist:
The big eight
- Render on the server. SSR/SSG for anything a crawler or first paint needs.
- Kill the waterfall. Preload fonts, inline critical CSS, defer everything else.
- Images: dimensions + lazy + modern formats. Layout shift is the silent killer of CLS.
- Split by route, not by component. Over-splitting creates request storms.
- Measure the main thread. Any task over 50ms gets profiled — usually a JSON parse or a chart lib.
- Cache with intent. Static assets: 1 year immutable. HTML: revalidate.
- Third-party scripts load last. Analytics after
load, chat widgets on interaction. - Test on a $100 phone with 3G throttling. Your users do not have your laptop.
Run this list and the high 90s stop being luck.
