C2i.net Test Results
C2i.net Mobile Performance: 36/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 1,650 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 47 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.
Minimize main-thread work
6.2 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
Largest Contentful Paint element
8,440 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Defer offscreen images
Potential savings of 10 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.
Avoid multiple page redirects
Potential savings of 1,410 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce JavaScript execution time
3.3 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.
Serve images in next-gen formats
Potential savings of 8 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 JavaScript
Potential savings of 563 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,100 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.
Preload Largest Contentful Paint image
Potential savings of 150 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
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 serving legacy JavaScript to modern browsers
Potential savings of 32 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
33 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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`.
Max Potential First Input Delay
1,180 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.
Time to Interactive
11.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.
C2i.net Mobile SEO: 85/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt. Lighthouse was unable to download a robots.txt file
C2i.net Mobile Best Practices: 62/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 about this errors in console diagnostic audit
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
C2i.net Mobile Accessibility: 65/100
Quick overview:
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.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
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.c2i.com
www.c2i.net
www.c2i.org
www.c2i.info
www.c2i.biz
www.c2i.us
www.c2i.mobi
www.2i.net
www.c2i.net
www.x2i.net
www.cx2i.net
www.xc2i.net
www.d2i.net
www.cd2i.net
www.dc2i.net
www.f2i.net
www.cf2i.net
www.fc2i.net
www.v2i.net
www.cv2i.net
www.vc2i.net
www.ci.net
www.c2.net
www.c2u.net
www.c2iu.net
www.c2ui.net
www.c2j.net
www.c2ij.net
www.c2ji.net
www.c2k.net
www.c2ik.net
www.c2ki.net
www.c2o.net
www.c2io.net
www.c2oi.net
www.c2i.net
www.c2i.org
www.c2i.info
www.c2i.biz
www.c2i.us
www.c2i.mobi
www.2i.net
www.c2i.net
www.x2i.net
www.cx2i.net
www.xc2i.net
www.d2i.net
www.cd2i.net
www.dc2i.net
www.f2i.net
www.cf2i.net
www.fc2i.net
www.v2i.net
www.cv2i.net
www.vc2i.net
www.ci.net
www.c2.net
www.c2u.net
www.c2iu.net
www.c2ui.net
www.c2j.net
www.c2ij.net
www.c2ji.net
www.c2k.net
www.c2ik.net
www.c2ki.net
www.c2o.net
www.c2io.net
www.c2oi.net