Tools & Wizards About Us
tearoad.ru screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

tearoad.ru

Великий чайный путь | Tea Road

Page Load Speed

9.8 sec in total

First Response

428 ms

Resources Loaded

8.2 sec

Page Rendered

1.1 sec

tearoad.ru screenshot

About Website

Click here to check amazing Tea Road content for Russia. Otherwise, check out these important facts you probably never knew about tearoad.ru

Традиция чаепития с молоком имеет давние истоки и является одним из распространенных способов приготовления и употребления чая во многих культурах. Эта практика широко распространена в Великобритании,...

Visit tearoad.ru

Key Findings

We analyzed Tearoad.ru page load time and found that the first response time was 428 ms and then it took 9.4 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

tearoad.ru performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value29.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,260 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value44.3 s

0/100

10%

Network Requests Diagram

tearoad.ru

428 ms

www.tearoad.ru

801 ms

screen.css

95 ms

style.css

192 ms

jd.gallery.css

286 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 48% of them (47 requests) were addressed to the original Tearoad.ru, 16% (16 requests) were made to I.okcdn.ru and 7% (7 requests) were made to St6-21.vk.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Tearoad.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.2 kB (1%)

Content Size

11.6 MB

After Optimization

11.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 41.5 kB

  • Original 52.3 kB
  • After minification 47.8 kB
  • After compression 10.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. 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 41.5 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 27.2 kB

  • Original 10.9 MB
  • After minification 10.9 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. Tea Road images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 28.4 kB

  • Original 214.2 kB
  • After minification 214.2 kB
  • After compression 185.8 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 28.4 kB or 13% of the original size.

CSS Optimization

-8%

Potential reduce by 31.2 kB

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

Requests Breakdown

Number of requests can be reduced by 56 (60%)

Requests Now

93

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tearoad.ru

tearoad.ru

428 ms

www.tearoad.ru

www.tearoad.ru

801 ms

screen.css

screen.css

95 ms

style.css

style.css

192 ms

jd.gallery.css

jd.gallery.css

286 ms

mootools-1.2.5-core-yc.js

mootools-1.2.5-core-yc.js

383 ms

mootools-1.2-more.js

mootools-1.2-more.js

286 ms

jd.gallery.js

jd.gallery.js

287 ms

jd.gallery.transitions.js

jd.gallery.transitions.js

286 ms

jQuery.1.13.js

jQuery.1.13.js

396 ms

jquery.hc-sticky.min.js

jquery.hc-sticky.min.js

378 ms

styles.css

styles.css

381 ms

front_end_style.css

front_end_style.css

381 ms

dashicons.min.css

dashicons.min.css

479 ms

desktop_style.css

desktop_style.css

473 ms

wpcf.css

wpcf.css

475 ms

jetpack.css

jetpack.css

475 ms

pagenavi-css.css

pagenavi-css.css

474 ms

script.js

script.js

522 ms

lib.js

lib.js

550 ms

lib.js

lib.js

518 ms

ex.js

ex.js

586 ms

adsbygoogle.js

adsbygoogle.js

169 ms

gas.js

gas.js

627 ms

627 ms

watch.js

watch.js

2 ms

devicepx-jetpack.js

devicepx-jetpack.js

24 ms

wp-embed.min.js

wp-embed.min.js

477 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

145 ms

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

233 ms

print.css

print.css

96 ms

network.css

network.css

107 ms

background.png

background.png

96 ms

logo.png

logo.png

95 ms

1.jpg

1.jpg

96 ms

2.jpg

2.jpg

286 ms

3.jpg

3.jpg

191 ms

4.jpg

4.jpg

282 ms

5.jpg

5.jpg

190 ms

HL2hsSRzMZM-14.jpg

HL2hsSRzMZM-14.jpg

474 ms

HL2hsSRzMZM-12.jpg

HL2hsSRzMZM-12.jpg

382 ms

HL2hsSRzMZM-9.jpg

HL2hsSRzMZM-9.jpg

569 ms

HL2hsSRzMZM-16.jpg

HL2hsSRzMZM-16.jpg

290 ms

HL2hsSRzMZM-17.jpg

HL2hsSRzMZM-17.jpg

474 ms

HL2hsSRzMZM-11.jpg

HL2hsSRzMZM-11.jpg

383 ms

HL2hsSRzMZM-8.jpg

HL2hsSRzMZM-8.jpg

1346 ms

HL2hsSRzMZM-18.jpg

HL2hsSRzMZM-18.jpg

668 ms

HL2hsSRzMZM-10.jpg

HL2hsSRzMZM-10.jpg

478 ms

HL2hsSRzMZM-19.jpg

HL2hsSRzMZM-19.jpg

5789 ms

search.gif

search.gif

569 ms

pagenav-hover.png

pagenav-hover.png

575 ms

nav-hover.png

nav-hover.png

661 ms

nav-background.png

nav-background.png

662 ms

context.js

context.js

1082 ms

sidebar-tab.png

sidebar-tab.png

640 ms

connect.js

connect.js

642 ms

upload.gif

upload.gif

116 ms

bullet.gif

bullet.gif

724 ms

widget_community.php

widget_community.php

271 ms

hit

hit

496 ms

loading-bar-black.gif

loading-bar-black.gif

685 ms

fleche1.png

fleche1.png

690 ms

fleche2.png

fleche2.png

691 ms

loader_nav211011784924_3.js

loader_nav211011784924_3.js

266 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

933 ms

lite.93f44416.css

lite.93f44416.css

636 ms

lang3_2.js

lang3_2.js

632 ms

c3d11fba.db7dbf71.js

c3d11fba.db7dbf71.js

499 ms

xdm.js

xdm.js

500 ms

base.ec2ae8ae.css

base.ec2ae8ae.css

542 ms

hit

hit

121 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

264 ms

dk

dk

136 ms

widget_group.6bf9c10f.css

widget_group.6bf9c10f.css

1068 ms

i

i

642 ms

i

i

650 ms

i

i

682 ms

i

i

684 ms

i

i

786 ms

i

i

671 ms

i

i

766 ms

i

i

777 ms

i

i

805 ms

i

i

809 ms

i

i

907 ms

i

i

892 ms

i

i

986 ms

i

i

955 ms

i

i

961 ms

i

i

937 ms

browsers.png

browsers.png

98 ms

upload.gif

upload.gif

81 ms

code.js

code.js

763 ms

logo_ok-widget@2x.png

logo_ok-widget@2x.png

132 ms

counter

counter

127 ms

dyn-goal-config.js

dyn-goal-config.js

251 ms

tracker

tracker

128 ms

Accessibility Review

tearoad.ru accessibility score

83

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tearoad.ru SEO score

85

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

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

tearoad.ru

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