To do this, add Adaptive Acceleration to your Ion property. It syncs with Akamai real-user monitoring to gather navigation and resource timing data and stores that data in a policy that's associated with your hostname. As requests for your hostname continue, policy data is gathered and reviewed to identify key resources. This allows Adaptive Acceleration to provide these resources to an end user's browser ahead of time, reducing the load and render time for your web pages.
Follow this process to set up this recommended feature.
Prefer an API?
If you'd rather use an API to set up and manage, you can use a combination of Akamai's Property Manager and Adaptive Acceleration APIs. Check out the tutorial.
Before you can configure Adaptive Acceleration, you need to do a few things:
Your Ion property needs to be secure. You need to define property hostnames that connect the end user to the Akamai edge securely via HTTPS. You can use any of the secure methods Akamai offers: Enhanced TLS, Standard TLS, or the Akamai shared certificate.
Enable a beacon source. Timing data is collected in "beacons" and sent to a Akamai's real-user monitoring source, mPulse. Adaptive Acceleration communicates with mPulse to get this data. To configure it, use the mPulse RUM sub-rule, that's default included in a new Ion property.
Enable HTTP/3. The HTTP/3 behavior is automatically included and enabled in the Default Rule. It doesn't require any additional configuration. It just needs to be included in your rule tree where it'll be applied to requests that also apply the Adaptive Acceleration behavior.
HTTP/2 is still supported
Older Ion properties automatically included the HTTP/2 behavior and it was required for use with Adaptive Acceleration. You can keep your property configured this way, but we recommend that you update it to use HTTP/3, instead.
- Get access to the Adaptive Acceleration interface in Akamai Control Center (Optional). This interface lets you view policies of navigation and resource timing data that have been gathered for use with the Automatic Push, Preconnect, and Font Preload services. You can also use it to reset the data gathering mechanism. You need to have a Control Center account that's been granted access to this interface. If you're not sure, talk to your local Akamai admin, or contact your Akamai account team.
Adaptive Acceleration is added by default to the Accelerate delivery sub-rule in your property.
To start, set Beacon Data Source to mPulse.
These options help optimize delivery using the beacon data gathered from mPulse. Here's roughly how these features interact with mPulse and Adaptive Acceleration:
Adaptive Acceleration analyzes mPulse data for the most-visited pages on your site. It identifies the resources and resource domains on the critical rendering paths for those pages and creates a report.
When subsequent end users request a page in the report, Adaptive Acceleration sends resources and establishes anticipated connections while the client is waiting for a response.
Set the options here as follows:
Automatic Server Push
Set this to On.
This lets browsers anticipate what connections the site needs, and establishes those connections ahead of time. But, it doesn't actually load or request anything.
Example of an Automatic Preconnect
This example shows how Automatic Preconnect establishes connections ahead of time. Assume the page
Every visit to that page prompts the user's browser to establish a second connection to
Automatic Font Preload
Set this to On.
This lets browsers preload the fonts they'll need before they fetch and process other resources. Beacon data from mPulse is used to identify the font requests made by the pages on your site. Font Preload uses this information to add browser-specific preload headers to each font. Once a preload header has been applied, the font will be ready to download before the browser has fully rendered the page.
Example of Automatic Font Preload
This example shows how Automatic Font Preload is used to load fonts before other resources are fully processed. Assume the page
Every visit to a page prompts the user's browser to submit a separate request for each of the three fonts. After examining user requests for the page, the Adaptive Acceleration learning engine gathers enough data to determine that those fonts "belong" to that page. Adaptive Acceleration adds an Automatic Font Preload entry to the policy: When responding to requests for `www.moviememorabilia.com/shop/, tell the browser to start loading the font resources before it fetches and processes resources referencing the fonts.
In addition to the compression offered by Adaptive Acceleration, there are other ways to set up compression in your Ion property. Before you apply it here, take a look at this table to see how all of the available methods stack up.
|Compression method||Where the compression is applied||Additional information|
Brotli Compression Beta
On the edge network.
You can enable this here in the Adaptive Acceleration rule. Brotli Compression looks to resolve several interoperability issues seen with Resource Optimizer. It automates the compression and delivery of
On the edge network.
You can enable this here in the Adaptive Acceleration rule. It automates the compression and delivery of your
On your origin server.
You need to add a separate behavior to include this support.
This behavior serves compressed resources to requesting browsers. The resources need to be Brotli-compressed on your origin. So this doesn't offer dynamic compression, while Brotli Compression and Resource Optimizer do. If you know that all of your
Last Mile Acceleration
On the edge network.
This behavior is included in the Minimize payload rule that's automatically included in your Ion property. It automates the compression of various file types to gzip. The following apply to its use:
To enable this, set it to On. If you also have access to Brotli Compression, set it to Off. You can't use both.
Resource Optimizer compresses
During the compression, Resource Optimizer sets the downstream TTL of the file to 900 seconds (15 minutes).
Resource Optimizer serves compressed, cached content on HTTP 200 responses to a request. Both the original and the optimized resources are served under the same cache key:
Before you save your property and enable it on any Akamai network, you need to apply a few more settings in your Ion property to ensure it's compatible with Resource Optimizer.
- You want to use Caching with a Maxage of at least an hour. This applies to the Caching behavior in the Offload Origin rule. Use any of the settings to enable caching—Cache, Honor origin Cache-Control and Expires, Honor origin Cache-Control, or Honor origin Expires— and set its "maxage" field to at least one hour.
There are several other caching-related sub-rules in the Offload Origin rule, too.
- Other static objects
They're used to override the generic Caching maxage for these specific file types, based on recognized best practices. They all include a default maxage in excess of one hour. For best results with Resource Optimizer, keep these maxage settings as is.
Only use Resource Optimizer for GET requests. It should only initiate compression and serve compressed content for requests that use the GET method.
Ensure the Cache-Control header doesn’t contain a private directive. The
Cache-Controlheader on your origin server can be used determine how caching should be applied. You can add the
Privatedirective to it to block the caching of personally identifiable information (PII). This header can't contain this directive if you want to use Resource Optimizer. You can apply this as a setting when configuring Downstream Cacheability.
In most cases, the standard Resource Optimizer feature provides the compression you'll need. We also offer this behavior to add more compression and to address some compatibility issues.
This behavior needs to be added to your contract. Talk to your Akamai account team for details.
Enable this option to add more support and error handling. Features of note include the following:
Support for Fast Purge using Cache Tags. You can generate purges via our Fast Purge application using any Cache Tags you've configured in your Ion property.
Obey your time to live settings. Resource Optimizer uses its own time to live (TTL) threshold for content it caches. If you've set your own TTL for your content in cache, we'll honor that value. The standard Resource Optimizer feature in Adaptive Acceleration will ignore a custom TTL and apply its own value.
It helps to prevent 404 errors from Resource Optimizer back-end requests in Akamai traffic reports.
It can help optimize the final resource when using redirects.
Consider these points when adding this behavior:
Put it in the same rule tree as Adaptive Acceleration. For the easiest application, include it as a behavior in the same rule to have it applied in place of the standard Resource Optimizer support. Or, include it in a child rule to the rule that includes Adaptive Acceleration. In this case, you can set it to a specific match criterion to apply its extended support for specific requests.
It overrides standard Resource Optimization. When you add this behavior, it overrides the standard Resource Optimizer feature in the Adaptive Acceleration behavior. You can disable the Resource Optimization feature in Adaptive Acceleration.
Resource Optimizer and Cloudlets. All forms of Resource Optimizer do not work with Cloudlets that modify the forward origin path.
Test this after you add it. If you're already delivering your site using the standard Resource Optimizer feature, you should thoroughly test your Ion property after adding this behavior.
This feature is only available to customers who have signed up for its beta program. Talk to your account team to see if you're eligible to participate.
To add this support:
- Set (BETA) Brotli Compression to On.
- Select Enable for Non-Cacheable if you also want to your non-cacheable content to be Brotli-compressed.
- Ensure that Resource Optimizer is set to Off. You can't use both.
You may experience a slight increase in latency if you've checked Enable for Non-cacheable and you're using any of these content injection behaviors on your page:
Brotli Compression targets text-based content. Compressible content is identified in the
Content-Type header of the metadata, or by the file extension. It returns Brotli-encoded responses to compatible browsers for resources with
.svg file extensions. It also returns Brotli-encoded responses for the following content-types:
You can use A/B testing to compare two versions of a webpage or app against each other to determine which one performs better. If you'd like to include Adaptive Acceleration-related data in your A/B testing model, enable it based on how you've set it up in your Ion property.
Cloudlets bring a site's business logic closer to the end user by placing it on the edge of the content delivery platform. Akamai offers several Cloudlets you can configure to support A/B testing:
If you've set up A/B testing using any of these Cloudlets:
Select Enabled using Cloudlets from the drop-down.
If you have multiple Cloudlets set in your Ion property, ensure that the Cloudlet you want to use for A/B testing is set lowest in the rule order. With Property Manager and these three Cloudlets, the last one in the list takes priority.
This applies A/B testing by redirecting a request to one of two origin servers, based on the contents of a cookie file included with the request. The cookie will use the same file name, but its content will vary, based on the desired site experience. So, when the cookie file is read, origin "A" or origin "B" is contacted to deliver the appropriate site experience.
This process assumes you already have an A/B testing model in place using a cookie in the request. You'll need to know the name of this cookie file.
- Open the Accelerate delivery sub-rule in the Default Rule.
- Click the Adaptive acceleration child rule.
- Set A/B Testing Method to Enabled manually.
- In the Cookie Name field that's revealed, enter the name of the cookie file that you've configured for use in your A/B testing model.
Adaptive Acceleration isn't compatible or has known issues with other features offered in Property Manager.
The match condition Percentage of Clients doesn't work with Adaptive Acceleration.
This would only be an issue if you were to add an instance of the Adaptive Acceleration behavior to another rule and you tried to set the Criteria to Percentage of Clients.
Automatic Push, Preconnect, and Font Preload
Brotli Compression Beta
For the Beta release, Brotli compression may not be performed if these features also apply to the request:
If any of these incompatibilities exist, you don't need to turn off Brotli Compression or any of the incompatible features. If an incompatibility is discovered, gzip or uncompressed resources are served instead.
With your property live and mPulse enabled as your beacon data source, give it some time to gather data. Data for the Automatic Push, Automatic Preconnect, and Automatic Font Preload settings is gathered and stored in a "property report." This report is used to determine "high usage" assets for your site or app, for use with Adaptive Acceleration.
Akamai offers additional services you can use with Adaptive Acceleration.
You can use these tools to interact with the beacon data collected in the policies for the Automatic Push, Preconnect, and Font Preload features.
View the policy data. See what Adaptive Acceleration has identified in your policies for early delivery. The Adaptive Acceleration interface on Akamai Control Center also lets you view warnings and event logs for the policy for troubleshooting.
Reset the policy. If you've changed your site or you don't want to wait for earlier data to drop out of the analysis, you can manually reset the data-gathering mechanism.
Check out the mPulse reports to access monitoring and reporting tools for beacon data used by Adaptive Acceleration.
Updated about 1 month ago