3.9 sec in total
468 ms
3.1 sec
326 ms
Welcome to teatam.ru homepage info - get ready to check Teatam best content for Russia right away, or after learning these important things about teatam.ru
Пуэр и другие чайные радости...
Visit teatam.ruWe analyzed Teatam.ru page load time and found that the first response time was 468 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
teatam.ru performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.3 s
42/100
25%
Value8.5 s
18/100
10%
Value1,880 ms
9/100
30%
Value0.018
100/100
15%
Value17.4 s
4/100
10%
468 ms
320 ms
629 ms
394 ms
204 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 20% of them (13 requests) were addressed to the original Teatam.ru, 20% (13 requests) were made to Vk.com and 15% (10 requests) were made to I.teatam.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source I.teatam.ru.
Page size can be reduced by 1.4 MB (67%)
2.2 MB
710.8 kB
In fact, the total size of Teatam.ru main page is 2.2 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. 40% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 127.7 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 127.7 kB or 85% of the original size.
Potential reduce by 13.6 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. Teatam images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 73% of the original size.
Potential reduce by 31.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. Teatam.ru needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 80% of the original size.
Number of requests can be reduced by 28 (46%)
61
33
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teatam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
teatam.ru
468 ms
common_5d56.css
320 ms
35.png
629 ms
openapi.js
394 ms
watch.js
204 ms
LqD64iH27Q0.jpg
954 ms
%D1%82%D0%B3%D1%88%D0%BA%D0%B0%D0%B2%D1%81.jpg
496 ms
%D1%84%D1%85%D0%B4%D1%86.jpg
1436 ms
%D0%BF%D1%83%D1%87%D0%B6%D0%B8%D0%B2%D1%8D%D0%B9.jpg
406 ms
%D0%B4%D1%85%D0%BF%201000.jpg
508 ms
803.jpg
492 ms
Gaba_Alishan_vc-500x500.jpg
580 ms
css
36 ms
require.js
160 ms
includer.min.js
737 ms
watch.js
448 ms
css
19 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
229 ms
black-opacity.png
85 ms
%D1%82%D0%B5%D0%BB.png
237 ms
cart-button.png
89 ms
%D0%B0%D0%BA%D1%86.jpg
860 ms
upload.gif
125 ms
widget_community.php
278 ms
cnt.js
536 ms
advert.gif
283 ms
loader_nav19188_3.js
266 ms
lite.css
267 ms
lite.js
402 ms
lang3_0.js
276 ms
widget_community.css
277 ms
xdm.js
275 ms
al_community.js
277 ms
uptolike.js
1321 ms
top.png
252 ms
formhandler.json.js
141 ms
jsonrpc
344 ms
jsonrpc
269 ms
jsonrpc
339 ms
1
88 ms
2268176.js
157 ms
transition.js
91 ms
27160079
88 ms
zoom.js
92 ms
pkoDJCTAmYQ.jpg
387 ms
ah9XYV_PLS4.jpg
373 ms
vw1umMheOn4.jpg
368 ms
cGr3VgEMoWk.jpg
376 ms
ilbbg-wp3n0.jpg
358 ms
NycPaIg8WwM.jpg
373 ms
74qDxoXiQZc.jpg
367 ms
1SjfWXtq6ZA.jpg
368 ms
fDljtofzH3Q.jpg
395 ms
UzZtjuyXduM.jpg
369 ms
53TnuE9cnug.jpg
371 ms
6SNsDHaFS34.jpg
376 ms
camera_50.png
156 ms
deactivated_50.png
155 ms
w_logo.png
150 ms
cnt
138 ms
f.gif
126 ms
version.js
156 ms
pixel
15 ms
pixel
14 ms
collect
219 ms
widgetsModule.js
462 ms
teatam.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
Image elements do not have [alt] attributes
Links do not have a discernible name
teatam.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
teatam.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 Teatam.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 Teatam.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.
teatam.ru
Open Graph description is not detected on the main page of Teatam. 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: