Cre.fr Test Results

Cre.fr Mobile Performance: 92/100
Quick overview:
Time to Interactive
11.8 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.
First Meaningful Paint
2.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
120 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Eliminate render-blocking resources
Potential savings of 390 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.
Reduce unused CSS
Potential savings of 68 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
Serve static assets with an efficient cache policy
12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused JavaScript
Potential savings of 34 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.
Defer offscreen images
Potential savings of 7 KiB
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.

Cre.fr Mobile SEO: 100/100
Quick overview:

Cre.fr Mobile Best Practices: 83/100
Quick overview:
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.
Cre.fr Mobile Accessibility: 82/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-hidden="true"]` is present on the document `<body>`
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn how `aria-hidden` affects the document body.
Similar sites
Similar tests
www.cre.com
www.cre.net
www.cre.org
www.cre.info
www.cre.biz
www.cre.us
www.cre.mobi
www.re.fr
www.cre.fr
www.xre.fr
www.cxre.fr
www.xcre.fr
www.dre.fr
www.cdre.fr
www.dcre.fr
www.fre.fr
www.cfre.fr
www.fcre.fr
www.vre.fr
www.cvre.fr
www.vcre.fr
www.ce.fr
www.cee.fr
www.cree.fr
www.cere.fr
www.cde.fr
www.crde.fr
www.cfe.fr
www.crfe.fr
www.cte.fr
www.crte.fr
www.ctre.fr
www.cr.fr
www.crw.fr
www.crew.fr
www.crwe.fr
www.crs.fr
www.cres.fr
www.crse.fr
www.crd.fr
www.cred.fr
www.crr.fr
www.crer.fr
www.crre.fr
Last Tested: