Rain
Fog
Snow
There are five key features that sports clubs should try to incorporate into their websites. In the following sections, we’ll explore these (more…)
Posted by Jonathon Roberts
When thinking of football, you probably immediately think of the big names like Liverpool, Manchester United and Chelsea, but these clubs are just the summit of what’s known as (more…)
Posted by John Murray
Before we’re even old enough to acquire language, colours help us to make sense of the world and are a form of communication. No sooner can children talk than they are able to tell us what their favourite colours are, perhaps influenced by the (more…)
Posted by John Murray
We’ve all come across websites that just make us think “this is awful!”, but it’s not always easy to identify what about it makes for a poor user (more…)
Posted by John Murray
In these times, when a lot of us would have no idea what to do with ourselves without the web, it may surprise you to read that more than one in seven (15%) of people in the UK are classed as (more…)
Posted by John Murray
In our final week of looking at Core Web Vitals, we’re going to talk about Cumulative Layout Shift, or (more…)
Posted by Andrew Waterhouse
In our second part of the Core Web Vitals Series (you can read the first part here), we’re going to look at First Input Delay (FID). So, first of all, what is it?
In short, FID is the time between the user’s first interaction with a page (such as by clicking a link), to when the browser first starts to process the interaction. Time to interaction (TTI) has been a similar metric in the past, though TTI only records how long it took for the page to be interactive, rather than the time to respond to user interaction. FID is a good metric to focus upon to help reduce the clunky feeling of a website.
A good FID score is a delay of less than 100 milliseconds, or 0.1 seconds. Usually, input delay occurs because the browser is busy with another task, so cannot yet respond to the user. Executing a JavaScript file is a common example of what might be keeping it busy. Note that FID only measures the delay in event processing, not the time it takes to complete the event processing time itself.
In the above example, the user just happened to interact when the browser was at the beginning of the main thread’s busiest period. If they had interacted a moment earlier, the browser could respond right away. Waterfall graphs can help identify which scripts are holding up a site from being FID-friendly.
For a better FID, you need a focus on reducing the impact of third-party code. Slashing the number of tools, plugins, and code elements of your site will go some way to help with this. The work of the main thread needs to be minimal, while request counts are kept low and transfer sizes small.
A great tool to troubleshoot FID is the Chrome User Experience Report. The data collected is powered by real-world users, measuring metrics from the web. The resulting data can be found by inputting your website into PageSpeed Insights and Google’s BigQuery project.
First Input Delay is one of three Core Web Vitals that Google wants to make a part of its search algorithm by May 2021. The earlier you make the necessary changes to make user-experience the focus, the more effective your search engine optimisation (SEO) campaign will be.
In the next blog post, I’ll discuss Cumulative Layout Shift, and the steps you can take to make sure your website is ready for the future of online search.
Posted by Andrew Waterhouse
In the first of three blogs about Google Core Web Vitals and its three fundamental aspects, today we’re going to look at Largest Contentful Paint. (more…)
Posted by Andrew Waterhouse
Copyright © 2009 - 2021 Engage Web
Engage Web is a registered trademark of Sheer Media Ltd.
All uses of this trademark is strictly prohibited without the written permission of Sheer Media Ltd
Registered In England and Wales, registered company number: 6889568
VAT Number: 972 0942 09
