This is part 3 of An introduction to SiteImp Reports, an 11 part series about SiteImp audits, designed to help you learn more about your new SiteImp report. If you would like to follow along, you can download it here. (Note - it will open in a new tab.)
Last article
Last article, I talked about the average scores report. That report shows the average score calculated on every page on your website.
Not to mention, I was upset with my site’s performance in cumulative layout shift. I’m a website performance consultant who forgot to test my site after I made a major change.
In between being upset with myself, I defined important measurements in SiteImp audits like “Performance”, “Cumulative Layout Shift” and “First Input Delay”.
This article
This article, we’re going to find out why my performance scores were so poor. Take a look at the five pages on my site (obviously before I pushed these articles live) and their scores:
Every page found and their scores from a Siteimp report run on January 7, 2022
It’s pretty simple now. Check the correlation between my cumulative layout shift and performance scores. I built the site (and SiteImp) so know exactly what to do but I will finish this tutorial, make the fix and blog about it.
Each column has the same meanings as in the last article. Only this very useful page shows your scores, and total bytes transferred for each of your pages. It’s a great way to figure out why you get relatively low performance scores.
It’s essentially all your Lighthouse scores, calculated for your entire website.
Next article
Next article, we’re going to talk about full site recommendations and why you should always implement them first.