Modified on: Mon, 22 Feb, 2021 at 4:41 PM
The Siteimprove Performance feature allows you to audit and optimize your website for improved load time performance. Improving the load times of your content will allow you to deliver a better experience for your visitors, improving retention and conversion rates and make your content more effective. This article explains some of terms used in the Performance feature.
First Contentful Paint (FCP)
The time it takes for the web browser to load, render and display the first bit of content on the page. This provides the user with the first indication that something is happening on the page. FCP also marks when the browser goes from whitespace to partial content being visible on the page.
The time stamp is based on how long it takes the browser to render any text, image (including background images), non-white canvas or SVG. This excludes iframes but includes web fonts that are pending.
Largest Contentful Paint (LCP)
The time it takes for the web browser to load, render and display the largest image or block of context within the users viewport. Anything that extends beyond the viewport is not included in this metric. This provides an overview of how long users will have to wait for the primary content of the page.
The time stamp is based on how long it takes for the browser to load, render and display the main content of a page, i.e. elements that make up the majority of the primary content on the page within the users viewport. Typical elements include images, videos, backgrounds images and block-level text.
Time to Interactive (TTI)
The time it takes for the content of your website to become functional and ready for your users to interact with. This will give you a better understanding of how your website is experienced and perceived on the user end.
The time stamp is calculated by measuring how long it takes until the page content is loaded and background activity levels are low enough that the page is ready to receive new input from the user without delay.
A combination of parameters used to generate a measurement. These include the type of device being simulated, the network with which the test is run and location from which the measurement will be carried out. Each visitor profile therefore represents a unique combination of factors, and this allows you to represent a myriad of different visitor situations in order to determine where your performance should be improved.
A method of encoding content in such a way that the file sizes are reduced, which results in a smaller amount of data that needs to be served to users. This, in turn, leads to a faster load and less time spent waiting for content to appear on the page.
Examples of file types that can be compressed include text, images, and fonts. There are many different techniques to choose from in order to enable compression, and some modern CMS systems support plug-ins that greatly speed up the process.
A method of storing common files and resources closer to the user, so that these don’t have to be re-downloaded upon consecutive site visits. By preventing this, we ensure as fast of an experience as possible for our users.
For our purposes, we can divide the area into two sub-categories; browser caching and server-side caching. Browser caching means that the web browser will store certain items like CSS files, images, and logos, in order to speed up future visits of your site.
Server-side caching means that it’s the server storing common items instead of the browser, which are then served to several users faster than traditional access.
A methodology whereby we defer the loading of items and files until they are needed by the user. This will speed up the initial load since we are not having to load in objects and files which the user might not need.
Common examples include deferring the loading of images that are not visible initially to the user (such as image grids outside of the user's viewport at the bottom of the page). These images would then instead be loaded as the user scrolls down the page.
A method for reducing the size of resources used by the website, in order to serve smaller files faster. This, in turn, will improve load times for the end user.
Did you find it helpful?Send feedback