Title:

As a webmaster I should be able to configure fastly IO on website so that I can improve the page-load time performance of the pages.

Description:

Media websites display images everywhere on the website. These images are uploaded independently of various sizes for display based on-screen resolutions. These images consume high network bandwidth and increase the page rendering time on the end-user devices (browsers). Fastly Image Optimizer (IO) comes with the solution to bypass this manual work of image upload for multiple screen resolutions and offers a mechanism to reduce page load time to improve end-user experiences. The reduced page load time improves the overall website performance, boosts conversions, and contributes to Google search crawling.   

In short Fastly IO: - 

1. i) Improve page load time: render the images on demand via their cloud edge platform by resizing, adjusting the quality, crop/trim, change orientations, convert formats and many more. 
2. ii) Reduce infrastructure costs: It reduces the third-party integration to render images.  It stores the images at one origin and renders them based on the requests. 

iii) Delighted customer Experience: Optimize the page load time, improve performance, reduce operation costs.  

Refer functional specification: [CLOUD] Fastly Image Optimizer V0.3_draft.docx, https://sway.office.com/0C3bmAXn7sSRe4YM?authoringPlay=true&publish

Acceptance Criteria:

Webmaster should be able to

• enable/disable Fastly IO on their application.
• customize Fastly IO configuration on their application.  
• bypass Fastly IO implementation on certain media/image types of their application.