Webpage: https://www.guess.eu
Device: Desktop Computer
Region: Ireland (Dublin)
Single Region Score
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Keep the server response time for the main document short because all other requests depend on it. [Learn more about the Time to First Byte metric].
Optimize LCP by making the LCP image [discoverable] from the HTML immediately, and [avoiding lazy-loading]
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size]
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].
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].
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].
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].
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast].
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]
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.
Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects].
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.
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.
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]