Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

osoo.ru

Котлы в Екатеринбурге

Page Load Speed

6.5 sec in total

First Response

890 ms

Resources Loaded

4.9 sec

Page Rendered

749 ms

About Website

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

Отопительные котлы для дома в Екатеринбурге

Visit osoo.ru

Key Findings

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

Performance Metrics

osoo.ru performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.088

92/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

osoo.ru

890 ms

5300b6fa692c5a562b968720312c839a

1337 ms

jquery.min.js

329 ms

styles_articles_tpl.css

361 ms

highslide.min.css

362 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 80% of them (112 requests) were addressed to the original Osoo.ru, 11% (15 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Counter.megagroup.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Osoo.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 330.1 kB (16%)

Content Size

2.0 MB

After Optimization

1.7 MB

In fact, the total size of Osoo.ru main page is 2.0 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.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 168.1 kB

  • Original 192.8 kB
  • After minification 115.8 kB
  • After compression 24.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 76.9 kB, which is 40% 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 168.1 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 22.4 kB

  • Original 1.2 MB
  • After minification 1.2 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. Osoo images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 48.2 kB

  • Original 365.9 kB
  • After minification 365.9 kB
  • After compression 317.7 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 48.2 kB or 13% of the original size.

CSS Optimization

-33%

Potential reduce by 91.3 kB

  • Original 275.5 kB
  • After minification 275.5 kB
  • After compression 184.2 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. Osoo.ru needs all CSS files to be minified and compressed as it can save up to 91.3 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (50%)

Requests Now

123

After Optimization

61

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

Accessibility Review

osoo.ru accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

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

Image elements do not have [alt] attributes

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

osoo.ru best practices score

67

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

osoo.ru SEO score

82

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Osoo.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 Osoo.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 Osoo. 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: