Cyu.fr Test Results
Cyu.fr Mobile Performance: 26/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images. Potential savings of 9,344 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Serve images in next-gen formats. Potential savings of 5,230 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Efficiently encode images. Potential savings of 2,659 KiB
Optimized images load faster and consume less cellular data. Learn more.
Preload key requests. Potential savings of 2,940 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Remove unused JavaScript. Potential savings of 273 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Enable text compression. Potential savings of 261 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Eliminate render-blocking resources. Potential savings of 1,130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Reduce initial server response time. Root document took 1,220 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused CSS. Potential savings of 111 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoid enormous network payloads
Total size was 12,401 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
5.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid an excessive DOM size
1,444 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Reduce JavaScript execution time
2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid long main-thread tasks
7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
31 requests • 12,401 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Cyu.fr Mobile SEO: 91/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more. Description text is empty.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
78% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Cyu.fr Mobile Best Practices: 71/100
Quick overview:
General
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
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.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more.
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 servedover 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.
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Cyu.fr Mobile Progressive Web App: 0/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 376px does not match the window size of 360px.
Contains some content when JavaScript is not available
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more.
Redirects HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
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 servedover 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.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 10.3 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Cyu.fr Mobile Accessibility: 76/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 are not valid or misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
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 more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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 more.
Similar sites
Similar tests
www.cyu.com
www.cyu.net
www.cyu.org
www.cyu.info
www.cyu.biz
www.cyu.us
www.cyu.mobi
www.yu.fr
www.cyu.fr
www.xyu.fr
www.cxyu.fr
www.xcyu.fr
www.dyu.fr
www.cdyu.fr
www.dcyu.fr
www.fyu.fr
www.cfyu.fr
www.fcyu.fr
www.vyu.fr
www.cvyu.fr
www.vcyu.fr
www.cu.fr
www.ctu.fr
www.cytu.fr
www.ctyu.fr
www.cgu.fr
www.cygu.fr
www.cgyu.fr
www.chu.fr
www.cyhu.fr
www.chyu.fr
www.cuu.fr
www.cyuu.fr
www.cuyu.fr
www.cy.fr
www.cyy.fr
www.cyuy.fr
www.cyyu.fr
www.cyh.fr
www.cyuh.fr
www.cyj.fr
www.cyuj.fr
www.cyju.fr
www.cyi.fr
www.cyui.fr
www.cyiu.fr
www.cyu.net
www.cyu.org
www.cyu.info
www.cyu.biz
www.cyu.us
www.cyu.mobi
www.yu.fr
www.cyu.fr
www.xyu.fr
www.cxyu.fr
www.xcyu.fr
www.dyu.fr
www.cdyu.fr
www.dcyu.fr
www.fyu.fr
www.cfyu.fr
www.fcyu.fr
www.vyu.fr
www.cvyu.fr
www.vcyu.fr
www.cu.fr
www.ctu.fr
www.cytu.fr
www.ctyu.fr
www.cgu.fr
www.cygu.fr
www.cgyu.fr
www.chu.fr
www.cyhu.fr
www.chyu.fr
www.cuu.fr
www.cyuu.fr
www.cuyu.fr
www.cy.fr
www.cyy.fr
www.cyuy.fr
www.cyyu.fr
www.cyh.fr
www.cyuh.fr
www.cyj.fr
www.cyuj.fr
www.cyju.fr
www.cyi.fr
www.cyui.fr
www.cyiu.fr