The developer at Experte, sent me a link to their Core Web Vitals checker to ask me to test it out. I’ve got to say, I’m impressed. Very impressed in fact. This is such a useful tool to add to your page speed testing arsenal.
Test All Pages – On Your Website
There are plenty of test sites out there that will check one page for you, to show you its core web vitals. But what this checker page does is look at your whole website (max 500 pages) and report on every page it finds.
As we all should know by now, in May 2021 Google has informed us all, that it will be testing our whole websites for the Core Web Vitals and marking our sites using what it finds for 75% of the pages. We don’t get to choose which pages it looks at, so we need to make sure all our pages are up to that test. This tester is a huge help in that task.
I’m lucky, that I’ve already worked very hard at bringing my website up to Google’s performance requirements. With most of my pages now passing their Core Web Vitals check, when I test in PageSpeed Insights. However, it doesn’t hurt to keep checking and find any pages I may have missed. This tester helps flag those that I should perhaps check again.
Two features I really like are:
1/ If you click on the notes icon to the right hand side, it auto launches a new tab in your browser and loads that page into PageSpeed Insights. That’s brilliantly simple.
2/ If you export the results. Then open them up in a spreadsheet. I opened mine in Apple Numbers program. You can then sort the results using various columns and also make any notes in a new column, if needed. Plus highlight any results that you need to look at. Very neat idea.
I can see myself recommending this test to all of my Website Speed course clients. It’s a great, simple way of testing your whole site and showing the results in an easy to understand and use, way.
I need to check with the developer about the middle column – FID (first input delay). Because as I understand it, no computer test can actually measure this. Because it requires human interaction to actually press something on your website – such as a menu button. It’s normally only shown in the Field Test results in PageSpeed Insights, where its recorded real world humans using the site. Most testing programs tend to use the TBT (total blocking time) instead. I imagine this does too, but is just titled differently. For our testing purposes, it’s not a big deal, because we are still checking how fast the server reacts to our instructions – if it blocks things, there’s a delay. And when you’re trying to serve up your website fast, any delays aren’t good. So ideally we want near zero blocking time if we can get it. My portfolio page flags up in the screenshot above, with a red time of 330ms. When tested with PSI (PageSpeed Insights) it passes fine. But it’s always worth double checking.
Want to speed up your website? Drop me an email. I run a course on how to tweak your website for maximum speed. No coding required. Just common sense and learning what factors really control how fast (or slow) your website loads.