Reece.com Site Title
Reece Business Portal
Reece.com Meta Description
Reece Business Portal
Reece.com Test Results
Reece.com Mobile Performance: 2/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Potential savings of 170 KiB
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,920 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Minimize main-thread work
14.5 s
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
Minify CSS
Potential savings of 29 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 113 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Eliminate render-blocking resources
Potential savings of 24,620 ms
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.
Largest Contentful Paint element
38,640 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
10.6 s
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.
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Reduce unused JavaScript
Potential savings of 3,350 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Enable text compression
Potential savings of 3,187 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid large layout shifts
3 layout shifts found
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
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Avoid enormous network payloads
Total size was 6,049 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Properly size images
Potential savings of 67 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve static assets with an efficient cache policy
42 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Time to Interactive
42.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
1,810 ms
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.
First Meaningful Paint
27.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Reece.com Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
4 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Reece.com Mobile Best Practices: 59/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Browser errors were logged to the console
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
Missing source maps for large first-party 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.
Trust and Safety
Does not use HTTPS
1 insecure request found
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.
Reece.com Mobile Accessibility: 87/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Links do not have a discernible name
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.
Buttons do not have an accessible name
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.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.reece.com
www.reece.net
www.reece.org
www.reece.info
www.reece.biz
www.reece.us
www.reece.mobi
www.eece.com
www.reece.com
www.eeece.com
www.reeece.com
www.ereece.com
www.deece.com
www.rdeece.com
www.dreece.com
www.feece.com
www.rfeece.com
www.freece.com
www.teece.com
www.rteece.com
www.treece.com
www.rece.com
www.rwece.com
www.rewece.com
www.rweece.com
www.rsece.com
www.resece.com
www.rseece.com
www.rdece.com
www.redece.com
www.rrece.com
www.rerece.com
www.rreece.com
www.rewce.com
www.reewce.com
www.resce.com
www.reesce.com
www.redce.com
www.reedce.com
www.rerce.com
www.reerce.com
www.reee.com
www.reexe.com
www.reecxe.com
www.reexce.com
www.reede.com
www.reecde.com
www.reefe.com
www.reecfe.com
www.reefce.com
www.reeve.com
www.reecve.com
www.reevce.com
www.reec.com
www.reecw.com
www.reecew.com
www.reecwe.com
www.reecs.com
www.reeces.com
www.reecse.com
www.reecd.com
www.reeced.com
www.reecr.com
www.reecer.com
www.reecre.com
www.reece.con
www.reece.net
www.reece.org
www.reece.info
www.reece.biz
www.reece.us
www.reece.mobi
www.eece.com
www.reece.com
www.eeece.com
www.reeece.com
www.ereece.com
www.deece.com
www.rdeece.com
www.dreece.com
www.feece.com
www.rfeece.com
www.freece.com
www.teece.com
www.rteece.com
www.treece.com
www.rece.com
www.rwece.com
www.rewece.com
www.rweece.com
www.rsece.com
www.resece.com
www.rseece.com
www.rdece.com
www.redece.com
www.rrece.com
www.rerece.com
www.rreece.com
www.rewce.com
www.reewce.com
www.resce.com
www.reesce.com
www.redce.com
www.reedce.com
www.rerce.com
www.reerce.com
www.reee.com
www.reexe.com
www.reecxe.com
www.reexce.com
www.reede.com
www.reecde.com
www.reefe.com
www.reecfe.com
www.reefce.com
www.reeve.com
www.reecve.com
www.reevce.com
www.reec.com
www.reecw.com
www.reecew.com
www.reecwe.com
www.reecs.com
www.reeces.com
www.reecse.com
www.reecd.com
www.reeced.com
www.reecr.com
www.reecer.com
www.reecre.com
www.reece.con