Cleocin.shop Test Results

Cleocin.shop Mobile Performance: 21/100
Quick overview:
Max Potential First Input Delay
2,420 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
27.3 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.
Avoid large layout shifts
7 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
First Meaningful Paint
3.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Cleocin.shop Mobile SEO: 79/100
Quick overview:
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 how to make pages mobile-friendly.
Document doesn't use legible font sizes
51.01% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
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.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Cleocin.shop Mobile Best Practices: 59/100
Quick overview:
General
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more about unload event listeners
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.
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
Cleocin.shop Mobile PWA: 63/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: Manifest does not have `theme_color`, No `<meta name="theme-color">` tag found.
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 about maskable manifest icons.
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 about splash screens. Failures: Manifest does not have `background_color`, Manifest does not have `theme_color`.
Cleocin.shop Mobile Accessibility: 55/100
Quick overview:
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
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.
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.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
`[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 how to fix duplicate `id`s.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Definition list items are not wrapped in `<dl>` elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
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.
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.
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.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Similar sites
Similar tests
www.cleocin.com
www.cleocin.net
www.cleocin.org
www.cleocin.info
www.cleocin.biz
www.cleocin.us
www.cleocin.mobi
www.leocin.shop
www.cleocin.shop
www.xleocin.shop
www.cxleocin.shop
www.xcleocin.shop
www.dleocin.shop
www.cdleocin.shop
www.dcleocin.shop
www.fleocin.shop
www.cfleocin.shop
www.fcleocin.shop
www.vleocin.shop
www.cvleocin.shop
www.vcleocin.shop
www.ceocin.shop
www.cpeocin.shop
www.clpeocin.shop
www.cpleocin.shop
www.coeocin.shop
www.cloeocin.shop
www.coleocin.shop
www.ckeocin.shop
www.clkeocin.shop
www.ckleocin.shop
www.clocin.shop
www.clwocin.shop
www.clewocin.shop
www.clweocin.shop
www.clsocin.shop
www.clesocin.shop
www.clseocin.shop
www.cldocin.shop
www.cledocin.shop
www.cldeocin.shop
www.clrocin.shop
www.clerocin.shop
www.clreocin.shop
www.clecin.shop
www.cleicin.shop
www.cleoicin.shop
www.cleiocin.shop
www.clekcin.shop
www.cleokcin.shop
www.clekocin.shop
www.clelcin.shop
www.cleolcin.shop
www.clelocin.shop
www.clepcin.shop
www.cleopcin.shop
www.clepocin.shop
www.cleoin.shop
www.cleoxin.shop
www.cleocxin.shop
www.cleoxcin.shop
www.cleodin.shop
www.cleocdin.shop
www.cleodcin.shop
www.cleofin.shop
www.cleocfin.shop
www.cleofcin.shop
www.cleovin.shop
www.cleocvin.shop
www.cleovcin.shop
www.cleocn.shop
www.cleocun.shop
www.cleociun.shop
www.cleocuin.shop
www.cleocjn.shop
www.cleocijn.shop
www.cleocjin.shop
www.cleockn.shop
www.cleocikn.shop
www.cleockin.shop
www.cleocon.shop
www.cleocion.shop
www.cleocoin.shop
www.cleoci.shop
www.cleocib.shop
www.cleocinb.shop
www.cleocibn.shop
www.cleocih.shop
www.cleocinh.shop
www.cleocihn.shop
www.cleocij.shop
www.cleocinj.shop
www.cleocim.shop
www.cleocinm.shop
www.cleocimn.shop
Last Tested: