19.9 sec in total
315 ms
18.7 sec
841 ms
Visit tea4me.ru now to see the best up-to-date Tea 4 Me content for Russia and also check out these interesting facts you probably never knew about tea4me.ru
Здоровье и красота с Just без лекарств! Чистые эфирные масла и косметика на их основе. Доставка в СДЭК и Почтой от 0 руб.
Visit tea4me.ruWe analyzed Tea4me.ru page load time and found that the first response time was 315 ms and then it took 19.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
tea4me.ru performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value11.2 s
0/100
25%
Value21.6 s
0/100
10%
Value35,540 ms
0/100
30%
Value0.375
28/100
15%
Value52.3 s
0/100
10%
315 ms
328 ms
156 ms
356 ms
63 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 20% of them (12 requests) were addressed to the original Tea4me.ru, 38% (23 requests) were made to Assets3.insales.ru and 8% (5 requests) were made to Static-eu.insales.ru. The less responsive or slowest element that took the longest time to load (17.1 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 356.3 kB (7%)
5.0 MB
4.6 MB
In fact, the total size of Tea4me.ru main page is 5.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. 50% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 37.2 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.5 kB, which is 22% 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 37.2 kB or 78% of the original size.
Potential reduce by 196.5 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. Tea 4 Me images are well optimized though.
Potential reduce by 61.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 61.8 kB or 67% of the original size.
Potential reduce by 60.8 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. Tea4me.ru needs all CSS files to be minified and compressed as it can save up to 60.8 kB or 82% of the original size.
Number of requests can be reduced by 24 (43%)
56
32
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tea 4 Me. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tea4me.ru
315 ms
www.tea4me.ru
328 ms
insales_counter.js
156 ms
style.css
356 ms
font-awesome.css
63 ms
jquery.rating.css
355 ms
jquery.min.js
8 ms
shadowbox-jquery.js
135 ms
modernize.js
347 ms
shadowbox.js
153 ms
jquery.cookie.js
135 ms
common_ru.js
153 ms
jquery.MetaData.js
352 ms
jquery.rating.pack.js
385 ms
jquery.cycle.all.js
389 ms
common.js
471 ms
OptionSelectors.js
484 ms
widget.js
523 ms
referer_code.js
274 ms
counter.insales.ru
278 ms
skin.css
134 ms
skin.js
139 ms
shadowbox-ru.js
139 ms
shadowbox-img.js
137 ms
loaded_logo.png
183 ms
33.jpg
1114 ms
murmansk_2.png
6516 ms
1-perevozki-po-odesse-i-ukraine-sbornyih-gruzov.jpg
569 ms
4972.5fa5a841a0e1e1ec3b1b46e28069934b.jpg
521 ms
m8QmCPI9Lkw.jpg
811 ms
2.jpg
792 ms
1.jpg
1049 ms
1spraydliavekjust_2.jpg
917 ms
medium_BlanX_Extra_White_30.jpg
410 ms
cHhRLW2p9ew.jpg
1197 ms
YgrFwycaLm0.jpg
1521 ms
AkhqAEl7-fI.jpg
1534 ms
watch.js
202 ms
weed.png
1322 ms
fon.jpg
1147 ms
fon-just-left.png
905 ms
fon-just-right.png
1027 ms
blur.png
147 ms
search.png
150 ms
button_bg.png
228 ms
cart_icon.png
258 ms
loaded_main_image_1.jpg
834 ms
loaded_main_image_2.jpg
934 ms
loaded_main_image_3.jpg
1099 ms
loaded_main_image_4.jpg
1200 ms
loaded_main_image_5.jpg
1256 ms
loaded_main_image_6.jpg
1266 ms
loaded_main_image_7.jpg
1376 ms
watch.js
16965 ms
OsIxomhDk2
171 ms
fontawesome-webfont.woff
37 ms
watch.js
17121 ms
widget_ru_RU.js
186 ms
advert.gif
298 ms
1
85 ms
tea4me.ru accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tea4me.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tea4me.ru SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tea4me.ru 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 Tea4me.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.
tea4me.ru
Open Graph description is not detected on the main page of Tea 4 Me. 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: