Web Performance Made Simple(medium.com) |
Web Performance Made Simple(medium.com) |
2: HTML
3: OK, add some images if needed. Links if possible, inline only if absolutely necessary.
4: If you really want the thing to load fast, inline styles as well.
5: Only use scripting if there is no other way to achieve what you want to achieve.
6: ...but maybe you want to achieve something which your users would be better off without?
This is one of the reasons, why at Baqend we opted for a different approach: by using Service Workers, we can make sure that as a service provider we will only see public data. Personally identifiable information like cookies and sensitive session information does not leave the user's browser. And if you think about it that makes a lot of sense, since the public data really is what makes a site fast or slow. User-specific data (e.g., a profile, payment data, etc.) is hardly ever the cause of performance problems. Nonetheless, we do use CDNs for public data as they are an indispensable tool to achieve low latency.
When it's actually simple as long as (like everything else) it had always been.
"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."
If you'd read https://news.ycombinator.com/newsguidelines.html and only comment in the spirit of this site, we'd appreciate it.