Frontend Web Performance

Front-end web performance is important. Sometimes it takes being on holidays in Australia, having to use wifi at a conference or bad 3G before you notice how much of the web is *really* slow for a huge amount of people. We should be doing everything we can to improve the experience, and the front-end is full of low hanging fruit.

Transcript

1. Frontend Web Performance Jonathan Cremin @Kudoz
2. Typical Factors
3. TTFB Time To First Byte
4. Weight
5. Geography
6. Where to Start?
7. Optimise your Backend
8. Gzip Everything
9. Combine and Minify
10. Optimise Images
11. CDN
12. Agressive Caching
13. Anycast DNS
14. Avoid Redirects
15. Optimise SSL
16. www.ssllabs.com/projects/best-practices www.ssllabs.com/ssltest/
17. Example
19. Unoptimised
20. Optimised — 33% Drop
21. Unoptimised, slow 3G
23. Optimised, slow 3G - 70% Drop
25. Test Test Test
26. — developers.google.com/speed/pagespeed/ — developer.yahoo.com/yslow/
27. RUM Real User Metrics
28. — pingdom.com — statuscake.com — newrelic.com — github.hubspot.com/bucky (OSS)
34. Resources Image Optimisation tool used — imageoptim.com Traffic control tool used — slowyapp.com Which is just a wrapper around tc if you're on linux — linuxmanpages.com/man8/tc.8.php