10.3 sec in total
722 ms
9.4 sec
174 ms
Click here to check amazing Prm content for Russia. Otherwise, check out these important facts you probably never knew about prm.ru
Последние свежие новости Перми и Пермского края за сегодня - онлайн на сайте 59.ру
Visit prm.ruWe analyzed Prm.ru page load time and found that the first response time was 722 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
prm.ru performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value23.5 s
0/100
25%
Value14.3 s
1/100
10%
Value3,800 ms
1/100
30%
Value0.004
100/100
15%
Value22.9 s
1/100
10%
722 ms
390 ms
1204 ms
598 ms
392 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 16% of them (10 requests) were addressed to the original Prm.ru, 27% (17 requests) were made to Static.ngs.ru and 10% (6 requests) were made to Do.prm.ru. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Do.prm.ru.
Page size can be reduced by 332.9 kB (29%)
1.1 MB
798.5 kB
In fact, the total size of Prm.ru main page is 1.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. 35% of websites need less resources to load. Images take 737.6 kB which makes up the majority of the site volume.
Potential reduce by 57.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 57.9 kB or 82% of the original size.
Potential reduce by 59.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. Prm images are well optimized though.
Potential reduce by 143.7 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 143.7 kB or 61% of the original size.
Potential reduce by 71.9 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. Prm.ru needs all CSS files to be minified and compressed as it can save up to 71.9 kB or 82% of the original size.
Number of requests can be reduced by 19 (35%)
55
36
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
prm.ru
722 ms
project_prm.css
390 ms
jquery-1.10.2.min.js
1204 ms
dohcohT2.js
598 ms
oauth.js
392 ms
624 ms
rnPageMain.js
209 ms
boom.min.js
202 ms
logo_perm.png
390 ms
cloudy_snow_day.png
676 ms
86be9ac6843a48174adfb60e3236b41e.png
1527 ms
dd51a99144190813b1aa24bab2c1086a_234_174_c.jpg
894 ms
3fd2b9aaf07987bf6ae4e9f1bd0b6f8b_234_174_c.jpg
2060 ms
8ce3e8326a98343d5b7814ecad47f385_1456747743_156_116_c.jpg
3919 ms
logo;prm_ru
255 ms
6a992769916d3e649f88cac3e5e4ff49_1456732096_156_116_c.jpg
4122 ms
f9f9062782cb74bf1129c2b38911fa75_1456300124_156_116_c.jpg
4322 ms
1f83fe6657aeab121428e68f751d7adc_1447753682_156_116_c.jpg
4525 ms
_156_116_c.
4877 ms
05520ee355c783fce4b0070a43ac6230_1454935021_156_116_c.jpg
5079 ms
a886f43e4eda5aa37a6e1b4684f6a983_234_174_c.jpg
884 ms
cc765a82c5706df30d91c94ed15862a6_156_116_c.jpg
651 ms
a3df88c72fd3a60176e367f19aaac6c4_156_116_c.jpg
658 ms
cd198f3006ef53c41060e5bf433ecbf9_156_116_c.jpg
694 ms
6d8b854bfbad317423b4c7fae66420cc_156_116_c.jpg
1142 ms
49f12bc29ee44305b3daf3cd2d10d70d_156_116_c.jpg
1088 ms
f5540b8a6110d62fa56268e0f0b54175_156_116_c.jpg
1124 ms
35a61138d5083a537baef7b82fcca3ce_156_116_c.jpg
1465 ms
970897b8cb6297145ff00437372bc581_156_116_c.jpg
1307 ms
696b3d5e282a31d90aba8afa996719df_156_116_c.jpg
1515 ms
bcbcb71162e5a7a517b8ebd6c3342642_156_116_c.jpg
1545 ms
e023137f785185bb54d0960d9690866e_156_116_c.jpg
1569 ms
e392adcb581183a709ca61728ab4f831_156_116_c.jpg
1702 ms
6fcca39a4c772a7770ee1c3c6221af76_156_116_c.jpg
1755 ms
fc3c92a7a2a677890d2ca19c55b79fc1_156_116_c.jpg
2097 ms
d654a7edce394641dba96c4a3af0e8dd_156_116_c.jpg
1940 ms
60f1e3e32931c11ee57b4455823ca558_234_174_c.jpeg
2142 ms
900609c9716d904fee4e6e37f1693845_156_116_c.jpg
2252 ms
c0025925d21666217eefaef1a4ae5fea_156_116_c.jpg
2343 ms
21f13c68957839123c9cc70d0ee66ca6_156_116_c.jpg
2461 ms
f8af3e9fed62ca024108e9b69cc00ef2_156_116_c.jpg
2545 ms
cloudy_snow_night.png
871 ms
watch.js
298 ms
dc.js
37 ms
tcounter.js
262 ms
342
255 ms
hit;prm_ru
262 ms
rta.js
29 ms
sprite_prm.png
805 ms
PTSans-Caption.woff
1960 ms
PTSans-CaptionBold.woff
1788 ms
PTSans-Regular.woff
2168 ms
PTSans-Bold.woff
2042 ms
tpx
600 ms
shadow_desc.png
538 ms
inpage_linkid.js
67 ms
__utm.gif
12 ms
watch.js
430 ms
54681192
256 ms
advert.gif
84 ms
1
85 ms
23857549
85 ms
200 ms
prm.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
<frame> or <iframe> elements do not have a title
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.
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.
prm.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
prm.ru 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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prm.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Prm.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.
prm.ru
Open Graph description is not detected on the main page of Prm. 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: