4.6 sec in total
503 ms
3.6 sec
487 ms
Visit 59.ru now to see the best up-to-date 59 content for Russia and also check out these interesting facts you probably never knew about 59.ru
Последние свежие новости Перми и Пермского края за сегодня. Все новости региона на сайте 59.ру
Visit 59.ruWe analyzed 59.ru page load time and found that the first response time was 503 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
59.ru performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value20.9 s
0/100
25%
Value12.5 s
3/100
10%
Value3,860 ms
1/100
30%
Value0.027
100/100
15%
Value26.4 s
0/100
10%
503 ms
919 ms
1041 ms
57 ms
911 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original 59.ru, 32% (18 requests) were made to Cdn.iportal.ru and 23% (13 requests) were made to Static.ngs.ru. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Cdn.iportal.ru.
Page size can be reduced by 705.2 kB (5%)
13.6 MB
12.9 MB
In fact, the total size of 59.ru main page is 13.6 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 12.6 MB which makes up the majority of the site volume.
Potential reduce by 579.7 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.7 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. 59 images are well optimized though.
Potential reduce by 125.5 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.5 kB or 46% of the original size.
Number of requests can be reduced by 27 (55%)
49
22
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 59. 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.
59.ru
503 ms
59.ru
919 ms
context.js
1041 ms
js
57 ms
tag.js
911 ms
ad-category-recognition.js
902 ms
AdRiverFPS.js
1032 ms
header-bidding.js
1216 ms
hsm-creative-manager.471.js
833 ms
asdk.js
831 ms
weboctx.min.js
27 ms
146x32.svg
885 ms
6043320a52805b72b3bd692f5e3cf7540344bbcc_1920_1920_c.jpg
1336 ms
sun-cloud.f76a355.svg
797 ms
acee051395ad511b912275c373a597470846cdbf_3000_2000_c.jpg
2401 ms
949bcef19242e8cb98ffc53c5f4d2e950d7e5fe8_3000_2000_c.JPG
2189 ms
e3a83767458d355cd9f547f46ee3db310d73203b_1000_667_c.jpg
1308 ms
71a88c876cdf895b9d5de363768838d90cd503d3_1280_853_c.jpg
1542 ms
f309835f3c1ad22d6f20e418e46f17260dc3a3d4_1191_794_c.jpg
1130 ms
743da98e7fc9b7df1bf21d61b2d4e1660ef5eb7f_1680_1120_c.jpg
2169 ms
9abb682ab20c21d356cf191df2653cda0dafd0fd_1920_1280_c.jpg
1936 ms
bc696d0cb189698d6240a0badfe7ca260be0542b_1920_1280_c.jpg
1493 ms
79eaed2a688b18960fb0f74adb7313dd0dc123e8_1200_800_c.jpg
1620 ms
a44b608ff9f2ef4baca28981877916770171fa4e_1257_838_c.jpg
1833 ms
c9c7cfd29907d73dc853ee708cad3d580456f28e_1199_799_c.jpg
1739 ms
8ba3503d98fd20f7784b296f8b4da2ce01ee11dc_1200_800_c.jpg
1862 ms
bfafadef7fe9fe345a625131b8bebeed089c1380_1200_800_c.jpg
2179 ms
01d161c3c40e2af3b3b2a42b85962a3d0346282b_1280_853_c.jpg
1986 ms
b1cdde0b40a7b2e9f5dfde34ad0b16b400fe9a9e_1920_1280_c.JPG
2407 ms
544881a037297261593bdddcb93b7c290ff115c2_1623_1082_c.jpg
1945 ms
7bddd20938ed59b09d564b0f8d7f2f0101fc9dcd_295_197_c.jpg
2069 ms
runtimechunk~app.848467d.js
450 ms
30400.cf1346b.js
453 ms
new-app.6a2458d.js
764 ms
79877.9b47768.js
525 ms
35820.8aabea7.js
653 ms
new-home-page.e6061c8.js
847 ms
app.e253233.js
654 ms
vq_starter.js
754 ms
OneSignalSDK.js
50 ms
roxot-manager.js
790 ms
hb.js
223 ms
sync-urls.js
1148 ms
sync-loader.js
897 ms
ui-common.b29e597eefc8bb61eb784dd93999db51.svg
66 ms
roboto-v30-latin_cyrillic-regular.woff
155 ms
roboto-v30-latin_cyrillic-700.woff
186 ms
ui-common.b29e597eefc8bb61eb784dd93999db51.svg
134 ms
roboto-slab-v24-latin_cyrillic-regular.woff
271 ms
roboto-slab-v24-latin_cyrillic-700.woff
462 ms
vq_init.js
255 ms
advert.gif
505 ms
vq_init.css
121 ms
sync_cookie_image_decide
145 ms
1
147 ms
1
246 ms
1
130 ms
59.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.
59.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
59.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 59.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 59.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.
59.ru
Open Graph description is not detected on the main page of 59. 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: