11.5 sec in total
1.1 sec
9.5 sec
908 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 1.1 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
59.ru performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value12.1 s
0/100
25%
Value19.5 s
0/100
10%
Value2,540 ms
4/100
30%
Value0.004
100/100
15%
Value24.1 s
0/100
10%
1098 ms
938 ms
958 ms
935 ms
475 ms
Our browser made a total of 219 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 59.ru, 34% (75 requests) were made to I.sdska.ru and 16% (34 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 2.7 MB (53%)
5.0 MB
2.3 MB
In fact, the total size of 59.ru main page is 5.0 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 2.5 MB which makes up the majority of the site volume.
Potential reduce by 207.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 207.7 kB or 81% of the original size.
Potential reduce by 764.2 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. Obviously, 59 needs image optimization as it can save up to 764.2 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 69% of the original size.
Potential reduce by 631.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. 59.ru needs all CSS files to be minified and compressed as it can save up to 631.9 kB or 87% of the original size.
Number of requests can be reduced by 107 (51%)
210
103
The browser has sent 210 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 56 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
59.ru
1098 ms
jquery-1.9.1.min.js
938 ms
jquery-1.8.3.min.js
958 ms
jquery.js
935 ms
jquery.xdomainrequest.min.js
475 ms
png.css
476 ms
popup_passport.css
477 ms
styles.css
630 ms
d_common.css
632 ms
d.css
633 ms
jquery.smartbanner.css
789 ms
styles.css
786 ms
announce.css
789 ms
widgets_common.css
1004 ms
widgets.css
1006 ms
news_d.css
1005 ms
news_common.css
1085 ms
styles.css
1086 ms
styles.css
1089 ms
styles.css
1094 ms
widgets.css
1095 ms
pt_serif.css
1097 ms
common.js
1237 ms
sdb.js
1242 ms
jquery.cookie.js
1244 ms
api.js
1724 ms
jquery.waypoints.js
1245 ms
fotorama-4.4.2.js
1397 ms
fotorama.waypoints.js
1388 ms
dohcohT2.js
538 ms
popup.js
1395 ms
ngs-place.js
1392 ms
startpage.js
1393 ms
browser_detect.js
1540 ms
google_charts.js
1547 ms
jquery.smartbanner.js
1548 ms
jquery.multi-ddm.js
1549 ms
scroll.js
1549 ms
dropdown.js
1270 ms
update_browser.js
1269 ms
paginate.js
1116 ms
poll.js
1114 ms
jquery.jcmcarousel.js
1253 ms
analytics.js
18 ms
boomerang-0.9.1401865982.js
188 ms
top100.cnt
275 ms
55x55_0_58ac789573b5f25f1cff4a35d048c540@300x182_0xc0a839a2_3086281261460057565.jpeg
356 ms
55x55_0_00ba2380588af226e7f63d59e0fb7fb1@389x231_0xc0a839a2_13908593811459893763.png
356 ms
2-z20-fd234f1e-a213-4ebc-acfd-59fdb992bb13.jpg
786 ms
2-z32-484a3abb-882f-491d-93e0-27788ef39468.jpg
632 ms
2-z3-01b9f3d2-0fc0-49a1-980b-26bf2d6a817f.jpg
512 ms
2-z29-0bac6c29-9757-4033-9335-95cfe17e2470.jpg
511 ms
2-z6-fb79f688-b68e-42ff-8633-79943646303b.jpg
484 ms
2-z1-c822a3cc-8aea-457e-9713-3d44e8f6a89f.jpg
490 ms
2-z23-ac3daa69-dfc4-401a-a868-6e3dd43b73de.jpg
508 ms
banner-88x31-rambler-gray2.gif
280 ms
logo;59
311 ms
55x55_0_d4be4d330f18c590dd327eb08a0ec595@300x182_0xc0a839a2_14912715521460064050.jpeg
352 ms
55x55_0_c737e279d8b61e4e1319a2880ac626b9@235x143_0xc0a839a2_7694223801459870584.jpeg
350 ms
mobile.gif
179 ms
12x12.png
179 ms
12x12.png
178 ms
12x12.png
177 ms
12x12.png
177 ms
18plus.png
349 ms
logo.59.ru.png
345 ms
6.png
345 ms
6.png
343 ms
x.gif
342 ms
video.png
344 ms
b3.gif
511 ms
gorod-online.png
510 ms
video_blue.gif
510 ms
rugion_job.png
509 ms
auto.59.png
510 ms
dom.59.png
511 ms
fin.59.png
658 ms
doctor.59.png
660 ms
afisha.59.png
657 ms
rugion-logo-color.png
660 ms
rn-logo-color.png
660 ms
18plus_bottom.png
659 ms
collect
14 ms
hit;59
291 ms
hit;rugion
306 ms
59
312 ms
watch.js
0 ms
watch.js
0 ms
tcounter.js
301 ms
179 ms
collect
105 ms
ga-audiences
132 ms
178 ms
hit;59
139 ms
hit;rugion
147 ms
59
127 ms
199 ms
3ddc23eba0fcfa5c4b258fcd1769dd8f_121.jpg
349 ms
tpx
349 ms
2-z6-dc51df14-a915-43ac-8a36-844705735daa.png
308 ms
2-z22-a3a15a97-238b-4701-a661-bee35d05ab16.png
465 ms
2-z5-18e04bac-b571-43d3-bb49-5540f170d55c.png
660 ms
2-z19-a36158b2-8f4e-40e1-85ce-fd50a5d5f46d.png
625 ms
2-z10-f8ded5f4-7461-4f3b-9df9-3eebaa9a9756.png
876 ms
2-z33-03c048a8-2b0f-44bc-b80d-6e828b701669.jpg
531 ms
2-z21-2733bbd4-57fe-4071-b9c7-5a62ce3bfa4d.png
766 ms
2-z7-920eabac-d149-4d9d-a3b4-1103fad2488f.png
818 ms
2-z24-2738852d-1d7c-4660-b16c-f253397f24f4.png
739 ms
2-z15-ee24d8e3-e7f1-4b7e-b81e-ce96977ea94a.png
732 ms
2-z9-baa8f4a0-29d1-4eea-ae4f-187ca59d2b02.png
646 ms
2-z23-a7a7015f-8135-4287-be56-1ed600b3c1be.jpg
159 ms
2-z14-9dbacc47-87b9-49d3-b5b9-70f839cf5c30.png
793 ms
2-z3-8363934f-f050-4d2b-adf0-5b7061cbd1af.png
494 ms
74527660
271 ms
2-z20-a2fbd37e-cc73-4624-a793-25dbb70bc285.png
482 ms
2-z19-94124890-23c5-4c52-b302-b3e72014fff2.png
619 ms
2-z22-73a8f3a6-235e-4830-8458-7f1a613fd388.png
482 ms
2-z21-9f002610-3066-49ca-a938-48433143c4e9.jpg
449 ms
button.png
193 ms
userbutton.png
194 ms
2-z33-1f016b68-4e06-4689-bd76-261804ec4831.jpg
521 ms
2-z33-e8eb3287-581e-460b-ae04-42931abc114b.png
678 ms
355 ms
p_common.css
154 ms
service_icons_simple.gif
162 ms
96adee935658e8547d53efc24e0fd7f5_217.jpg
544 ms
tpx
178 ms
179 ms
43d54eea0c2d9ef47c7bc64ed20c3c4b_462.jpg
186 ms
tpx
177 ms
359 ms
adsbygoogle.js
36 ms
tpx
212 ms
input-back.png
166 ms
select-back.png
167 ms
button-back.png
167 ms
line.png
180 ms
181 ms
ca-pub-6074599255075755.js
48 ms
zrt_lookup.html
40 ms
show_ads_impl.js
56 ms
ads
210 ms
osd.js
43 ms
412aee86940c2cc3f9b5a7c6f63092d5_119.jpg
179 ms
tpx
177 ms
212 ms
5400389523403473514
39 ms
abg.js
42 ms
m_js_controller.js
52 ms
googlelogo_color_112x36dp.png
33 ms
s
23 ms
x_button_blue2.png
25 ms
b54141b895025203be1312c411846add_217.jpg
374 ms
tpx
186 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
3 ms
186 ms
c51d88a8437fe06ba0dbd88e7a2989da_104.jpg
187 ms
tpx
186 ms
186 ms
ads
281 ms
tpx
177 ms
230 ms
196 ms
9119330473792315707
31 ms
push
53 ms
pixel
15 ms
context.js
231 ms
tpx
176 ms
context_static_r1082.js
376 ms
watch.js
1 ms
46287
242 ms
activeview
53 ms
229 ms
182 ms
01aa7024700bba795a98fce6c681118c_317.jpg
393 ms
tpx
190 ms
218 ms
2-z26-463302a6-8a10-4e24-85c9-b7bfcdbf0565.jpg
462 ms
2-z25-7063d100-ab3e-4d86-9300-721954792542.jpg
450 ms
2-z5-f6078df9-0735-4309-9ae1-bd8df4ab70c8.jpg
165 ms
2-z29-393628a4-2231-42e9-927c-0f5b81108e1b.jpg
169 ms
2-z24-a1a287b2-4068-43a5-9f9f-c8d53913d3c4.jpg
230 ms
2-z35-b39d9040-fe2c-4a80-a05c-536006f20291.jpg
481 ms
2-z17-5dd29654-6de4-4aa6-b474-6f25e634866b.jpg
529 ms
2-z22-81c23fe4-5b44-4d5a-adca-280d05be5989.jpg
306 ms
2-z34-c70d5120-5a1a-4a09-b1e7-27b95e95caa5.jpg
547 ms
2-z3-846dcf29-f0b2-4f96-b8cd-63ba08fcbf5d.jpg
174 ms
2-z13-62bc096e-c7ab-4434-a2b2-c91ab88d8372.jpg
494 ms
2-z11-02dc272a-67d4-47be-b0e5-3f1e679aebc5.jpg
498 ms
2-z8-70256a57-4482-4214-b74e-5b2da5f8e599.jpg
535 ms
2-z31-cb89cd34-3f13-4665-bf1e-5df2527af7c4.jpg
475 ms
2-z4-24b9a057-a8b6-4b30-8b8b-38876f0f1611.jpg
386 ms
2-z23-56f806d9-1d95-4bb9-995e-f074963f4220.jpg
174 ms
2-z12-f3035b0b-9b68-461d-9ea7-612433f649d1.jpg
485 ms
2-z16-53f81783-2fb8-47e9-a6eb-e647ca082ac8.jpg
457 ms
2-z10-6b397c2b-bf9b-4b33-99d2-502e5902d25e.jpg
159 ms
2-z33-82f1dae2-68f8-4409-90b9-8b38740e4da3.jpg
159 ms
2-z18-cfc57aff-2443-4a45-9788-1b447dd28fae.jpg
452 ms
2-z19-62fde356-3915-4b19-b5e8-dd834056c83b.jpg
358 ms
2-z25-d5ab657d-dabf-43a7-b76f-a28e9e685933.jpg
384 ms
2-z25-8e0ce4f9-eb2b-45bb-9d9c-03ab2aa1ef6e.jpg
385 ms
2-z17-02446aa6-a3de-47fa-958a-d9657596d0f2.jpg
438 ms
2-z13-03ea7ea2-7ce6-4549-bb2a-d118eed9d68a.jpg
437 ms
2-z29-c978a349-a851-4fcf-a232-4090a56ec931.jpg
342 ms
2-z31-6027700a-8a50-4fce-9d2d-0fa42a024ddf.jpg
444 ms
2-z35-86b96af5-8ea1-42cb-b324-1759e5bb65d5.jpg
388 ms
2-z35-23f1a67c-3a72-4984-95b4-630bbe3cf30a.jpg
389 ms
2-z23-4a23fbda-6a06-4119-96db-ce20a657bdac.jpg
345 ms
2-z24-b8e95fd1-960c-45f4-b615-c15770a4b5b7.jpg
343 ms
2-z5-06cfbab1-907d-4c2c-85d9-a14f2973624c.jpg
230 ms
2-z5-1db508d1-6f56-4cd7-aa47-0d616ec7206e.jpg
343 ms
2-z5-ad4ea5d2-675b-4580-8f3c-97795b9da39b.jpg
345 ms
service_icons.png
308 ms
59
483 ms
180 ms
Widget_Login
174 ms
sprite_button.png
157 ms
checkauth.php
792 ms
check
1094 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
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
59.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
WINDOWS-1251
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 59.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
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: