Piez is a Chrome plug-in that provide information about the optimizations performed by Image Manager, Adaptive Acceleration, and/or Resource Optimizer (it might support other features in the future). The following information will be available in Piez
- Image Manager: shows total and per image bytes savings on a web page when using Akamai Image Manager to optimize images.
- Adaptive Acceleration: shows the pre-connected and pushed URLs on a web page when using Adaptive Acceleration
- Resource Optimizer: shows total and per object bytes savings on a web page when using Resource Optimizer
- Load the extension from the Chrome store, or use the source located at https://github.com/bretts/piez to load unpacked in developer mode.
- Ensure that the extension is enabled (it's enabled by default). Piez installs a shortcut in the Chrome app shortcut menu - check the status of Piez to ensure the icon displays 'On'.
- Click the Piez icon and select between the modes: Image Manager Standard, Image Manager Advanced, Adaptive Acceleration, Resource Optimizer Standard, or Resource Optimizer Advanced.
- Open the Chrome developer pane by clicking "View > Developer > Developer Tools" in the browser OR hitting Command + Option + J (Mac).
- Ensure that cache is disabled when developer tools is open. On Windows, navigate to settings in the developer tool pane, then select the "Disable cache (while devtools is open)" checkbox. On a Mac, select “disable cache” under Network tab in the developer pane.
- Switch to the Piez tab in the developer pane.
- OK, you're all good. Navigate to a page that uses the Akamai behavior you want to test and watch your page get optimized.
Important note about using Piez with Chrome’s emulation mode
When using Chrome’s emulation mode, Image Manager will think you’re using a device that supports JPEG 2000 (.j2) images if, for example, you have emulation mode set to emulate an iPhone or iPad. In this case, these images will not be rendered by the browser, since the browser is actually still Chrome, and therefore does not support JPEG 2000 images
Credit to Adrian Willis and Michael Gooding who documented this internally