How to Automatically Optimize the Size of Your Critical Page Resources

by Ted Shuter
391

This is one in a series of posts following up on our announcements from the Developer Zone at Edge 2017. For a complete review of Edge, see our recap page.

In an earlier blog post, I gave an overview of Adaptive Acceleration, Akamai’s intelligent solution to continuously apply performance optimizations with zero development effort.

That was followed up by a post about Adaptive Acceleration’s Learning Engine feature.

Now with this third post I want to highlight yet another incredible feature in Adaptive Acceleration: It’s called Resource Optimizer, and it’s a simple way to optimize the size of your critical page resources. I like to describe it as “Image Manager for non-images”.

As we all know, growing page weight is slowing down performance and driving up user bills. Resource Optimizer was designed to mitigate these issues to reduce bandwidth and improve customer web experiences.

In particular, Resource Optimizer leverages Zopfli and Brotli protocols to reduce the size of cached CSS and JavaScript (Zopfli for older browsers, and Brotli for modern browsers that are using https). So your page weight will get smaller, with file sizes reduced by 5% to 25% as Resource Optimizer automatically compresses, caches, and delivers. This process accelerates the rendering so your users see information sooner and can interact with your content faster.

For additional insight and information on Resource Optimizer and Adaptive Acceleration, see our video of the Developer General Session presentation at Edge 2017 (the Adaptive Acceleration portion begins at 33:18).

Adaptive Acceleration is available with Ion, Ion Premier, and Ion Media Advanced. To get started with Adaptive Acceleration right now just log into your Akamai customer portal, where you can try Ion via the Marketplace. Or if you’re an existing Ion customer, simply log into Property Manager and add the Adaptive Acceleration behavior to your property (note: the Adaptive Acceleration behavior requires that you enable both HTTP/2 and RUM on the same property). Here’s a quick walk-through that shows you exactly how to do it:

See the other posts in this four-post series about Adaptive Acceleration:
1. Overview
2. Learning Engine
3. Resource Optimizer (you are here)
4. Script Management (coming soon)

Categories: DevOps, Edge '17 Highlights

Suggested Article

LEAVE A REPLY