6.9 sec in total
2 sec
4.3 sec
607 ms
Click here to check amazing In Tea content for Russia. Otherwise, check out these important facts you probably never knew about intea.ru
Интернет магазин чая InTea.ru осуществляет продажу разных сортов китайского чая. Купить зеленый чай, пуэр, улун с доставкой по Москве и России.
Visit intea.ruWe analyzed Intea.ru page load time and found that the first response time was 2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
intea.ru performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value7.0 s
6/100
25%
Value6.7 s
36/100
10%
Value2,500 ms
4/100
30%
Value0
100/100
15%
Value7.4 s
48/100
10%
2001 ms
301 ms
654 ms
298 ms
302 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 75% of them (40 requests) were addressed to the original Intea.ru, 6% (3 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Intea.ru.
Page size can be reduced by 254.4 kB (35%)
723.6 kB
469.2 kB
In fact, the total size of Intea.ru main page is 723.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 337.1 kB which makes up the majority of the site volume.
Potential reduce by 92.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. 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 92.3 kB or 78% of the original size.
Potential reduce by 3.2 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. In Tea images are well optimized though.
Potential reduce by 135.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 135.8 kB or 57% of the original size.
Potential reduce by 23.0 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. Intea.ru needs all CSS files to be minified and compressed as it can save up to 23.0 kB or 76% of the original size.
Number of requests can be reduced by 25 (51%)
49
24
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Tea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.intea.ru
2001 ms
template_css.css
301 ms
highslide-full.min.js
654 ms
highslide.css
298 ms
default.css
302 ms
mod_cd_callback.css
302 ms
mod_cd_login.css
308 ms
mediaobject-150.js
316 ms
mootools-yui-compressed.js
167 ms
caption.js
442 ms
fetchscript.php
447 ms
share.js
180 ms
tabs_slides_comp.js
447 ms
mootools-core-compat.js
104 ms
jquery.min.js
44 ms
jquery-ui.min.js
92 ms
head.jpg
594 ms
sprite_2.png
427 ms
02613.jpg
233 ms
sale_page.jpg
234 ms
sale_page_hover.jpg
229 ms
755_tmb.jpg
235 ms
273_tmb.jpg
350 ms
583_tmb.jpg
351 ms
_________________4d67c16e61cb4.jpg
353 ms
_________________4d67c1020cd09.jpg
351 ms
_________________4daeb0b8bb15d.jpg
445 ms
_________________4ca8cdf978106.jpg
455 ms
_________________4a5c3af410863.jpg
427 ms
_________________4ba65cda7bc92.jpg
457 ms
IlCafe_tmb.png
503 ms
sprite_3.png
567 ms
bottom.jpg
1032 ms
t2.jpg
608 ms
l2.jpg
615 ms
bl2.jpg
619 ms
br2.jpg
724 ms
tl2.jpg
732 ms
tr2.jpg
749 ms
b3.jpg
712 ms
dot.jpg
712 ms
bag.jpg
829 ms
b3.png
835 ms
ga.js
50 ms
watch.js
38 ms
analytics.js
304 ms
__utm.gif
22 ms
collect
181 ms
analytics.js
361 ms
rounded-white.png
170 ms
zoomout.cur
157 ms
sprite_6.png
159 ms
sprite_6_2.jpg
160 ms
intea.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
intea.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
intea.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
Tap targets are not sized appropriately
RU
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intea.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Intea.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.
intea.ru
Open Graph description is not detected on the main page of In Tea. 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: