Access 202.by. Питьевая вода 202

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.811

4/100

15%

TTI (Time to Interactive)

Value6.9 s

53/100

10%

202.by

407 ms

www.202.by

1300 ms

template_bfcb2ef0390c8cde1359fa0984390a0a0.css

554 ms

template_66ccd1cd3ba2c5a6d55267ccf2678356.js

1370 ms

watch.js

128 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 85% of them (94 requests) were addressed to the original 202.by, 4% (4 requests) were made to Google-analytics.com and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain 202.by.

Content Size

3.0 MB

After Optimization

2.4 MB

In fact, the total size of 202.by main page is 3.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. 65% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 103.3 kB

Original 122.7 kB
After minification 99.4 kB
After compression 19.4 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 23.3 kB, which is 19% 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 103.3 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 126.3 kB

Original 2.4 MB
After minification 2.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. 202 images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 43.7 kB

Original 72.4 kB
After minification 72.3 kB
After compression 28.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 43.7 kB or 60% of the original size.

CSS Optimization

-86%

Potential reduce by 267.5 kB

Original 312.7 kB
After minification 298.3 kB
After compression 45.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. 202.by needs all CSS files to be minified and compressed as it can save up to 267.5 kB or 86% of the original size.

Requests Now

102

After Optimization

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

Accessibility Issues

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.

High

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

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

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

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 202.by 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 202.by 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

202.by

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Питьевая вода 202

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

202.by

www.202.by

template_bfcb2ef0390c8cde1359fa0984390a0a0.css

template_66ccd1cd3ba2c5a6d55267ccf2678356.js

watch.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

202.by

www.202.by

template_bfcb2ef0390c8cde1359fa0984390a0a0.css

template_66ccd1cd3ba2c5a6d55267ccf2678356.js

watch.js

analytics.js

icon-location-red.png

icons-close.png

icon-arr-left-red.png

icon-person-header.png

logo.png

logo-slogan.png

i-big-phone.png

gsm-202.png

gsm-arr.png

basket-small.png

spritesheet.png

logo-context-small.png

bg-main-banner.png

pic_butylka_1_.png

zheltaya.png

krasnaya.png

bg-shadow-clock.png

calendar-clock.png

bg-shadow-car.png

calendar-car.png

3.png

1.png

2.png

icon-sootv-prod.png

pic34.png

voda2022.png

red.png

kompress.png

pic35.png

bez_okhlazhdeniya.png

kompressorny.png

pic36.png

kholodilnik.png

pic37.png

2323.jpg

collect

collect