Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

soto.ru

Главная

Page Load Speed

3.8 sec in total

First Response

547 ms

Resources Loaded

2.8 sec

Page Rendered

418 ms

soto.ru screenshot

About Website

Visit soto.ru now to see the best up-to-date Soto content and also check out these interesting facts you probably never knew about soto.ru

Главная

Visit soto.ru

Key Findings

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

Performance Metrics

soto.ru performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

soto.ru

547 ms

common-bundle.js

390 ms

common-bundle.css

528 ms

css

43 ms

css

59 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 43% of them (12 requests) were addressed to the original Soto.ru, 50% (14 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Soto.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.2 kB (32%)

Content Size

1.3 MB

After Optimization

905.0 kB

In fact, the total size of Soto.ru main page is 1.3 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.0 kB

  • Original 14.2 kB
  • After minification 14.1 kB
  • After compression 3.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.0 kB or 77% of the original size.

Image Optimization

-34%

Potential reduce by 416.2 kB

  • Original 1.2 MB
  • After minification 808.1 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. Obviously, Soto needs image optimization as it can save up to 416.2 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 50.6 kB
  • After minification 50.6 kB
  • After compression 50.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 28 B

  • Original 43.1 kB
  • After minification 43.1 kB
  • After compression 43.1 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. Soto.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (25%)

Requests Now

12

After Optimization

9

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

Accessibility Review

soto.ru accessibility score

95

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

soto.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

soto.ru SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Soto.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 Soto.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 data is detected on the main page of Soto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: