For full transcript https://www.semrush.com/blog/weekly-wisdom-with-ross-tavendale-site-speed-audit/
Hello everyone, and welcome to another Weekly Wisdom. I am Ross Tavendale of Type A Media. Recently, Google added a bunch of page speed insights into Webmaster tools, or should I say Search Console (that is one for the original Gs out there). So, today I want to show you how to use your Chrome browser to run a Lighthouse audit, but also dig into a bunch of things you can do in the site’s code itself to speed things up. This isn’t going to be super techie, but it is kind of intermediate. So strap in and let’s get into it.
First and foremost, this is our website here. Let’s have a look at our case studies page because there are lots of images on it. To get a true understanding of a new person coming to the site, I am going to clear the cache. The cache is essentially all the memory stored in the browser; I want to delete that, so when I click Command + R to reload, you see that that image didn’t load as fast as it did the first time.
So, let’s dig into that and see what is actually going on there. I am going to hit F12 in order to get into the console itself. When you open it up, you SEO guys will be very familiar with doing control/Cmd + F to find and determine if there are canonicals on the page, are they broken, or why is it not ranking. Is it because there is a noindex tag on there or something like that?
We are all very used to looking at the site’s code itself, but when it comes to the order of things loading, and things like the first contentful paint, where do we find that information? Okay, well, let me show you. Let’s jump into “Network”, and what I am going to do is I am going to reload this guy again.