4.2 sec in total
719 ms
3 sec
455 ms
Click here to check amazing Echoperm content for Russia. Otherwise, check out these important facts you probably never knew about echoperm.ru
Свежие новости Перми и Пермского края на ЭХО Москвы в Перми. Читайте у нас на сайте: все новости, интервью, мнения на актуальные темы.
Visit echoperm.ruWe analyzed Echoperm.ru page load time and found that the first response time was 719 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
echoperm.ru performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value5.9 s
14/100
25%
Value8.3 s
19/100
10%
Value5,880 ms
0/100
30%
Value0.014
100/100
15%
Value13.3 s
12/100
10%
719 ms
26 ms
261 ms
381 ms
267 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 62% of them (83 requests) were addressed to the original Echoperm.ru, 8% (11 requests) were made to V-kurse.ru and 5% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Echoperm.ru.
Page size can be reduced by 560.1 kB (24%)
2.3 MB
1.8 MB
In fact, the total size of Echoperm.ru main page is 2.3 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 120.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 29.2 kB, which is 20% 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 120.3 kB or 83% of the original size.
Potential reduce by 44.0 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. Echoperm images are well optimized though.
Potential reduce by 219.4 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 219.4 kB or 50% of the original size.
Potential reduce by 176.4 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. Echoperm.ru needs all CSS files to be minified and compressed as it can save up to 176.4 kB or 80% of the original size.
Number of requests can be reduced by 28 (24%)
119
91
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Echoperm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
echoperm.ru
719 ms
css
26 ms
jquery-ui.min.css
261 ms
style.css
381 ms
mobile.css
267 ms
jquery-1.8.3.min.js
394 ms
jquery-ui.min.datepicker.js
409 ms
main.js
419 ms
main.mobile.js
389 ms
magnific-popup.css
387 ms
openapi.js
424 ms
share.js
268 ms
i1.png
321 ms
3_0_E6E6E6FF_E6E6E6FF_0_pageviews
324 ms
logo
327 ms
i2.png
317 ms
i3.png
320 ms
vk.png
318 ms
tw.png
317 ms
face.png
320 ms
a2678959c0f5ea64697fa11d077f2dfc.BqtnjF.jpg
323 ms
%D0%91%D0%B5%D0%B7%D1%8B%D0%BC%D1%8F%D0%BD%D0%BD%D1%8B%D0%B9.6Y92Dg.dpeu6f.png
529 ms
DSC_5665.Ett5Tx.JPG
323 ms
bfa5adbc6a98589e77d0c5277d146c7e.FRgNah.JPG
325 ms
Dux.iDZFQ4.jpg
325 ms
%D0%9E%D0%BB%D0%B5%D1%81%D1%8F_%D0%93%D0%BE%D0%BB%D1%83%D0%B1%D0%B5%D0%B2%D0%B0_2.KL3RBC.jpg
325 ms
%D1%83%D1%80%D0%B0%D0%BB_%D1%84%D0%B4.cCEUyh.jpg
454 ms
%D1%81%D1%82%D1%80%D0%BE%D0%B8%D1%82%D0%B5%D0%BB%D1%8C.dz2Zww.JPG
454 ms
%D0%97%D0%BE%D1%82%D0%B8%D0%BD%D0%A2%D1%83%D0%BB%D0%B0.wBhF9f.jpg
453 ms
%D0%93%D0%B0%D0%B4%D0%B6%D0%B8%D0%B5%D0%B2.Re5tW6.jpg
454 ms
%D0%A1%D0%B0%D0%BF%D0%B8%D1%80%D0%BE.H6v5hj.qJpgYX.jpg
456 ms
%D0%BC%D1%83%D1%85%D0%B0.W2cGD9.jpg
514 ms
%D0%9A%D0%BE%D1%81%D1%8C%D0%B2%D0%B8%D0%BD%D1%86%D0%B5%D0%B2.KHCgyD.jpg
528 ms
%D0%B3%D0%B8%D0%BB%D1%8F%D0%B7%D0%BE%D0%B2%D0%B0.DNiPxD.jpg
527 ms
%D0%93%D0%B5%D1%80%D1%88%D0%B0%D0%BD%D0%BE%D0%BA.e6uvmH.jpg
527 ms
UK_banner_2.JPG
664 ms
215x215_3.VjPkkz.gif
1265 ms
busaev.EKce3f.jpg
656 ms
2-z3-a13d5034-3456-4fef-b6bc-d04f4e916f6e.HCQbHQ.jpg
657 ms
domik1.VXWpFk.jpg
653 ms
hrushi.zNagfx.jpg
776 ms
6f512b13261295df66363a432f9a8692.aX5ypB.jpg
787 ms
oS_UjU1dqkQ.eM8D6V.jpg
787 ms
aGatIf0ITJk.G7FAjG.jpg
789 ms
Cherd.meK8e8.jpg
803 ms
%D0%9E%D0%A1%D0%9E%D0%91%D0%9E%D0%95_%D0%9C%D0%9D%D0%95%D0%9D%D0%98%D0%95_%D0%B2%D1%8B%D1%81%D0%BA%D0%B0%D0%B7%D1%8B%D0%B2%D0%B0%D1%8E%D1%82_%D0%B3%D0%BE%D1%81%D1%82%D0%B8_%D0%AD%D1%85%D0%B0_%D0%9F%D0%B5%D1%80%D0%BC%D0%B8.CKYthj.jpg
902 ms
%D0%BF%D0%B5%D1%80%D0%BE.myteZ6.jpg
911 ms
%D0%9D%D0%B0%D1%83%D0%BA%D0%B0.Y2RvB3.jpg
914 ms
%D0%98%D0%BB%D1%8C%D0%B8%D0%BD.9Dgscx.jpg
914 ms
IMG_2048-1.jyXzV4.jpg
930 ms
all.js
311 ms
k3k702ZOKiLJc3WVjuplzGeP1y_Bkidl4ESyB_O2G_c.ttf
46 ms
MTP_ySUJH_bn48VBG8sNSmeP1y_Bkidl4ESyB_O2G_c.ttf
269 ms
K88pR3goAWT7BTt32Z01m6CWcynf_cDxXwCLxiixG1c.ttf
270 ms
DXI1ORHCpsQm3Vp6mXoaTWeP1y_Bkidl4ESyB_O2G_c.ttf
269 ms
501 ms
78788.js
334 ms
watch.js
296 ms
radioechoperm
591 ms
weather
86 ms
hit
279 ms
Echo_Ottepel-2016_w.html
1018 ms
IMG_1877-1.AkEFmW.jpg
731 ms
IMG_2034-1.dWU7Z9.jpg
746 ms
IMG_2024-1.5haz7n.jpg
744 ms
IMG_1980-1.m7QUG4.jpg
755 ms
~text
137 ms
IMG_1955-1.MHFGnV.jpg
892 ms
IMG_1967-1.w84Njw.iQKHSF.jpg
892 ms
IMG_1955-1.MHFGnV.jWVNY9.jpg
892 ms
%D0%94%D0%BE%D0%BC%D0%BE%D1%83%D0%BF%D1%80%D0%B0%D0%B2.XiX9De.jpg
891 ms
IMG_1822-2.XqQd6U.jpg
1008 ms
xjAJXh38I15wypJXxuGMBlwIJl2YiaXHM0xUx_ugXFg.ttf
62 ms
%D0%B4%D0%B5%D0%BD%D0%B8%D1%81%D0%B5%D0%BD%D0%BA%D0%BE.5YhCeR_(1).545YGB.jpg
1009 ms
watch.js
582 ms
%D0%91%D1%83%D0%BA%D0%B0%D1%82%D0%BE%D0%B2%D0%B0-2.Dgg52T.jpg
881 ms
IMG_2016-1.72jUQv.jpg
892 ms
%D0%91%D1%83%D0%BA%D0%B0%D1%82%D0%BE%D0%B2%D0%B0-2.WC27zJ.jpg
940 ms
IMG_1932.KZG4nS.JPG
962 ms
2877181.jpeg
732 ms
2842331.jpeg
510 ms
2848176.jpeg
284 ms
309 ms
%D0%91%D1%83%D0%BA%D0%B0%D1%82%D0%BE%D0%B2%D0%B0-2.Pw4SsB.jpg
944 ms
2321152.jpeg
741 ms
2809872.jpeg
986 ms
137 ms
xd_arbiter.php
127 ms
xd_arbiter.php
263 ms
IMG_1855-2.pznTPJ.jpg
937 ms
%D0%97%D0%B4%D0%BE%D1%80%D0%BE%D0%B2%D1%8B%D0%B9_%D0%BF%D0%BE%D0%B4%D1%85%D0%BE%D0%B4.nabVLQ.jpg
925 ms
%D0%9A%D1%80%D0%B0%D1%81%D0%BD%D1%8B%D0%B9_%D1%87%D0%B5%D0%BB%D0%BE%D0%B2%D0%B5%D1%87%D0%B5%D0%BA_%D0%B3%D0%BE%D1%82%D0%BE%D0%B2.zdP7SS.jpg
948 ms
%D0%9E%D0%B2%D0%B5%D1%80%D1%82%D0%B0%D0%B9%D0%BC.nFNYjL.jpg
990 ms
%D0%A0%D0%B0%D0%B9%D0%BE%D0%BD%D1%8B-%D0%BA%D0%B2%D0%B0%D1%80%D1%82%D0%B0%D0%BB%D1%8B.vRvnJq.jpg
1014 ms
css
17 ms
css
24 ms
template_16bff423a8a5ce63535df565747a87b4.css
132 ms
logo_s.png
236 ms
21dc3b876e3703be3d2cc6eee59ba4c4.jpg
646 ms
ce45a9017e30ba4f8b9f35577c339681.jpg
777 ms
30d38311eac2a5fc8a1c1713081b1296.jpg
628 ms
6387a8e43909ceb3ffe983739573be51.jpg
784 ms
70db0a3cd11b646a4b9b988df3fef746.JPG
787 ms
6609fd7d2d518db3116ef69dbc4c9290.jpg
1137 ms
9019295bd397cb6e02471a87a65bd727.jpeg
942 ms
65027a16d913d88c4f614e86656bf08e.jpg
1032 ms
hit
135 ms
redcross.png
908 ms
logo.png
923 ms
gradient-h.png
923 ms
mail.png
940 ms
rss.png
867 ms
430 ms
ban_line.png
880 ms
arrow-up.png
901 ms
n2.png
921 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
13 ms
k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf
13 ms
gradient-V30.png
906 ms
n1.png
834 ms
f1.png
857 ms
f2.png
879 ms
f3.png
900 ms
footer_logo.png
908 ms
advert.gif
113 ms
runtime.js
83 ms
f_logo.png
802 ms
dev.png
815 ms
ui-bg_flat_75_ffffff_40x100.png
836 ms
189 ms
1
117 ms
194 ms
ping
60 ms
echoperm.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.
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
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
echoperm.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
echoperm.ru SEO score
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 Echoperm.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 Echoperm.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.
echoperm.ru
Open Graph description is not detected on the main page of Echoperm. 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: