It uses real-user monitoring (RUM) data gathered by Akamai' mPulse service to show you which scripts referenced on your site are causing the largest impacts on performance. You can use this information to create Script Management policies that automatically block or defer scripts and ensure that single points of failure don't stop pages from loading. It also offers "testing suggestions" that help you find the most popular pages that your policy affects, so you can confirm that Script Management is working as intended.
akam-sw.js. A service worker is a code that runs in the background and performs tasks separate from the page and user interactions. Here's roughly how it works:
With the Script Management enabled and its Mode set to Analysis and action, your Ion property injects a script into pages on your site.
When a user first requests a page, the injected script downloads and installs the
The service worker applies your Script Management policy to manage scripts as the user navigates the page. (You create the policy outside of this behavior, using a separate tool.)
As the user navigates your site, scripts are blocked, deferred, or allowed based on what's set in your Script Management policy.
akam-sw.js service worker operates at the root scope of your site. This is true regardless of what page a user is viewing. For example, when a user requests
www.example.com/products/widgets/index.html, the scope is
The service worker only works with supported browsers. This currently includes the latest versions of:
- Chrome (desktop and mobile)
- Firefox (desktop and mobile)
- Safari (desktop only)
Script Management is supported for use with Akamai's Ion product. You need to include a few other behaviors in your Ion property, too. We offer a workflow that describes the full process to add it in the Ion user docs.
Updated 12 months ago