How Does It Work?
Once FEO is enabled in the Akamai portal, an FEO policy is created by Akamai or by our customers, that contains URL match criteria and a set of optimizations that are applied to those match criteria. An offline process analyses a page and produces transformation rules to be applied for a period of time. Those transformations are applied at the Akamai edge as content is served to the end users.
- The FEO framework maintains the order of the scripts for download and execution. Generally this is not an issue. Problem scripts can also be excluded by URL or regular expression.
How do I test it to make sure the code I’m working on right now works?
- See testing considerations
Disabling FEO on a request
If you want to compare the behavior of a page with and without FEO, this can be done by modifying the query string. All you need to do is add the query string parameter akamai-feo=off to your request, and the un-optimized, original page will be returned. For example, http://www.example.com/products/item.html?akamai-feo=off or http://www.example.com/products/item.html?exampleparam=somevalue&akamai-feo=off Just be sure to add it prior to any anchors, as denoted by # in the url.
An additional suggestion is to have two tabs open, one with FEO and one without so that the user experience can be compared..
How to debug
The first step is to functionally compare an optimized page against an unoptimized path in the browser. Use the browser tools to examine console messages. If you need to examine when a function triggers, as compared to another, you can add breakpoints in your browser developer tools to do this. You will note, when looking in the call tree, that the FEO framework will appear in the call list.
Testing New Code