Codelo.pro Test Results

Codelo.pro Mobile Performance: 80/100
Quick overview:
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 600 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
4,090 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 50 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.
Eliminate render-blocking resources
Potential savings of 2,570 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.
Enable text compression
Potential savings of 427 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Reduce unused CSS
Potential savings of 463 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.
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Efficiently encode images
Potential savings of 20 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
First Meaningful Paint
3.3 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
3.9 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.

Codelo.pro Mobile SEO: 36/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description. Description text is empty.
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.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Codelo.pro Mobile Best Practices: 72/100
Quick overview:
Trust and Safety
Does not use HTTPS
15 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.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
Codelo.pro Mobile Accessibility: 55/100
Quick overview:
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
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.
`<object>` elements do not have alternate text
Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
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.codelo.com
www.codelo.net
www.codelo.org
www.codelo.info
www.codelo.biz
www.codelo.us
www.codelo.mobi
www.odelo.pro
www.codelo.pro
www.xodelo.pro
www.cxodelo.pro
www.xcodelo.pro
www.dodelo.pro
www.cdodelo.pro
www.dcodelo.pro
www.fodelo.pro
www.cfodelo.pro
www.fcodelo.pro
www.vodelo.pro
www.cvodelo.pro
www.vcodelo.pro
www.cdelo.pro
www.cidelo.pro
www.coidelo.pro
www.ciodelo.pro
www.ckdelo.pro
www.cokdelo.pro
www.ckodelo.pro
www.cldelo.pro
www.coldelo.pro
www.clodelo.pro
www.cpdelo.pro
www.copdelo.pro
www.cpodelo.pro
www.coelo.pro
www.coxelo.pro
www.codxelo.pro
www.coxdelo.pro
www.coselo.pro
www.codselo.pro
www.cosdelo.pro
www.coeelo.pro
www.codeelo.pro
www.coedelo.pro
www.corelo.pro
www.codrelo.pro
www.cordelo.pro
www.cofelo.pro
www.codfelo.pro
www.cofdelo.pro
www.cocelo.pro
www.codcelo.pro
www.cocdelo.pro
www.codlo.pro
www.codwlo.pro
www.codewlo.pro
www.codwelo.pro
www.codslo.pro
www.codeslo.pro
www.coddlo.pro
www.codedlo.pro
www.coddelo.pro
www.codrlo.pro
www.coderlo.pro
www.codeo.pro
www.codepo.pro
www.codelpo.pro
www.codeplo.pro
www.codeoo.pro
www.codeloo.pro
www.codeolo.pro
www.codeko.pro
www.codelko.pro
www.codeklo.pro
www.codel.pro
www.codeli.pro
www.codeloi.pro
www.codelio.pro
www.codelk.pro
www.codelok.pro
www.codell.pro
www.codelol.pro
www.codello.pro
www.codelp.pro
www.codelop.pro
Last Tested: