Access 1whois.ru. Whois Service v1.7 [Получить информацию о домене, сайте или IP-адресе]

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

1whois.ru

1007 ms

logo.jpg

331 ms

gv24b.js

144 ms

info.jpg

236 ms

icon_world.png

237 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original 1whois.ru, 8% (1 request) were made to Stg.odnoklassniki.ru and 8% (1 request) were made to Static.avast.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain 1whois.ru.

Content Size

31.0 kB

After Optimization

21.5 kB

In fact, the total size of 1whois.ru main page is 31.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 19.7 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 7.6 kB

Original 11.3 kB
After minification 10.1 kB
After compression 3.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 1.2 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 7.6 kB or 67% of the original size.

Image Optimization

-10%

Potential reduce by 1.9 kB

Original 19.7 kB
After minification 17.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. 1 Whois images are well optimized though.

Requests Now

After Optimization

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 Whois. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

RU
Language Claimed

N/A
Encoding

WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1whois.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 1whois.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of 1 Whois. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: