canonical url like "Type=amp" or something similar. This will make it easy to differentiate amp pages from normal web pages in analytics, or create a custom segment if you need. This way, you can compare the total page traffic before and after the amp company employee list launch. Side note: how accelerated mobile pages work if you're wondering how amp pages can seem to load instantly, it's because they're optimized differently than a typical webpage. Below, I've summarized the optimizations amp performs to reduce the amount of work a browser has to do to render a page.
(see the full list on the amp project site.)here is what the amp process can do: run only asynchronous javascript - it doesn't wait for large files to load. Trim assets (such as images, ads, and iframes) statically – the browser knows exactly how the page will be presented from the get-go. Don't let extensions block rendering – the page doesn't have to wait even if there are upcoming extensions. Keep 3rd party javascript out of the critical path – things like ads are limited to sandboxed iframes. Only allow inline css – inflated css files do not lag the page. No http requests until fonts start downloading .
keeps fonts efficient. Minimize styling recalculations - all dom reads happen upstream to lay out the page. Run only gpu-accelerated animations - the graphics processing unit handles visual animations (transformation and opacity), reducing company employee list cpu pressure. Prioritize resource loading – the most important resources (above the fold) are downloaded first. Load pages through pre-rendered content - content above the fold can be available.