Webpage: https://www.donaldson.com
Device: Desktop Computer
Region: Ireland (Dublin)
Single Region Score
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.
Deprecated APIs will eventually be removed from the browser. [Learn more about deprecated APIs].
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more about the Maximum Potential First Input Delay metric].
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].
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. [Learn more about third-party cookies].
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time].
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. [Learn how to make links accessible].
Optimize LCP by making the LCP image [discoverable] from the HTML immediately, and [avoiding lazy-loading]
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.
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].
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. [Learn how to make buttons more accessible].
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work]
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].
Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects].
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]
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].
This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element]
Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.