24.8 sec in total
486 ms
23.7 sec
612 ms
Welcome to tea-coffee.info homepage info - get ready to check Tea Coffee best content for Russia right away, or after learning these important things about tea-coffee.info
Купить оптом качественный чай и кофе лучших сортов со всего мира от производителя Vintage по всей России, ".date_diff(new DateTime(), new DateTime('2004-08-25 00:00:01'))->y." лет на рынке, 130 магази...
Visit tea-coffee.infoWe analyzed Tea-coffee.info page load time and found that the first response time was 486 ms and then it took 24.3 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
tea-coffee.info performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value9.3 s
1/100
25%
Value8.2 s
20/100
10%
Value17,240 ms
0/100
30%
Value0.001
100/100
15%
Value24.8 s
0/100
10%
486 ms
1345 ms
1480 ms
2533 ms
1866 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 79% of them (57 requests) were addressed to the original Tea-coffee.info, 4% (3 requests) were made to Vs31.tawk.to and 3% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (19.6 sec) belongs to the original domain Tea-coffee.info.
Page size can be reduced by 994.0 kB (19%)
5.1 MB
4.1 MB
In fact, the total size of Tea-coffee.info main page is 5.1 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.0 MB which makes up the majority of the site volume.
Potential reduce by 57.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 9.1 kB, which is 13% 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 57.3 kB or 83% of the original size.
Potential reduce by 121.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. Tea Coffee images are well optimized though.
Potential reduce by 673.5 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 673.5 kB or 74% of the original size.
Potential reduce by 141.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. Tea-coffee.info needs all CSS files to be minified and compressed as it can save up to 141.8 kB or 87% of the original size.
Number of requests can be reduced by 13 (22%)
58
45
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tea Coffee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
tea-coffee.info
486 ms
kernel_main0.css
1345 ms
popup.css
1480 ms
template_4518db2b50c71f28c3a0bbb4bf8d66ba0.css
2533 ms
kernel_main.js
1866 ms
template_af02af903606a0d7808785e938e84c1b.js
1264 ms
html5.js
412 ms
respond.js
607 ms
mobile_sect_1.png
775 ms
mobile_sect_2.png
939 ms
mobile_sect_3.png
1127 ms
mobile_sect_4.png
1321 ms
mobile_sect_5.png
1429 ms
market.jpg
1638 ms
ea48db913918399b497c758fba5f5993.png
1642 ms
%D0%A1%D0%B5%D0%B2%D0%B5%D1%80%D0%BD%D0%BE%D0%B5-%D0%A1%D0%B8%D1%8F%D0%BD%D0%B8%D0%B5.png
1600 ms
%D0%A1%D0%BE%D0%BB%D0%BD%D0%B5%D1%87%D0%BD%D0%B0%D1%8F_%D1%85%D1%80%D0%B8%D0%B7%D0%B0%D0%BD%D1%82%D0%B5%D0%BC%D0%B01.png
2072 ms
%D0%9A%D1%83%D0%B4%D0%B8%D0%BD-%D0%B2%D0%B5%D1%80%D0%B5%D1%82%D0%B5%D0%BD%D0%BE1.png
1766 ms
%D0%93%D0%B0%D0%BD%D0%BF%D0%B0%D1%83%D0%B4%D0%B5%D1%80_%D0%BF%D1%80%D0%B5%D0%BC%D0%B8%D1%83%D0%BC.png
1967 ms
%D0%9A%D0%B8%D1%82%D0%B0%D0%B9%D1%81%D0%BA%D0%B8%D0%B9_%D0%9F%D0%BE%D1%80%D0%BE%D1%851.png
1849 ms
%D0%97%D0%B5%D0%BB%D0%B5%D0%BD%D0%B0%D1%8F_%D1%81%D0%BF%D0%B8%D1%80%D0%B0%D0%BB%D1%8C1.png
1935 ms
%D0%A3%D0%BB%D1%83%D0%BD_%D0%A1%D0%BB%D0%B8%D0%B2%D0%BE%D1%87%D0%BD%D1%8B%D0%B91.png
2034 ms
%D0%A3%D0%BB%D1%83%D0%BD_%D0%A2%D0%B5_%D0%93%D1%83%D0%B0%D0%BD%D1%8C_%D0%98%D0%BD%D1%8C-5001.png
2022 ms
%D0%A3%D0%BB%D1%83%D0%BD_%D0%9D%D1%8F%D0%B9_%D0%A1%D0%B0%D0%BD.png
2102 ms
%D0%91%D0%BE%D0%BB%D1%8C%D1%88%D0%BE%D0%B9_%D0%BA%D1%80%D0%B0%D1%81%D0%BD%D1%8B%D0%B9_%D1%85%D0%B0%D0%BB%D0%B0%D1%82.png
2154 ms
%D0%A2%D0%B5_%D0%93%D1%83%D0%B0%D0%BD%D1%8C_%D0%98%D0%BD%D1%8C_%D0%B6%D0%B5%D0%BD%D1%8C%D1%88%D0%B5%D0%BD%D1%8C.png
2208 ms
%D0%9D%D0%B0%D0%B9_%D0%A1%D1%8F%D0%BD_%D0%A2%D0%B5_%D0%93%D1%83%D0%B0%D0%BD%D1%8C_%D0%98%D0%BD%D1%8C.png
2239 ms
%D0%A2%D0%B5_%D0%93%D1%83%D0%B0%D0%BD%D1%8C_%D0%98%D0%BD%D1%8C_%D0%BC%D0%BE%D0%BB%D0%BE%D1%87%D0%BD%D1%8B%D0%B9.png
2283 ms
%D0%A2%D0%B5_%D0%93%D1%83%D0%B0%D0%BD%D1%8C_%D0%98%D0%BD%D1%8C_300.png
2284 ms
%D0%A3%D0%BB%D1%83%D0%BD-%D0%94%D0%B0-%D0%A5%D1%83%D0%BD-%D0%9F%D0%B0%D0%BE.png
2449 ms
%D0%9D%D0%B8%D0%BE%D0%BC%D0%B1%D0%B8_%D0%A2%D0%B0%D0%BD%D0%B7%D0%B0%D0%BD%D0%B8%D1%8F.png
2371 ms
%D0%A6%D0%B5%D0%B9%D0%BB%D0%BE%D0%BD%D1%81%D0%BA%D0%B8%D0%B9_%D0%BA%D1%80%D1%83%D0%BF%D0%BD%D0%BE%D0%BB%D0%B8%D1%81%D1%82%D0%BE%D0%B2%D0%BE%D0%B9.png
2421 ms
%D0%97%D0%BE%D0%BB%D0%BE%D1%82%D0%B0%D1%8F_%D0%BE%D0%B1%D0%B5%D0%B7%D1%8C%D1%8F%D0%BD%D0%B0.png
2922 ms
%D0%AE%D0%BD%D0%BD%D0%B0%D0%BD%D1%8C_0211.png
2421 ms
3-01.png
2891 ms
3-01.png
3195 ms
header.png
365 ms
sprite.png
647 ms
main_icon_1.png
364 ms
main_icon_2.png
395 ms
main_icon_3.png
395 ms
main_icon_4.png
411 ms
main_icon_5.png
536 ms
dab7ff754aad8a50d2bfd13a0461c540.png
4097 ms
18307156dfddb5af4d73b9b64b3efb1d.png
3356 ms
4c39e3bf85ee22a2d88aea394a350c49.png
2882 ms
9ce250a0ae378e50d8a2d26f00aafd37.png
19639 ms
ae729c6892b7c41c7d9ed59f590488f1.png
13266 ms
44bf2e1e29debdb49e8905b4f21f1742.png
3284 ms
hits.png
3227 ms
form.jpg
3480 ms
pat.png
3930 ms
footer.jpg
3540 ms
ba.js
250 ms
gtm.js
216 ms
watch.js
213 ms
default
548 ms
lora-regular-webfont.woff
3448 ms
lora-bold-webfont.woff
3333 ms
lora-italic-webfont.woff
3500 ms
lora-bolditalic-webfont.woff
3727 ms
analytics.js
69 ms
sip.js
735 ms
bx_stat
269 ms
collect
50 ms
icons.png
268 ms
1460132293523
1591 ms
338 ms
341 ms
1031 ms
v3
127 ms
set.cgi
1060 ms
tea-coffee.info accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
tea-coffee.info 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
tea-coffee.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tea-coffee.info 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 Tea-coffee.info 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.
tea-coffee.info
Open Graph description is not detected on the main page of Tea Coffee. 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: