Tools & Wizards About Us
baikaltea.ru screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

baikaltea.ru

Иван-чай Байкальский, Оптом от Производителя! Baikal tea

Page Load Speed

3.4 sec in total

First Response

626 ms

Resources Loaded

2.5 sec

Page Rendered

282 ms

baikaltea.ru screenshot

About Website

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

Иван-чай Байкальский оптом от производителя. Оптовая продажа иван-чая. Предлагаем Иван-чай крупным и мелким оптом.

Visit baikaltea.ru

Key Findings

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

Performance Metrics

baikaltea.ru performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value520 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

baikaltea.ru

626 ms

site-83a5e7d352.css

599 ms

styles-31e13ecf2f.css

361 ms

vendor.js

907 ms

runtime_editor_v1.js

390 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 9% of them (3 requests) were addressed to the original Baikaltea.ru, 36% (12 requests) were made to Baikal-tea.nethouse.ru and 24% (8 requests) were made to S.siteapi.org. The less responsive or slowest element that took the longest time to load (907 ms) relates to the external source S2.siteapi.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.6 kB (18%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Baikaltea.ru main page is 1.7 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. 45% of websites need less resources to load. Images take 826.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 38.1 kB

  • Original 49.9 kB
  • After minification 40.0 kB
  • After compression 11.8 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 9.9 kB, which is 20% 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 38.1 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 11.5 kB

  • Original 826.5 kB
  • After minification 815.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. Baikal Tea images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 199 B

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

CSS Optimization

-81%

Potential reduce by 248.8 kB

  • Original 308.4 kB
  • After minification 308.0 kB
  • After compression 59.6 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. Baikaltea.ru needs all CSS files to be minified and compressed as it can save up to 248.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (28%)

Requests Now

25

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

baikaltea.ru

baikaltea.ru

626 ms

site-83a5e7d352.css

site-83a5e7d352.css

599 ms

styles-31e13ecf2f.css

styles-31e13ecf2f.css

361 ms

vendor.js

vendor.js

907 ms

runtime_editor_v1.js

runtime_editor_v1.js

390 ms

vendor-54b0e4b0a8.min.js

vendor-54b0e4b0a8.min.js

851 ms

translate.js

translate.js

144 ms

scripts-4efb77bafc.js

scripts-4efb77bafc.js

631 ms

element.js

element.js

41 ms

6969781.puo93k3y2t.W215.jpg

6969781.puo93k3y2t.W215.jpg

237 ms

71392747.izqx45fqlj.W665.jpg

71392747.izqx45fqlj.W665.jpg

357 ms

0.jpg

0.jpg

36 ms

play-5df78d3d30.png

play-5df78d3d30.png

118 ms

footer_logo-32e4dda856.png

footer_logo-32e4dda856.png

121 ms

0.jpg

0.jpg

47 ms

0.jpg

0.jpg

47 ms

0.jpg

0.jpg

47 ms

71392757.opuw7go988.W665.jpg

71392757.opuw7go988.W665.jpg

357 ms

71392770.nlfumeb7ui.W665.jpg

71392770.nlfumeb7ui.W665.jpg

365 ms

71392791.gyuin5jfx0.W665.jpg

71392791.gyuin5jfx0.W665.jpg

364 ms

71392811.per29la51i.W665.jpg

71392811.per29la51i.W665.jpg

365 ms

71392820.h5ckgvah1b.W665.jpg

71392820.h5ckgvah1b.W665.jpg

365 ms

0-609d960b61.png

0-609d960b61.png

120 ms

get_image-56caf33695.png

get_image-56caf33695.png

550 ms

8m840D1hJ8

8m840D1hJ8

525 ms

http:/

http:/

26 ms

71392747.izqx45fqlj.W665.jpg

71392747.izqx45fqlj.W665.jpg

840 ms

71392757.opuw7go988.W665.jpg

71392757.opuw7go988.W665.jpg

751 ms

71392791.gyuin5jfx0.W665.jpg

71392791.gyuin5jfx0.W665.jpg

868 ms

71392811.per29la51i.W665.jpg

71392811.per29la51i.W665.jpg

749 ms

71392770.nlfumeb7ui.W665.jpg

71392770.nlfumeb7ui.W665.jpg

762 ms

71392820.h5ckgvah1b.W665.jpg

71392820.h5ckgvah1b.W665.jpg

763 ms

8m840D1hJ8

8m840D1hJ8

266 ms

Accessibility Review

baikaltea.ru accessibility score

79

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

baikaltea.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

baikaltea.ru SEO score

92

Search Engine Optimization Advices

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 Baikaltea.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 Baikaltea.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

baikaltea.ru

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