Building quick apps in 2018
summary
Web performance drives conversions so aim to render meaningful content within 1 second / 40 KB (average slow 3G ≈ 50 KB/s, two thirds of users on 2/3G) and keep time-to-interactive under about 5–15 seconds (users lose attention ≈10s). Use concrete tools: run Lighthouse or Lighthouse CI for metrics, adopt Next.js for SSR, automatic code-splitting and prefetching, extract critical CSS with critical or CSS-in-JS server-side extraction, prefetch bundles via webpack/workbox, and front resources with Cloudflare or Netlify to cut TTFMP and TTI.
AI-written summary · about
chapters (8)
- 0:00Why performance matters
- 1:53Key performance metrics
- 3:28Targeting performance goals
- 6:43Optimizing meaningful paint
- 17:25Resource preloading
- 26:21Improving interactivity
- 35:17Maintaining long-term speed
- 37:54Q&A and final thoughts
related talks
23mPerformance Optimizations for Progressive Web Apps
39mFrom make it work to make it fast: quick wins to boost your application
45mBuilding Web Apps That Don’t Suck
01h 04mNeed for speed 8, performance tuning of your web application
01h 03mSpeed up your Web Application
26mDon't Make Users Wait: Secrets to Supercharge Server-Rendered Page
31mWe're All Doing the Best We Can
32mPractical Performance Tips Building Progressive Web Apps