Whose.land Site Title

Whose Land - Добро пожаловать

Whose.land Test Results

Whose.land Mobile Performance: 84/100
Quick overview:
Max Potential First Input Delay
490 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.1 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.
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 1,900 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 8 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 187 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.

Whose.land Mobile SEO: 80/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.

Whose.land Mobile Best Practices: 59/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
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Uses third-party cookies
21 cookies found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
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.
Whose.land Mobile Accessibility: 85/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.
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.
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 about the `lang` attribute.
Similar tests
www.whose.com
www.whose.net
www.whose.org
www.whose.info
www.whose.biz
www.whose.us
www.whose.mobi
www.hose.land
www.whose.land
www.qhose.land
www.wqhose.land
www.qwhose.land
www.ahose.land
www.wahose.land
www.awhose.land
www.shose.land
www.wshose.land
www.swhose.land
www.ehose.land
www.wehose.land
www.ewhose.land
www.wose.land
www.wbose.land
www.whbose.land
www.wbhose.land
www.wgose.land
www.whgose.land
www.wghose.land
www.wyose.land
www.whyose.land
www.wyhose.land
www.wuose.land
www.whuose.land
www.wuhose.land
www.wjose.land
www.whjose.land
www.wjhose.land
www.wnose.land
www.whnose.land
www.wnhose.land
www.whse.land
www.whise.land
www.whoise.land
www.whiose.land
www.whkse.land
www.whokse.land
www.whkose.land
www.whlse.land
www.wholse.land
www.whlose.land
www.whpse.land
www.whopse.land
www.whpose.land
www.whoe.land
www.whowe.land
www.whoswe.land
www.whowse.land
www.whoee.land
www.whosee.land
www.whoese.land
www.whode.land
www.whosde.land
www.whodse.land
www.whoze.land
www.whosze.land
www.whozse.land
www.whoxe.land
www.whosxe.land
www.whoxse.land
www.whoae.land
www.whosae.land
www.whoase.land
www.whos.land
www.whosw.land
www.whosew.land
www.whoss.land
www.whoses.land
www.whosse.land
www.whosd.land
www.whosed.land
www.whosr.land
www.whoser.land
www.whosre.land
Last Tested: