4.9 sec in total
438 ms
4.2 sec
261 ms
Visit downtown.ru now to see the best up-to-date Downtown content for Russia and also check out these interesting facts you probably never knew about downtown.ru
Visit downtown.ruWe analyzed Downtown.ru page load time and found that the first response time was 438 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
downtown.ru performance score
438 ms
203 ms
395 ms
299 ms
204 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 50% of them (59 requests) were addressed to the original Downtown.ru, 9% (11 requests) were made to Vk.com and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Downtown.ru.
Page size can be reduced by 359.9 kB (13%)
2.8 MB
2.5 MB
In fact, the total size of Downtown.ru main page is 2.8 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 2.5 MB which makes up the majority of the site volume.
Potential reduce by 61.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 61.8 kB or 76% of the original size.
Potential reduce by 104.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. Downtown images are well optimized though.
Potential reduce by 162.2 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 162.2 kB or 68% of the original size.
Potential reduce by 31.5 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. Downtown.ru needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 80% of the original size.
Number of requests can be reduced by 49 (43%)
114
65
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Downtown. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
438 ms
cusel.css
203 ms
downtown.css
395 ms
blocks.css
299 ms
admin.css
204 ms
search.css
204 ms
jquery.min.js
75 ms
jquery-migrate-1.2.1.min.js
9 ms
jquery-ui.min.js
94 ms
blocks.js
274 ms
cls-main.js
293 ms
cusel-min-2.4.1.js
296 ms
jquery.form.min.js
299 ms
jquery.nano.js
366 ms
jquery.dtbubble.js
423 ms
jquery.fancybox-1.3.4.pack.js
422 ms
jquery.fancybox-1.3.4.css
424 ms
mark.css
425 ms
jquery.marker.js
473 ms
spcjs.php
472 ms
ga.js
25 ms
__utm.gif
25 ms
spc.php
123 ms
fl.js
191 ms
collect
57 ms
loader.gif
189 ms
logo.png
194 ms
361_168_26dc85cc44d8fafc34960ed806c957fc5320.jpeg
289 ms
168_168_59c35076b8a20ededcdc4a850519e7c27316.jpeg
389 ms
th_ffb0fe74ec6645470969e7e20ba66f008116.png
923 ms
th_3d27d1f2c162e307628887f9685c3d378995.jpeg
694 ms
th_e5533a493de78bcf009477bea8409ad43907.jpeg
938 ms
th_fdb01d244688b8ef3705ab6338ce9a434435.jpeg
677 ms
168_168_6103167e050cb65a836ae17694e478cf3914.jpeg
481 ms
361_168_2b6e6b6f3fed2bcd2c9c76432293398a915.jpeg
593 ms
361_168_8ca6e765489bf16f4d4d73b66d7c72709315.jpeg
779 ms
361_168_5b7de7b2c634f27e34310183942cd0583205.jpeg
1179 ms
168_168_de6c1561e0655412839a1b6b43795abd707.jpeg
980 ms
168_168_e148f04541ad0ba8c11a01bc00e291d9437.jpeg
808 ms
th_41a51a6f3ba808e604f54426be7a76d82786.jpeg
1070 ms
th_89a5daa969777055957fef4bf936f96f8227.jpeg
920 ms
th_8dc610ea2ca3a1799501fbce1f251bd93562.jpeg
1019 ms
th_173ad40d175fa57959bd2fcaed1d9f3c8754.jpeg
1131 ms
th_dda9ec185fa3b9e5ebf748c265afee903342.jpeg
1040 ms
th_3db13316aa33d748fe3b55f3ec2dc9c34233.jpeg
1177 ms
361_168_f85b8e93430f4eb3f9be7aec0eb2cf6d3983.jpeg
1123 ms
361_168_21b9b99c3e77b5a0ef06a2df2bc2d92a7797.jpeg
1224 ms
cf0d97a2140e1a5d2fa9026193dfae047940.png
1165 ms
75ad8bcd759606a3f316e33e01716b8b7046.png
1219 ms
f653b1d86b9f08bb67ff85f7331208657273.png
1228 ms
361_168_f62bcde31e3f3d25d894663918b2d6464718.jpeg
1358 ms
361_168_5a1ef3c7f104725bffea2c7e97486c1f9189.jpeg
1276 ms
9136a8f9021993d34e5ded266b4678d07991.png
1279 ms
app-store-icon.png
1317 ms
vk_icon.png
1318 ms
fb_icon.png
1326 ms
tw_icon.png
1373 ms
ig_icon.png
1374 ms
rss_icon.png
1411 ms
m-logo.png
1410 ms
632b8811ac309464af5f4c0010bd1b21.png
387 ms
icon-set.png
1420 ms
lg.php
112 ms
pfdintextcondpro-medium-webfont.woff
1377 ms
pfdintextcondpro-bold-webfont.woff
1407 ms
mark.png
1485 ms
getCodeTest
134 ms
end_2.png
1125 ms
end_1.png
1034 ms
transparent.gif
581 ms
1556144.jpg
1142 ms
e89ee576fa3313c30985e317e553e2b7.gif
197 ms
lg.php
117 ms
widgets.js
30 ms
watch.js
479 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
14 ms
likebox.php
163 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
16 ms
info.json
79 ms
pfdintextcondpro-regular-webfont.woff
1044 ms
favpost_mask.png
950 ms
jTuqQ-OPDr6.css
47 ms
n370yiaI2G6.css
55 ms
_rx8naC75Dy.js
74 ms
x5F9OMjKyLw.js
102 ms
ICDbTSzjQEg.js
94 ms
TTCre3391I0.js
94 ms
jot
148 ms
1511032_572935759454373_904497812_n.jpg
90 ms
12049613_893001700781109_5235580254030988311_n.png
53 ms
71454_10200835324678874_64647352_n.jpg
54 ms
12651349_1747187068849517_2036200908345379389_n.jpg
56 ms
1914850_115838555455156_1750960534037065487_n.jpg
63 ms
12196164_552671338221651_1781837018146911202_n.jpg
61 ms
1491724_1501386886833756_1087003265165215721_n.jpg
61 ms
wL6VQj7Ab77.png
15 ms
s7jcwEQH7Sx.png
15 ms
I6-MnjEovm5.js
8 ms
vlXaquuXMrr.js
15 ms
advert.gif
90 ms
widget_community.php
839 ms
1
92 ms
loader_nav19127_3.js
128 ms
lite.css
254 ms
lite.js
504 ms
lang3_0.js
261 ms
widget_community.css
260 ms
xdm.js
257 ms
al_community.js
259 ms
LiA85zdefmE.jpg
384 ms
AHIqvSEtgss.jpg
383 ms
e_0a2872fd.jpg
389 ms
u6C_C769HN4.jpg
391 ms
YfmYmOp4Mms.jpg
260 ms
z3yU1qq6zYk.jpg
397 ms
aefx6lhvHD4.jpg
392 ms
camera_50.png
127 ms
upload.gif
128 ms
w_logo.png
127 ms
downtown.ru SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Downtown.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Downtown.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.
downtown.ru
Open Graph description is not detected on the main page of Downtown. 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: