Guide to Optimize AMP for Google PageSpeed insights

In this tutorial, we will guide you to optimize AMP for Google PageSpeed insights by showing you some of the most common issues along with ways to solve them.

Here is a list of Google PageSpeed insights most Common problems

1. Remove Unused Javascript: That has AMP Url’s
2. Eliminate render-blocking resources: …css/all.css(use.fontawesome.com)

1. Remove Unused Javascript: That has AMP Url’s

1. Remove unused JavaScript – Usually, this is not a problem but this time, it has AMP scripts in it. Recently Google has changed the ads to AMP4Ads, now those “unused” URLs are actually getting loaded in the iframe. So that is also being counted as unused, which should not be the case actually this thing is confusing a lot of people. In reality, the script isn’t loading, so there is no performance issue or slow down in speed as the report might suggest.
2. Eliminate render-blocking resources – Font awesome CSS is loading, to solve this, use CSS Icons from https://take.ms/hiVy7

2. Eliminate render-blocking resources: …css/all.css(use.fontawesome.com)

The goal is to reduce the impact of these render-blocking URLs by inlining critical resources, deferring non-critical resources, and removing anything unused.

Font Awesome CSS is loading, to solve this, use CSS Icons from AMP settings for this follow the below screenshot.

That’s it for this tutorial!

We hope it helped you. If you have any feedback or questions, then please share them in the comments section below.