Get In Touch
Recently by Pierre Lermant
Significant technology and usage changes have emerged since the initial publication of the practical guide to web resource caching. This updated edition revisits the recommendations issued earlier and brings new focus on: Fast Purge, the ability to invalidate or delete assets from the Akamai network in five seconds, and API usage, prevalent in native mobile and single page applications.
I'm often asked by our customers how their web sites compare to the industry averages, in terms of speed and size. While the numbers vary depending on the business, devices used and audiences, we can leverage the information gathered by httparchive.org to report overall metrics for desktop home pages.
Purging URLs at the Edge when its underlying content changes at the origin infrastructure may seem to be the best way to manage a website dynamic content. Or is it? In this post, we'll explore the pros and cons of purging, and offer an alternative when appropriate.
Every web site is unique, and each presents its own set of performance challenges and opportunities. These challenges can be exacerbated by perfectly reasonable business goals and site features, which can negatively affect the overall end-user experience. Business requirements (more features/ads), analytics (data beacons), time to market (we want it now), resources and cost constraints are all considerations that should be balanced with their effect on delivering a web experience
As we carry out performance evaluations for our customers, we often come across very popular pages that are made 'non-cacheable' at the edge. On top of incurring additional latency and therefore a degraded user experience, it generates heavy loads on our customers' origin infrastructure.
The first part of this series reminded our reader on the best practices for caching and emphasized the need to isolate personal data from any page view content. In this second blog post, we will provide actual caching value recommendations for client browsers and edge servers. We categorize each resource by time sensitivity, list the main observed use cases for each of them, and propose TTL values for the client
Web resource caching provides the dual benefit of reducing load on the origin infrastructure while accelerating the content delivered to the clients. Yet, because of business and technical requirements, it is often difficult to select the best caching rules for the client browser and the Akamai edge servers. In this 2-part blog I will review industry's best practices and offer recommendations for common use cases. Part 1 will walk