Dos.zone Site Title

Dos.Zone

Dos.zone Meta Description

Dos.Zone play dos games in browser

Dos.zone Test Results

Dos.zone Mobile Performance: 65/100
Quick overview:
Max Potential First Input Delay
300 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
5.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.
First Meaningful Paint
2.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Potential savings of 124 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.
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Largest Contentful Paint element
2,810 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Eliminate render-blocking resources
Potential savings of 820 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 multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Enable text compression
Potential savings of 601 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Minimize main-thread work
2.0 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
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
Reduce unused JavaScript
Potential savings of 114 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.
Serve static assets with an efficient cache policy
26 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Properly size images
Potential savings of 336 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

Dos.zone Mobile SEO: 100/100
Quick overview:

Dos.zone Mobile Best Practices: 79/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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.
Dos.zone Mobile Accessibility: 80/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.
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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Similar sites
Similar tests
www.dos.com
www.dos.net
www.dos.org
www.dos.info
www.dos.biz
www.dos.us
www.dos.mobi
www.os.zone
www.dos.zone
www.xos.zone
www.dxos.zone
www.xdos.zone
www.sos.zone
www.dsos.zone
www.sdos.zone
www.eos.zone
www.deos.zone
www.edos.zone
www.ros.zone
www.dros.zone
www.rdos.zone
www.fos.zone
www.dfos.zone
www.fdos.zone
www.cos.zone
www.dcos.zone
www.cdos.zone
www.ds.zone
www.dis.zone
www.dois.zone
www.dios.zone
www.dks.zone
www.doks.zone
www.dkos.zone
www.dls.zone
www.dols.zone
www.dlos.zone
www.dps.zone
www.dops.zone
www.dpos.zone
www.do.zone
www.dow.zone
www.dosw.zone
www.dows.zone
www.doe.zone
www.dose.zone
www.does.zone
www.dod.zone
www.dosd.zone
www.dods.zone
www.doz.zone
www.dosz.zone
www.dozs.zone
www.dox.zone
www.dosx.zone
www.doxs.zone
www.doa.zone
www.dosa.zone
www.doas.zone
Last Tested: