Webpage: http://www.electrorent.com
Device: Desktop Computer
Region: Australia (Sydney)
Single Region Score
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]
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].
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. [Learn more about accessible names].
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.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. [Learn more about form element labels].
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript].
This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element]
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].
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].
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content], where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. [Learn more about HTTPS].
Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects].
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]
Form elements without effective labels can create frustrating experiences for screen reader users. [Learn more about the `select` element].
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast].
A large DOM will increase memory usage, cause longer [style calculations], and produce costly [layout reflows]. [Learn how to avoid an excessive DOM size].
Third party code can significantly impact load performance. [Reduce and defer loading of third party code] to prioritize your page's content.
Image display dimensions should match natural aspect ratio. [Learn more about image aspect ratio].
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size]