Digibury: SciVisum - Making your website fast - and scalable
1 like402 views
The document discusses strategies for enhancing website speed and scalability, highlighting issues like network latency, bulky images, and third-party scripts as common culprits of slow performance. It emphasizes the importance of user experience, continuous performance testing, and the limitations of cloud auto-scaling in addressing these challenges. Practical resources and tools for web performance monitoring are also recommended.
Digibury: SciVisum - Making your website fast - and scalable
- 1. Deri Jones Making your website fast - and scalable Jan 14 2015 #Digibury @Digibury @SciVisum_Ltd
- 2. Tue Feb 3rd
- 3. Website Speed ● Black Friday and Xmas peaks
- 5. The Need for Speed ● Impatience ● SEO
- 6. The Need for Speed ● Impatience ● SEO ● UX is the final USP
- 8. What makes sites slow ?
- 9. Network effects ●ADSL 3G 4G
- 10. Latency
- 11. Latency targets ● Backbone best: ● Local: − ADSL 25 mS − Mobile 250 mS
- 12. Network effects ●Bulky: Images ●Too many objects ●Not using HTTP Keep alive
- 17. The offender: ● <script src="http://3rdparty.com/script.js"></script>
- 18. Old solution These days <script async defer src="siteScript.js" onload="myInit()"></script> These days:
- 19. Browser effects ●Objects block ●Rendering time ●3rd party blocking
- 20. Ad serving is slow And no political motive to be faster Will get slower as big-Data progresses
- 21. Responsive web Avoid the Whitehouse.org story...
- 22. Can be good: ●Painless install ●Many configuration choices Can be tricky: ●Embedded CSS obsession
- 23. Tools ● Firebug, DevTools ● HTTPArchive.org ● Webpagetest.org
- 25. Challenges ● Responsive web: − Better than 2 sites www. and m.
- 27. Website Scaling
- 28. Surprising lessons ● Cloud auto-scaling – doesn't work
- 29. Surprising lessons Cloud auto-scaling – doesn't work − Scales too late − Allows rest of farm to die − Small print: − Strictly 'very often' doesn't work
- 30. Surpising lessons ● Cloud auto-scaling – doesn't work − Scales too late − Allows rest of farm to die
- 31. ● Cloud auto-scaling ● Uncertain spin-up time ● DOA
- 32. ● Scaling ● Don't obsess Disk IO − Yes it's moving metal − Web is a lot about static content
- 33. ● Scaling ● The code platforms are good ● Many problems in SysAdmin configs ● CDNs − Cache-Miss hurts ● But don't assume!
- 34. ● Scaling ● Many big hosters: − Not motivated to help you
- 35. ● Scaling
- 36. Users' Experience It's both: ●The new battleground ●A challenge − Single Page website − Offline-cache content − Users' journeys complexity
- 37. User Experience ● Cultural shift − Make every one responsible for it! ● Performance is a deliverable − Test every release − Continuous Integration
- 38. User Experience ● Hard ● Easier to save timings in your code − ElasticSearch, Graphite ● RUM and Analytics help
- 39. User Experience ● 'Do what your Customers do' − more Synthetic monitoring − For another day ...
- 40. Making your website fast - and scalable Deri Jones Digibury January 2015
- 41. Resources ● London Web performance meetup − http://www.meetup.com/London-Web-Performance-Group ● Third Party Footprints − http://www.slideshare.net/bbinto/third-party-footprint-evaluating-the-performance-of-external-scripts ● HTTP Archive − https://speakerdeck.com/deanohume/the-good-the-bad-and-the-ugly-of-the-http-archive