Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

66.ru

66.RU. Здесь все всё понимают

Page Load Speed

12.9 sec in total

First Response

1.1 sec

Resources Loaded

11.4 sec

Page Rendered

382 ms

66.ru screenshot

About Website

Welcome to 66.ru homepage info - get ready to check 66 best content for Russia right away, or after learning these important things about 66.ru

Visit 66.ru

Key Findings

We analyzed 66.ru page load time and found that the first response time was 1.1 sec and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

66.ru performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.179

67/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

66.ru

1077 ms

556 ms

PT_Sans_Narrow.css

1955 ms

client.css

1231 ms

client.js

1415 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 66.ru, 17% (27 requests) were made to S.66.ru and 13% (20 requests) were made to Show.adlift.ru. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source S.66.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (39%)

Content Size

3.1 MB

After Optimization

1.9 MB

In fact, the total size of 66.ru main page is 3.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 126.5 kB

  • Original 156.2 kB
  • After minification 138.6 kB
  • After compression 29.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 17.6 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 126.5 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 39.5 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. 66 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 740.2 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 338.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 740.2 kB or 69% of the original size.

CSS Optimization

-56%

Potential reduce by 284.6 kB

  • Original 512.4 kB
  • After minification 505.0 kB
  • After compression 227.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 66.ru needs all CSS files to be minified and compressed as it can save up to 284.6 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (48%)

Requests Now

149

After Optimization

78

The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 66. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

66.ru accessibility score

59

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Internationalization and localization

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

Impact

Issue

High

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

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.

Impact

Issue

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

66.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

66.ru SEO score

92

Search Engine Optimization Advices

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 more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 66.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that 66.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of 66. 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: