Webpage: https://www.bostik.com
Device: Desktop Computer
Region: Australia (Sydney)
Single Region Score
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. [Learn more about source maps].
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast].
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size]
Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more about modern image formats].
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn how to defer offscreen images].
Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects].
Descriptive link text helps search engines understand your content. [Learn how to make links more accessible].
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS].
This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element]
Optimize LCP by making the LCP image [discoverable] from the HTML immediately, and [avoiding lazy-loading]
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn how to eliminate render-blocking resources].
Layout shifts occur when elements move absent any user interaction. [Investigate the causes of layout shifts], such as elements being added, removed, or their fonts changing as the page loads.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. [Learn more about touch targets].
Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining] can move these network requests out of the critical path.
Serve images that are appropriately-sized to save cellular data and improve load time. [Learn how to size images].
Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs].
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit]
Image display dimensions should match natural aspect ratio. [Learn more about image aspect ratio].
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing]. [Learn how to improve CLS]