In this video we will cover the basics and more advanced aspects of pre-fetching pages or resources for near instantaneous load times.
We will cover the three main types of pre-fetching:
As well as the most common issues and challenges associated with this performance optimization.
Everybody agrees the mobile web is big. In the US, Mobile browsing has now surpassed desktop browsing, every 3rd person owns a browsing-enabled phone, and Android devices are selling like hotcakes. With the importance of the Mobile Web comes the importance of Mobile Web Performance, and naturally that spawns a lot of research and conversation.
In the midst of this craze, it’s worth stopping for a second and asking what exactly is the mobile web? What does “Mobile” mean? Is a windows laptop with a 3G stick a mobile device? What about an iPad on WiFi? Defining Mobile is critical if we want to understand and respond to mobile performance.
I find the best way to understand “Mobile” is to split it into 3 categories: Network, Hardware and Software. Each category comes with its own performance implications, and understanding those is important to keeping your site fast despite the different environment.
Read the rest of this entry »
In this video we focus on caching. We’ll describe the different cache types and how to manage your cache. We’ll then discuss some common challenges, pitfalls, and suggest solutions.
Update: Average page size is actually 800 KB, and average mobile page size is 400 KB.
Update: CDNs can also act as an SSL terminating proxy to cache SSL content, while still fetching it from origin over SSL.
If you enjoyed this video and would like to see more please post in the comments or send us an email to contact@blaze.io.
In this video Blaze CTO Guy Podjarny explains the basic concept, common pitfalls, and performance trade-offs of implementing consolidation on a website.
This whiteboard video is a new format experiment we are trying for this blog. If you enjoy this format please let us know at contact@blaze.io and we will make these videos on a regular basis.
This is a follow-up post to the review of HTTP Pipelining in Mobile.
HTTP pipelining introduces an interesting dilemma to the browsers which support it: How should they distribute the requests across the different connections and pipes?
When a new request needs to be made, the browser has three options:
