5.5 sec in total
523 ms
4.4 sec
598 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 523 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prm.ru performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value25.9 s
0/100
25%
Value15.4 s
0/100
10%
Value10,530 ms
0/100
30%
Value0.027
100/100
15%
Value31.8 s
0/100
10%
523 ms
1112 ms
1075 ms
68 ms
788 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Prm.ru, 33% (18 requests) were made to Cdn.iportal.ru and 24% (13 requests) were made to Static.ngs.ru. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Cdn.iportal.ru.
Page size can be reduced by 705.6 kB (5%)
15.4 MB
14.7 MB
In fact, the total size of Prm.ru main page is 15.4 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. 45% of websites need less resources to load. Images take 14.5 MB which makes up the majority of the site volume.
Potential reduce by 579.8 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 579.8 kB or 86% of the original size.
Potential reduce by 0 B
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 125.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 125.8 kB or 45% of the original size.
Number of requests can be reduced by 21 (44%)
48
27
The browser has sent 48 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 22 to 1 for JavaScripts and as a result speed up the page load time.
prm.ru
523 ms
59.ru
1112 ms
context.js
1075 ms
js
68 ms
tag.js
788 ms
ad-category-recognition.js
1374 ms
AdRiverFPS.js
924 ms
header-bidding.js
1241 ms
hsm-creative-manager.471.js
986 ms
asdk.js
861 ms
weboctx.min.js
18 ms
146x32.svg
995 ms
1a393ff3b75d17a773416176719b60ae03013685_720_720_c.jpg
1249 ms
mostly-cloudy.dfc39c5.svg
828 ms
acee051395ad511b912275c373a597470846cdbf_3000_2000_c.jpg
1466 ms
dd77a1ad92e132b75161d9c29dd2c8d90b3e38e6_1620_1080_c.jpg
1700 ms
e3a83767458d355cd9f547f46ee3db310d73203b_1000_667_c.jpg
1118 ms
fb34597dc2b20053b80987eb962003bd0495f85b_1078_719_c.jpg
1410 ms
254dfcdc5e9c45d264080937a535fba60e5cae5a_1200_800_c.jpg
1196 ms
743da98e7fc9b7df1bf21d61b2d4e1660ef5eb7f_1680_1120_c.jpg
1411 ms
949bcef19242e8cb98ffc53c5f4d2e950d7e5fe8_3000_2000_c.JPG
1635 ms
bc696d0cb189698d6240a0badfe7ca260be0542b_1920_1280_c.jpg
3088 ms
d42ffdbc043886a1064c845f29cf07810500428f_3000_2000_c.jpeg
1809 ms
a44b608ff9f2ef4baca28981877916770171fa4e_1257_838_c.jpg
1550 ms
26a2ee6a78aefba0468972ff88de3a6c036cc72d_1920_1280_c.jpg
1607 ms
71a88c876cdf895b9d5de363768838d90cd503d3_1280_853_c.jpg
1717 ms
f309835f3c1ad22d6f20e418e46f17260dc3a3d4_1191_794_c.jpg
1716 ms
a7df1e0a59adb43bfcbae849b45efa0600da4fe6_3000_2000_c.jpg
1630 ms
0eca1987c44b7cd70d55a6e365d4d14905ba5210_1500_1000_c.jpg
1675 ms
0f96c06eaf5c1e65c1a99ca2c14e38240226adad_2560_1707_c.jpg
1694 ms
7bddd20938ed59b09d564b0f8d7f2f0101fc9dcd_295_197_c.jpg
1664 ms
runtimechunk~app.848467d.js
503 ms
30400.cf1346b.js
547 ms
new-app.6a2458d.js
817 ms
79877.9b47768.js
547 ms
35820.8aabea7.js
547 ms
new-home-page.e6061c8.js
796 ms
app.e253233.js
638 ms
vq_starter.js
717 ms
OneSignalSDK.js
39 ms
roxot-manager.js
778 ms
hb.js
214 ms
sync-urls.js
1134 ms
sync-loader.js
780 ms
vq_init.js
273 ms
roboto-v30-latin_cyrillic-regular.woff
141 ms
roboto-v30-latin_cyrillic-700.woff
895 ms
ui-common.b29e597eefc8bb61eb784dd93999db51.svg
44 ms
roboto-slab-v24-latin_cyrillic-regular.woff
151 ms
roboto-slab-v24-latin_cyrillic-700.woff
151 ms
advert.gif
465 ms
vq_init.css
127 ms
1
165 ms
1
145 ms
1
144 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
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: