Dns.watch Site Title

Fast, free and uncensored. DNS.WATCH. - DNS.WATCH

Dns.watch Meta Description

DNS.WATCH is a fast, free and uncensored DNS-Server (or more specific, a DNS resolver). Service is provided world-wide and free-of-charge for everyone.

Dns.watch Test Results

Dns.watch Desktop Performance: 90/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce initial server response time. Root document took 900 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Eliminate render-blocking resources. Potential savings of 190 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.
Serve images in next-gen formats. Potential savings of 134 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.
Remove unused CSS. Potential savings of 26 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.
Serve static assets with an efficient cache policy
18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Keep request counts low and transfer sizes small
28 requests • 712 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
21 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.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Dns.watch Desktop SEO: 90/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.

Dns.watch Desktop Best Practices: 85/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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.
Dns.watch Desktop Progressive Web App: 44/100
Quick overview:
Installable
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.
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.
Fast and reliable
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.
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. 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.
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.
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
Dns.watch Desktop Accessibility: 81/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.
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.
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.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Similar sites
Similar tests
www.dns.com
www.dns.net
www.dns.org
www.dns.info
www.dns.biz
www.dns.us
www.dns.mobi
www.ns.watch
www.dns.watch
www.xns.watch
www.dxns.watch
www.xdns.watch
www.sns.watch
www.dsns.watch
www.sdns.watch
www.ens.watch
www.dens.watch
www.edns.watch
www.rns.watch
www.drns.watch
www.rdns.watch
www.fns.watch
www.dfns.watch
www.fdns.watch
www.cns.watch
www.dcns.watch
www.cdns.watch
www.ds.watch
www.dbs.watch
www.dnbs.watch
www.dbns.watch
www.dhs.watch
www.dnhs.watch
www.dhns.watch
www.djs.watch
www.dnjs.watch
www.djns.watch
www.dms.watch
www.dnms.watch
www.dmns.watch
www.dn.watch
www.dnw.watch
www.dnsw.watch
www.dnws.watch
www.dne.watch
www.dnse.watch
www.dnes.watch
www.dnd.watch
www.dnsd.watch
www.dnds.watch
www.dnz.watch
www.dnsz.watch
www.dnzs.watch
www.dnx.watch
www.dnsx.watch
www.dnxs.watch
www.dna.watch
www.dnsa.watch
www.dnas.watch
Last Tested: