Irsn.fr Site Title
Accueil | IRSN
Irsn.fr Meta Description
L'Institut de Radioprotection et de Sûreté Nucléaire (IRSN) effectue des recherches et des expertises sur les risques liés à la radioactivité.
Irsn.fr Test Results
Irsn.fr Mobile Performance: 57/100
Quick overview:
First Meaningful Paint
8.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
14.2 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 1,188 KiB
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.
Reduce unused CSS
Potential savings of 169 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.
Largest Contentful Paint element
13,410 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Enable text compression
Potential savings of 44 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid multiple page redirects
Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
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 156 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.
Eliminate render-blocking resources
Potential savings of 6,110 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.
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
Avoid enormous network payloads
Total size was 2,941 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minimize main-thread work
3.7 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 JavaScript
Potential savings of 23 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid an excessive DOM size
958 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Irsn.fr Mobile SEO: 100/100
Quick overview:
Irsn.fr Mobile Best Practices: 83/100
Quick overview:
Trust and Safety
Does not use HTTPS
2 insecure requests 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.
General
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.
Irsn.fr Mobile Accessibility: 81/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-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
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.
Elements with visible text labels do not have matching accessible names.
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.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.irsn.com
www.irsn.net
www.irsn.org
www.irsn.info
www.irsn.biz
www.irsn.us
www.irsn.mobi
www.rsn.fr
www.irsn.fr
www.ursn.fr
www.iursn.fr
www.uirsn.fr
www.jrsn.fr
www.ijrsn.fr
www.jirsn.fr
www.krsn.fr
www.ikrsn.fr
www.kirsn.fr
www.orsn.fr
www.iorsn.fr
www.oirsn.fr
www.isn.fr
www.iesn.fr
www.iresn.fr
www.iersn.fr
www.idsn.fr
www.irdsn.fr
www.idrsn.fr
www.ifsn.fr
www.irfsn.fr
www.ifrsn.fr
www.itsn.fr
www.irtsn.fr
www.itrsn.fr
www.irn.fr
www.irwn.fr
www.irswn.fr
www.irwsn.fr
www.iren.fr
www.irsen.fr
www.irdn.fr
www.irsdn.fr
www.irzn.fr
www.irszn.fr
www.irzsn.fr
www.irxn.fr
www.irsxn.fr
www.irxsn.fr
www.iran.fr
www.irsan.fr
www.irasn.fr
www.irs.fr
www.irsb.fr
www.irsnb.fr
www.irsbn.fr
www.irsh.fr
www.irsnh.fr
www.irshn.fr
www.irsj.fr
www.irsnj.fr
www.irsjn.fr
www.irsm.fr
www.irsnm.fr
www.irsmn.fr
www.irsn.net
www.irsn.org
www.irsn.info
www.irsn.biz
www.irsn.us
www.irsn.mobi
www.rsn.fr
www.irsn.fr
www.ursn.fr
www.iursn.fr
www.uirsn.fr
www.jrsn.fr
www.ijrsn.fr
www.jirsn.fr
www.krsn.fr
www.ikrsn.fr
www.kirsn.fr
www.orsn.fr
www.iorsn.fr
www.oirsn.fr
www.isn.fr
www.iesn.fr
www.iresn.fr
www.iersn.fr
www.idsn.fr
www.irdsn.fr
www.idrsn.fr
www.ifsn.fr
www.irfsn.fr
www.ifrsn.fr
www.itsn.fr
www.irtsn.fr
www.itrsn.fr
www.irn.fr
www.irwn.fr
www.irswn.fr
www.irwsn.fr
www.iren.fr
www.irsen.fr
www.irdn.fr
www.irsdn.fr
www.irzn.fr
www.irszn.fr
www.irzsn.fr
www.irxn.fr
www.irsxn.fr
www.irxsn.fr
www.iran.fr
www.irsan.fr
www.irasn.fr
www.irs.fr
www.irsb.fr
www.irsnb.fr
www.irsbn.fr
www.irsh.fr
www.irsnh.fr
www.irshn.fr
www.irsj.fr
www.irsnj.fr
www.irsjn.fr
www.irsm.fr
www.irsnm.fr
www.irsmn.fr