& TECHNOLOGY
Google’s page experience update explained
Ahead of the rollout of Google’s latest algorithm update, Digital Growth Programme consultant Ian Lockwood explains how businesses can ensure their website is up to speed and offers advice on ways they can improve quality scoring.
DIGITAL
to be in place by the end of August. This change to its organic
I
ranking algorithm rolls up a number of existing ranking factors and introduces some changes to the way page load speed is measured. Google first announced this last
November so the change is likely to be noticeable, although it’s clear that the quality of information on a page is the priority, even if the page experience is sub-par. You can already find a new page
experience report in Google Search Console to show if your site has any issues. Specifically, Google’s page
experience signals are: • Core Web Vitals (the three measurements of page load speed are largest contentful paint, first input delay and cumulative layout shift)
• Mobile-friendly • Safe browsing (website is not hacked)
• HTTPS (site serves over a secure connection)
• No intrusive interstitials (large overlays covering the page on mobile) These are all used in Google’s algorithm already, although Core Web Vitals changes the metrics measuring page load speed.
CORE WEB VITALS UNPACKED Core Web Vitals probably presents the biggest challenge for websites, as the vast majority should already be compliant with the other criteria (but do make sure your website serves over HTTPS, passes Google’s mobile-friendly test and doesn’t have intrusive interstitials). Let’s look at Core Web Vitals.
Firstly, largest contentful paint (LCP), which measures how long the main content area of the page
64 business network June 2021
‘Core Web Vitals probably presents the biggest challenge for websites’
(without scrolling down) takes to appear. The target is under 2.5 seconds.
While the quality of hosting can affect speed, most issues stem from how long it takes the visitor’s browser to download, process and render (visually display) the files that make up the page. Common issues include render- blocking (JavaScript and CSS files that have to be processed but aren’t used in the initially-visible page), unused resources (CSS and JavaScript included but not actually used) and images with unnecessarily large files. Images are relatively easy to fix,
such as replacing existing images with correctly-sized and better- compressed ones, but other issues can be tricky. Plugins and modules to help
might be available (WP Super Cache and Autoptimize for WordPress), but often only hand- editing the code can fully fix LCP issues. First input delay (FID) measures
the time before a user can interact with the page, such as to click a link. The target is under 100 milliseconds. FID is caused by the browser
being tied up by JavaScript and CSS, preventing it reacting to the user’s input. This requires optimisation of code to lower the impact on processing time. Cumulative layout shift (CLS)
measures how much the parts of a page move around as it loads, scored 0 to 1 with a target of below 0.1. Solutions include setting the size
for anything loaded separately, such as images, videos and other
elements (eg cookie notices). Loading fonts can also cause CLS
– the text is initially displayed in the default browser font, then the “proper” font loads and text shifts. If you want to know how your
website and page load speed are performing, test your site at one of the links below:
Google Search Console page experience report:
https://bit.ly/emc-gsc
Google PageSpeed Insights:
https://bit.ly/emc-psi
For full details on Google’s page experience update, visit
http://bit.ly/emc-pe
To hear more from Ian join him at our next workshop. To see the full schedule, visit www.leics-
digital.co.uk/events
n mid-June, Google begins its rollout of its page experience update, with the full effects due
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80
