5.4 sec in total
621 ms
4.6 sec
129 ms
Click here to check amazing Echo H content for Russia. Otherwise, check out these important facts you probably never knew about echo-h.ru
В интернет-магазине Эхо Голливуда вы найдете богатый ассортимент женской обуви, купить которую можно и оптом, ведь мы являемся производителями продукции бренда Echo of Hollywood.
Visit echo-h.ruWe analyzed Echo-h.ru page load time and found that the first response time was 621 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
echo-h.ru performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value5.9 s
14/100
25%
Value10.0 s
9/100
10%
Value5,290 ms
0/100
30%
Value0.007
100/100
15%
Value26.4 s
0/100
10%
621 ms
70 ms
957 ms
15 ms
229 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 25% of them (26 requests) were addressed to the original Echo-h.ru, 47% (48 requests) were made to St6-21.vk.com and 6% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 492.3 kB (15%)
3.2 MB
2.7 MB
In fact, the total size of Echo-h.ru main page is 3.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. 60% of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 62.9 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 62.9 kB or 77% of the original size.
Potential reduce by 13.1 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. Echo H images are well optimized though.
Potential reduce by 338.6 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 338.6 kB or 15% of the original size.
Potential reduce by 77.6 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. Echo-h.ru needs all CSS files to be minified and compressed as it can save up to 77.6 kB or 14% of the original size.
Number of requests can be reduced by 78 (80%)
97
19
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Echo H. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
echo-h.ru
621 ms
js
70 ms
tag.js
957 ms
jquery.min.js
15 ms
jquery.fancybox-1.3.4.css
229 ms
style.css
234 ms
jquery.fancybox-1.3.4.pack.js
237 ms
jquery.easing-1.3.pack.js
238 ms
jquery.mousewheel-3.0.4.pack.js
238 ms
jquery.accordion.js
241 ms
main.js
350 ms
main.css
385 ms
WebResource.axd
387 ms
ScriptResource.axd
623 ms
ScriptResource.axd
505 ms
jsdebug
389 ms
openapi.js
370 ms
share.js
377 ms
watch.js
0 ms
top100.jcn
395 ms
ga.js
5 ms
__utm.gif
11 ms
0105_0008_m%D0%9E-0040.jpg
238 ms
0493_m125-3gold.jpg
126 ms
0782_m50-06.jpg
285 ms
top100.jcn
653 ms
header_top.jpg
234 ms
bar-bg.png
121 ms
header_menu.jpg
120 ms
spacer.gif
122 ms
search.png
122 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
238 ms
red_star.gif
118 ms
grey_star.gif
119 ms
upload.gif
120 ms
widget_community.php
317 ms
right_array.gif
119 ms
sdk.js
22 ms
footer.jpg
120 ms
arrow_up.png
119 ms
hit
277 ms
b-share.png
261 ms
b-share-icon.png
390 ms
b-share-popup_down__tail.png
521 ms
advert.gif
594 ms
sdk.js
7 ms
cnt.js
34 ms
hit
540 ms
loader_nav21187537420_3.js
276 ms
fonts_cnt.c7a76efe.css
895 ms
lite.c9bfd4eb.css
681 ms
lang3_2.js
593 ms
polyfills.c3a1b892.js
629 ms
vkui.acd59e29.css
713 ms
xdm.js
538 ms
ui_common.963f8bc1.css
628 ms
vkcom-kit.f0442830.css
808 ms
vkcom-kit.99b57119.js
1010 ms
react.6a15a5cc.js
851 ms
vkcom-kit-icons.1e383998.js
890 ms
vkui.db495a8c.js
999 ms
state-management.c2ab675e.js
939 ms
architecture-mobx.b95ff7c7.js
955 ms
audioplayer-lib.93b52d88.css
977 ms
audioplayer-lib.f4c83799.js
1004 ms
bootstrap.d45896fc.js
1231 ms
core_spa.860f105b.js
1070 ms
common.fa0817a7.js
1204 ms
7f463667.b3f6bf8c.js
1092 ms
ui_common.43d06ff5.css
1089 ms
ui_common.b769de43.js
1103 ms
audioplayer.43d06ff5.css
1155 ms
audioplayer.0ed6dee4.js
1174 ms
widget_community.4978d481.css
1179 ms
6056d482.d934d35f.js
1194 ms
5233f55c.e7bdbbce.js
1247 ms
23cad2f0.2f3019d3.js
1262 ms
82fab9f9.2343c849.js
1270 ms
likes.43d06ff5.css
1282 ms
likes.5e0eb9a5.js
1290 ms
vkcom-kit.6ec86c95.css
1325 ms
vkcom-kit.04385c47.js
1363 ms
vkcom-kit-icons.2356ab10.js
1351 ms
architecture-mobx.cb627586.js
1369 ms
audioplayer-lib.85b39ca5.css
1369 ms
audioplayer-lib.514083c8.js
1391 ms
lite.f8081c5724ea3c8f7503758696b1108c.js
330 ms
sync_cookie_image_decide
151 ms
community.640eed5d.css
879 ms
base.3e47d375.css
816 ms
react.84cfd9aa.js
858 ms
1
150 ms
state-management.60b70a9c.js
771 ms
vkui.defca93c.js
794 ms
c3d11fba.afd34106.js
680 ms
0fc69f32.50a5506a.js
665 ms
79661701.f609cbc1.js
643 ms
57703e15.7fd3085f.js
629 ms
edb6ffde.e78a3f4a.js
859 ms
community.3c4e00bd.js
619 ms
GtdOpLmobKF9Imz58fU7c17Me7ubLYF07X6e2f32X6TwwLHGu2x1CTU__ZX4uAh_h5yRTf6OIxa0BokvHZWFylzV.jpg
490 ms
2R9yQTfeilM.jpg
890 ms
upload.gif
88 ms
echo-h.ru accessibility score
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
echo-h.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
echo-h.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
![]()
RU
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Echo-h.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 Echo-h.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.
echo-h.ru
Open Graph description is not detected on the main page of Echo H. 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: