7.4 sec in total
780 ms
4.9 sec
1.8 sec
Click here to check amazing Teremok content for Russia. Otherwise, check out these important facts you probably never knew about teremok.ru
Мы придерживаемся современного улучшенного подхода к быстрому питанию, в котором отменный вкус сочетается с высокой скоростью обслуживания.
Visit teremok.ruWe analyzed Teremok.ru page load time and found that the first response time was 780 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
teremok.ru performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value27.7 s
0/100
25%
Value11.0 s
6/100
10%
Value2,210 ms
6/100
30%
Value0.095
91/100
15%
Value30.8 s
0/100
10%
780 ms
9 ms
717 ms
1112 ms
1058 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 22% of them (21 requests) were addressed to the original Teremok.ru, 18% (17 requests) were made to Teremok.ru.opt-css.1c-bitrix-cdn.ru and 18% (17 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Teremok.ru.
Page size can be reduced by 858.1 kB (11%)
7.8 MB
7.0 MB
In fact, the total size of Teremok.ru main page is 7.8 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. 70% of websites need less resources to load. Images take 6.9 MB which makes up the majority of the site volume.
Potential reduce by 53.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 53.3 kB or 75% of the original size.
Potential reduce by 172.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. Teremok images are well optimized though.
Potential reduce by 457.2 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 457.2 kB or 75% of the original size.
Potential reduce by 175.3 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. Teremok.ru needs all CSS files to be minified and compressed as it can save up to 175.3 kB or 85% of the original size.
Number of requests can be reduced by 42 (46%)
92
50
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teremok. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
teremok.ru
780 ms
jquery.min.js
9 ms
kernel_main0.css
717 ms
template_b60c000c2c43a0783cc0e64e30dd2dbc0.css
1112 ms
kernel_main.js
1058 ms
template_80f069c5f96f8009d9489dbef69503c7.js
901 ms
openapi.js
386 ms
ba.js
192 ms
analytics.js
91 ms
logo.png
640 ms
okrosh_2016_610x458.jpg
871 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
287 ms
%D0%94%D1%83%D0%B1%D1%80%D0%B0%D0%B2%D0%B0.png
1138 ms
blinchik_59_670x450_june.jpg
999 ms
obed_169_800x500%20RUSSKY_afimall.jpg
1183 ms
%D0%A4%D0%9B%D0%90%D0%9C%D0%9F.png
1048 ms
postnoe_2016_610x458.jpg
1051 ms
BIG%20968x504.jpg
1330 ms
%D0%9A%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B0-%D0%B0%D0%BD%D0%BE%D0%BD%D1%81.jpg
1599 ms
%D0%9B%D0%B0%D0%B4%D1%8C%D1%8F_02.03.jpg
1332 ms
%D0%97%D0%B2%D0%B5%D0%B7%D0%B4%D0%BD%D0%B0%D1%8F%20%D1%84%D1%83%D0%B4%D0%BA%D0%BE%D1%80%D1%82.jpg
1333 ms
%D0%97%D0%B5%D0%BB%D0%B5%D0%BD%D0%BE%D0%BF%D0%B0%D1%80%D0%BA.jpg
1596 ms
980528_1693175920920418_4428832325973259512_o.jpg
1326 ms
%D0%9A%D0%B8%D0%B4%D0%B1%D1%83%D1%80%D0%B3.jpg
1469 ms
KM%20(1).jpg
1482 ms
collage%20%D1%81%D0%B0%D0%B9%D1%82.jpg
1623 ms
NY_2016_500x337.jpg
1630 ms
%D0%9E%D0%B1%D0%BB%D0%B5%D0%BF%D0%B8%D1%85%D0%BE%D0%B2%D1%8B%D0%B9%20%D1%87%D0%B0%D0%B9_%D0%A4%D0%91%20%D0%B8%20%D1%81%D0%B0%D0%B9%D1%82.jpg
1746 ms
06.jpg
1769 ms
%D0%A8%D0%B5%D1%80%D0%B5%D0%BC%D0%B5%D1%82%D1%8C%D0%B5%D0%B2%D0%BE%20D.png
1711 ms
%D0%9A%D0%B0%D0%BB%D0%B8%D1%82%D0%B0_%D1%81%D0%B0%D0%B9%D1%82.png
1713 ms
msk.png
634 ms
okrosh_2016_850x358.jpg
1610 ms
banner_teremok_850kh358_2.jpg
1117 ms
postnoe_2016_850x358.jpg
1634 ms
kotlety_850x358.jpg
1451 ms
spasibo_sberbank.jpg
1451 ms
left_bg.png
571 ms
sdk.js
79 ms
top_menu.png
385 ms
moblie.png
365 ms
matrioshka.png
716 ms
calibri.woff
1506 ms
myriadpro-it.woff
707 ms
upload.gif
148 ms
widget_community.php
293 ms
trip_adv.png
483 ms
destination.jpg
656 ms
bottom_menu.png
657 ms
social_ico.png
667 ms
watch.js
91 ms
rs_navItem.png
718 ms
rs_navItem_active.png
723 ms
rsArrowLeft.png
721 ms
rsArrowRight.png
741 ms
select_arr.png
727 ms
collect
33 ms
bx_stat
214 ms
182 ms
xd_arbiter.php
37 ms
xd_arbiter.php
55 ms
loader_nav19239_3.js
133 ms
lite.css
139 ms
lite.js
510 ms
lang3_0.js
249 ms
widget_community.css
254 ms
xdm.js
257 ms
al_community.js
260 ms
connect.js
659 ms
-5xdRk7OhHw.jpg
376 ms
w_logo.png
129 ms
dk
164 ms
widget.a86e7c8a.css
645 ms
image
847 ms
ic_odkl_m.png
166 ms
add-or.png
325 ms
ic_odkl.png
480 ms
page.php
196 ms
G_MXJ0Fhta6.css
36 ms
y8ed17D0DwU.css
41 ms
_uvIFeNpD93.css
52 ms
SRSW8M763HA.js
61 ms
f60bAZQOUtx.js
79 ms
XokP-R2tSzH.js
78 ms
qknduWkmLL_.js
76 ms
EwhOebGmqZh.js
56 ms
UlhmM0m3TH8.js
57 ms
RFvRVBkbFtO.js
233 ms
12191812_888863144538254_487606868542608076_n.jpg
74 ms
wL6VQj7Ab77.png
66 ms
Wh-wXqXludh.png
67 ms
-N4O24bI2Vm.png
6 ms
R9GKCzjAnbk.js
7 ms
AWWjhOengNF.js
6 ms
YnSasnyq68i.js
9 ms
kQf_jlUv-kX.js
8 ms
teremok.ru 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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
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.
teremok.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teremok.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 Teremok.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.
teremok.ru
Open Graph description is not detected on the main page of Teremok. 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: