5.4 sec in total
580 ms
4 sec
833 ms
Visit tea24.ru now to see the best up-to-date Tea24 content for Russia and also check out these interesting facts you probably never knew about tea24.ru
Купить чай в интернет-магазине недорого. Большой выбор чая, кофе, аксессуаров и сладостей. Купить чай в Москве. Низкие цены на чай, зерновой кофе. Быстрая доставка и гарантия высокого качества.
Visit tea24.ruWe analyzed Tea24.ru page load time and found that the first response time was 580 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tea24.ru performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value3.7 s
58/100
25%
Value7.0 s
32/100
10%
Value0 ms
100/100
30%
Value0.013
100/100
15%
Value3.7 s
90/100
10%
580 ms
747 ms
284 ms
561 ms
422 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 95% of them (73 requests) were addressed to the original Tea24.ru, 3% (2 requests) were made to Mc.yandex.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Tea24.ru.
Page size can be reduced by 96.0 kB (5%)
1.9 MB
1.8 MB
In fact, the total size of Tea24.ru main page is 1.9 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.6 MB which makes up the majority of the site volume.
Potential reduce by 47.3 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 10.4 kB, which is 18% 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 47.3 kB or 80% of the original size.
Potential reduce by 33.4 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. Tea24 images are well optimized though.
Potential reduce by 5.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.
Potential reduce by 9.7 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. Tea24.ru needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 18% of the original size.
Number of requests can be reduced by 13 (18%)
72
59
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tea24. 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 from 8 to 1 for CSS and as a result speed up the page load time.
tea24.ru
580 ms
tea24.ru
747 ms
jquery-2.1.1.min.js
284 ms
bootstrap.min.css
561 ms
bootstrap.min.js
422 ms
font-awesome.min.css
423 ms
css
33 ms
style.css
424 ms
fonts.css
422 ms
blog.css
423 ms
magnific-popup.css
580 ms
blog.css
580 ms
jquery.magnific-popup.min.js
581 ms
cdek_official.js
583 ms
common.js
583 ms
custom.js
699 ms
bg.png
143 ms
header-bg.png
141 ms
tea19CBEBD82B0B6BDB08F+BEB1BBB081828C+1.png
144 ms
cart-ico.png
143 ms
search-ico.png
146 ms
menu-li.png
144 ms
green_leaf.png
280 ms
pin.png
281 ms
pink_leaf.png
282 ms
brown_leaf.png
283 ms
red_leaf.png
285 ms
Longjing-Tea01.jpg
840 ms
arr-more.png
420 ms
Puer11.jpg
427 ms
ZHasminovayazhemchuzhina1.jpg
699 ms
bilochun.jpg
842 ms
bajmudan1.jpg
840 ms
Alishan.jpg
836 ms
zelenijmolochnij.jpg
708 ms
arr-bread.png
841 ms
head-dot.png
848 ms
head-ico.png
975 ms
lunczin-200x133.jpg
978 ms
genmajchayaponiya-200x133.jpg
981 ms
bajhaoinchzhen2-200x133.jpg
980 ms
nefritovij2-200x133.jpg
982 ms
9e2d3888-b433-413f-b3e3-6e91cd836585-200x133.jpg
1071 ms
28520710-1e16-476a-b244-1a993a11eb00-200x133.jpg
1114 ms
Keniya1-200x133.jpg
1119 ms
Laos-200x133.jpg
1120 ms
Ulun1-200x133.jpg
1121 ms
Tajvan2-200x133.jpg
1122 ms
CladkijOsmantus-200x133.jpg
1128 ms
29af14b7-d9b2-4bd8-b23b-4c4f2172b4af-200x133.jpg
1254 ms
644607e9-36f9-4235-b597-22899d429092-200x133.jpg
1260 ms
SHupuer-200x133.jpg
1206 ms
tag.js
926 ms
3131265-webfont.woff
1123 ms
fontawesome-webfont.woff
1148 ms
65080ac2b181642afa17a46cd85bda96-200x133.png
1148 ms
BergamotLajm-200x133.jpg
1253 ms
6cae9aa6-fca3-46ee-843d-d995fee12cec-200x133.jpg
1259 ms
afb0aeb3-0bba-4676-bacf-7e51b712fae7-200x133.jpg
1261 ms
2d328dfe-8387-440e-9a04-33fae158c32c-200x133.jpg
1125 ms
54c1f7dc-4f83-4b77-99c1-c17f82e2763a-200x133.jpg
1125 ms
1e7bf1b0-bf57-479f-aa09-87891fabf9c7-200x133.jpg
1132 ms
6ae91576-4e0e-4d0e-a111-17e8d83290e7-200x133.jpg
1253 ms
13621951-c659-49a9-af0d-b8059c67a767-200x133.jpg
1258 ms
fd2b1a0d-bcec-440d-bdaf-6c620999fd32-200x133.jpg
1126 ms
83375804-9803-4388-9682-f323c1a42b13-200x133.jpg
1119 ms
Keniya-200x133.jpg
849 ms
867124bd-d9de-43ed-865c-de34101ad7b6-200x133.jpg
847 ms
75d0fc2f-d754-4242-86ca-7516a24020f9-200x133.jpg
843 ms
c4eeeadf-4dce-4b59-aa57-f91989275eb0-200x133.jpg
845 ms
cec249d2-61fd-4fdd-bdae-2d7e63f0dc44-200x133.jpg
846 ms
8836aa46-f158-437f-b539-9f1c4d26c2ed-200x133.jpg
844 ms
5e87df3c-c64f-40f5-bb05-a67ec6daa8fa-200x133.jpg
847 ms
footer-bg.png
847 ms
footer-li.png
842 ms
advert.gif
667 ms
sync_cookie_image_decide
140 ms
tea24.ru accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
tea24.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
tea24.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tea24.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 Tea24.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.
tea24.ru
Open Graph description is not detected on the main page of Tea24. 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: