12.3 sec in total
1 sec
10.6 sec
712 ms
Welcome to 29.ru homepage info - get ready to check 29 best content for Russia right away, or after learning these important things about 29.ru
Последние свежие новости Архангельска и Архангельской области за сегодня - онлайн на сайте 29.ру
Visit 29.ruWe analyzed 29.ru page load time and found that the first response time was 1 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
29.ru performance score
1003 ms
939 ms
938 ms
958 ms
481 ms
Our browser made a total of 217 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 29.ru, 33% (72 requests) were made to I.sdska.ru and 21% (46 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source I.sdska.ru.
Page size can be reduced by 959.9 kB (50%)
1.9 MB
947.3 kB
In fact, the total size of 29.ru main page is 1.9 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. 60% of websites need less resources to load. Images take 767.9 kB which makes up the majority of the site volume.
Potential reduce by 244.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. 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 244.3 kB or 82% of the original size.
Potential reduce by 111.7 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, 29 needs image optimization as it can save up to 111.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 509.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 509.8 kB or 70% of the original size.
Potential reduce by 94.2 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. 29.ru needs all CSS files to be minified and compressed as it can save up to 94.2 kB or 82% of the original size.
Number of requests can be reduced by 120 (57%)
212
92
The browser has sent 212 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 29. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 71 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
29.ru
1003 ms
jquery-1.9.1.min.js
939 ms
jquery-1.8.3.min.js
938 ms
jquery.js
958 ms
jquery.xdomainrequest.min.js
481 ms
png.css
481 ms
popup_passport.css
482 ms
styles.css
634 ms
d_common.css
634 ms
d.css
636 ms
jquery.smartbanner.css
786 ms
styles.css
787 ms
announce.css
787 ms
widgets_common.css
971 ms
widgets.css
971 ms
news_d.css
971 ms
news_common.css
1088 ms
styles.css
1087 ms
styles.css
1091 ms
styles.css
1097 ms
widgets.css
1097 ms
pt_serif.css
1098 ms
common.js
1238 ms
sdb.js
1241 ms
jquery.cookie.js
1244 ms
api.js
1554 ms
jquery.waypoints.js
1247 ms
fotorama-4.4.2.js
1402 ms
fotorama.waypoints.js
1389 ms
dohcohT2.js
591 ms
popup.js
1390 ms
ngs-place.js
1396 ms
startpage.js
1400 ms
browser_detect.js
1541 ms
google_charts.js
1542 ms
jquery.smartbanner.js
1551 ms
jquery.multi-ddm.js
1575 ms
scroll.js
1576 ms
dropdown.js
1225 ms
update_browser.js
1236 ms
paginate.js
1084 ms
poll.js
1085 ms
jquery.jcmcarousel.js
1084 ms
analytics.js
23 ms
boomerang-0.9.1401865982.js
156 ms
top100.cnt
255 ms
2-z7-bfee4a39-ae08-4693-839c-0bb256f21609.jpg
617 ms
2-z31-1daebb06-f9fa-4a06-993e-ae4e23be2f07.jpg
753 ms
2-z36-d0a6228f-755f-4a20-9433-6292b70d7e9e.jpg
451 ms
2-z22-45e5f20b-4554-4edd-8eef-f99fc1a1eb0a.jpg
318 ms
55x55_0_757dbf6df6a391ad93099cf6ddc7abf0@235x142_0x3e4c1b9b_20290022121456761767.jpeg
321 ms
55x55_0_82a6bb0d039c070eb9788cf945377ba7@300x182_0x3e4c1b9b_9833342221456742759.jpeg
318 ms
banner-88x31-rambler-gray2.gif
262 ms
logo;r29
255 ms
mobile.gif
155 ms
12x12.png
158 ms
12x12.png
158 ms
12x12.png
154 ms
12x12.png
155 ms
18plus.png
300 ms
logo.29.ru.png
311 ms
6.png
307 ms
6.png
309 ms
x.gif
316 ms
video.png
313 ms
b3.gif
453 ms
gorod-online.png
458 ms
rugion_job.png
460 ms
auto.29.png
465 ms
dom.29.png
467 ms
fin.29.png
463 ms
afisha.29.png
607 ms
rugion-logo-color.png
610 ms
rn-logo-color.png
611 ms
18plus_bottom.png
614 ms
55x55_0_c57313bea39bc5dc7441828d63406706@235x142_0xd42ee437_11075470561423479726.jpeg
313 ms
55x55_0_1b7abe23d2f015df02f859643ae687da@235x143_0xd42ee437_5352788491454416310.jpeg
327 ms
hit;r29
254 ms
hit;rugion
257 ms
29
258 ms
watch.js
181 ms
tcounter.js
256 ms
collect
12 ms
207 ms
watch.js
523 ms
d8e8a49b3e49c26960741cf19c9f577d_170.jpg
416 ms
tpx
386 ms
396 ms
hit;r29
128 ms
hit;rugion
131 ms
29
132 ms
148631469
258 ms
p_common.css
156 ms
3a2d4c97cda634ee00fd32187f740ef4_664.jpg
393 ms
tpx
197 ms
200 ms
advert.gif
84 ms
2cb2033956b684231747aae6c9f706a1_196.jpg
888 ms
tpx
193 ms
2-z15-412ac3bf-37ac-4890-b625-d73a014e3864.jpg
470 ms
button.png
156 ms
2-z30-27018878-8e7b-45f0-841f-9974647d858a.jpg
446 ms
2-z24-43f8da23-3a34-44a2-b468-1d237e9b6cca.jpg
569 ms
2-z29-da0cddf7-5490-4ce0-b188-ca15d3c12342.jpg
429 ms
2-z33-e5c51a7c-0844-4ead-a5f0-861fff2635f9.jpg
448 ms
2-z8-c2ed986a-3997-40d9-97c9-510f0e72284d.png
790 ms
2-z14-dd230c05-ce6c-44cb-9176-2da7f069bc06.jpg
449 ms
2-z28-12dbc1c7-9a64-433e-bcaa-5aa1453e7506.jpg
533 ms
2-z9-12b61307-5404-4e5f-994e-aa88d63b5023.jpg
497 ms
2-z19-c78818d0-ef4b-43fb-858e-3090717a9286.jpg
444 ms
2-z2-6c8a9f92-911b-48b1-89e3-e744d3d28262.jpg
478 ms
2-z32-a477232e-a04a-4c9c-b70c-83689e785b89.jpg
723 ms
2-z18-c2fc1124-7693-483a-b58f-3b566d200b9b.jpg
562 ms
2-z26-1a78ad79-e741-467e-9a75-1d8def0ec720.jpg
440 ms
2-z15-c7dfe6c4-a61c-424e-aa25-71aef37e23b7.jpg
463 ms
2-z29-ef7d8117-f045-41c1-83a2-b6bbaad20bf2.jpg
423 ms
2-z29-5882f925-6541-43b4-9c12-1a593642e229.png
615 ms
2-z30-9cb747ec-b140-406b-85a1-fcb2d8827ecb.jpg
436 ms
2-z28-e19d0ecf-033f-4a21-b66e-b3e5bbbb2934.jpg
531 ms
2-z14-a71624f0-5d04-4039-8753-1e9135f4b7a4.jpg
444 ms
352 ms
1
86 ms
12725860
85 ms
service_icons_simple.gif
157 ms
49032645ce9a5236cf358e5e9b682636_361.jpg
586 ms
tpx
193 ms
208 ms
tpx
194 ms
203 ms
2b79dcd41a65a244cf835268d142158a_366.jpg
769 ms
tpx
196 ms
285 ms
input-back.png
156 ms
select-back.png
155 ms
button-back.png
156 ms
line.png
156 ms
208 ms
cb24b4d70036ed31ed2ad5e6d3b158a6_180.jpg
198 ms
tpx
196 ms
200 ms
tpx
196 ms
203 ms
adsbygoogle.js
9 ms
tpx
197 ms
200 ms
ca-pub-6074599255075755.js
41 ms
zrt_lookup.html
43 ms
show_ads_impl.js
58 ms
ads
162 ms
osd.js
6 ms
201 ms
5171746271700867932
39 ms
abg.js
25 ms
m_js_controller.js
38 ms
googlelogo_color_112x36dp.png
75 ms
s
29 ms
x_button_blue2.png
28 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
5 ms
4a105968ee45fbe98c2a8d90d7c9ad09_102.png
198 ms
tpx
196 ms
200 ms
context.js
226 ms
tpx
196 ms
200 ms
201 ms
context_static_r1065.js
672 ms
201 ms
200 ms
202 ms
19331
179 ms
19331
86 ms
202 ms
y150
13 ms
214 ms
2-z18-acc2874a-b08a-4f13-89f6-d25c30fcdeff.png
156 ms
2-z13-a46afc14-ff83-432f-8530-d07eccfebf2c.jpg
506 ms
2-z15-85b1cfe8-d810-451c-8303-8f842e35c348.jpg
155 ms
2-z21-0acd355a-3380-4ed9-9911-32d467ccd03c.jpg
563 ms
2-z20-d595ea8a-d489-4bba-8bc4-e74c8dbbd47f.jpg
474 ms
2-z33-0c2ab51d-5384-45d4-ab38-72f38d1de85a.jpg
159 ms
2-z22-293f307b-76dd-445c-924d-e89d638ffe3b.jpg
155 ms
207 ms
2-z25-9bc2bee6-6df5-4926-8f12-94d74ea3585f.jpg
439 ms
2-z23-e84a624a-fb74-4ce5-9f59-dded2daf6176.jpg
435 ms
2-z30-c51f36f2-65a1-48d2-8415-550881b6f47d.jpg
156 ms
2-z1-1e307598-440f-4ca2-bd56-2c58aa327e35.jpg
486 ms
2-z32-e5e5127f-07bd-430c-85ab-75a0aadaf105.jpg
151 ms
2-z21-93a967a3-0f9b-4f12-aafb-4b5b867210a4.jpg
335 ms
202 ms
200 ms
2-z12-7d9f04d3-ac53-4786-b513-2c1b19f7166f.jpg
439 ms
2-z30-02469591-66a0-4f59-9768-cb6b553da2ab.jpg
157 ms
2-z36-0f41d6c1-451c-4478-a094-0f6acbab6f8b.jpg
154 ms
2-z34-1add2218-bc2c-47e1-9a81-028f649436bd.jpg
470 ms
2-z6-d3f0b92b-a7a8-4011-9379-b0bf8c5f9903.jpg
485 ms
2-z36-0963c37e-05be-4c97-a5f7-69b172f57ed8.jpg
327 ms
202 ms
202 ms
2-z5-3bac2bbc-2631-43a8-89da-441fea0963d3.jpg
437 ms
2-z35-d678afe3-915f-4f6c-ad8b-fa47675106fa.jpg
542 ms
2-z30-e01667d9-446e-4b2b-852e-a2fb08af484a.jpg
156 ms
2-z23-b1785d16-143b-43ca-b14e-9ba6d7d6f76f.jpg
156 ms
2-z20-29313ffb-d503-45a2-b5cd-26d2fe59a3c0.jpg
156 ms
2-z35-535b5053-6cc7-404d-b045-533672c53c24.jpg
537 ms
200 ms
2-z6-1ede6f18-63be-4266-bcf6-b692e4069ad5.jpg
161 ms
2-z30-0f903aed-f3db-4324-a17d-5db6deb39d57.jpg
155 ms
2-z31-276b3e80-98a0-4706-9f1a-4b5786ce0262.jpg
150 ms
2-z34-9c78eda5-cb60-4919-831d-463b4eaa818d.jpg
156 ms
2-z1-0dfe97a7-69a2-49c7-87a8-95e469316411.jpg
155 ms
2-z31-e7a3d089-fd65-4cef-b5ff-185c2994bcf0.jpg
317 ms
service_icons.png
309 ms
213 ms
Widget_Login
163 ms
sprite_button.png
156 ms
checkauth.php
768 ms
check
1211 ms
29.ru SEO score
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 29.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 29.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.
29.ru
Open Graph description is not detected on the main page of 29. 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: