8.3 sec in total
441 ms
7.2 sec
626 ms
Welcome to soyuz.ru homepage info - get ready to check Soyuz best content for Russia right away, or after learning these important things about soyuz.ru
СОЮЗ: Всё самое интересное в мире музыки, кино, литературы, игр. Новости, рецензии, обзоры, новинки и многое другое!
Visit soyuz.ruWe analyzed Soyuz.ru page load time and found that the first response time was 441 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
soyuz.ru performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value15.3 s
0/100
25%
Value9.7 s
10/100
10%
Value1,240 ms
19/100
30%
Value0.464
19/100
15%
Value19.1 s
3/100
10%
441 ms
1517 ms
633 ms
474 ms
120 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 42% of them (75 requests) were addressed to the original Soyuz.ru, 12% (22 requests) were made to Pbs.twimg.com and 9% (16 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Cs627129.vk.me.
Page size can be reduced by 1.3 MB (43%)
2.9 MB
1.6 MB
In fact, the total size of Soyuz.ru main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 280.0 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 280.0 kB or 88% of the original size.
Potential reduce by 18.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. Soyuz images are well optimized though.
Potential reduce by 787.0 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 787.0 kB or 73% of the original size.
Potential reduce by 172.7 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. Soyuz.ru needs all CSS files to be minified and compressed as it can save up to 172.7 kB or 83% of the original size.
Number of requests can be reduced by 75 (43%)
175
100
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Soyuz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
soyuz.ru
441 ms
www.soyuz.ru
1517 ms
style.css
633 ms
DD_roundies_0.0.2a-min.js
474 ms
plusone.js
120 ms
prototype.js
1267 ms
popups.js
642 ms
srchCache.js
480 ms
op.js
640 ms
dropdownPopup.css
639 ms
paOrdering.js
787 ms
basket.js
943 ms
cookie.js
795 ms
serializer.js
795 ms
widget-status.css
800 ms
jquery.min.js
35 ms
jquery.tmpl.min.js
13 ms
status-widget.js
739 ms
cb=gapi.loaded_0
16 ms
ga.js
33 ms
__utm.gif
11 ms
votings.js
327 ms
openapi.js
375 ms
addthis_widget.js
13 ms
mail_16.gif
207 ms
rek_16.gif
206 ms
bg-head.gif
197 ms
logo.gif
203 ms
close_red.gif
204 ms
radio-soyuz-part1.jpg
752 ms
radio-soyuz-part5.png
619 ms
radio-soyuz-part6.png
622 ms
radio-soyuz-part7.png
624 ms
radio-soyuz-part8.png
620 ms
radio-soyuz-part12.png
624 ms
radio-soyuz-part13.png
637 ms
radio-soyuz-part14.png
638 ms
banner2.jpg
753 ms
pic1_m.jpg
758 ms
pic3_m.jpg
755 ms
pic1_m.jpg
841 ms
98351_c_m.jpg
750 ms
98346_c_m.jpg
842 ms
98350_c_m.jpg
846 ms
98348_cdvd_m.jpg
845 ms
98333_cdvd_m.jpg
1032 ms
98331_cdvd_m.jpg
965 ms
98344_c_m.jpg
1149 ms
98345_c_m.jpg
966 ms
98337_c_m.jpg
964 ms
98292_c_m.jpg
966 ms
98299_c_m.jpg
1152 ms
98306_c_m.jpg
1275 ms
97910_c_m.jpg
1149 ms
97909_c_m.jpg
1290 ms
97911_c_m.jpg
1147 ms
pic1_m.jpg
1454 ms
pic1_m.jpg
1275 ms
pic1_m.jpg
1292 ms
fastbutton
141 ms
pic1_m.jpg
1259 ms
cb=gapi.loaded_0
37 ms
cb=gapi.loaded_1
48 ms
likebox.php
455 ms
pic1_m.jpg
1268 ms
pic1_m.jpg
1273 ms
pic1_m.jpg
1269 ms
pic1_m.jpg
1267 ms
widgets.js
402 ms
xdmHelper.js
344 ms
upload.gif
333 ms
widget_community.php
351 ms
182 ms
646 ms
boost
152 ms
300lo.json
139 ms
ru.js
131 ms
lt.gif
1027 ms
beige_br.gif
1025 ms
1px.gif
1021 ms
beige_bl.gif
1020 ms
ebiMDO3r-8l.css
200 ms
wakJkBioHgT.css
225 ms
FAHeNGXgPup.js
259 ms
FJmpeSpHpjS.js
343 ms
0wM5s1Khldu.js
329 ms
1bNoFZUdlYZ.js
326 ms
rt.gif
1011 ms
beige_rb.gif
1177 ms
beige_rt.gif
1177 ms
loader_nav19171_3.js
177 ms
lite.css
179 ms
lite.js
271 ms
lang3_0.js
269 ms
widget_community.css
270 ms
page.css
510 ms
xdm.js
299 ms
al_community.js
301 ms
page.js
645 ms
sh.07f0d9bf220d07a763adad1e.html
127 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
379 ms
beige_lb.gif
1063 ms
beige_lt.gif
1063 ms
lb.gif
1060 ms
beige_tr.gif
1210 ms
beige_tl.gif
1201 ms
rb.gif
1127 ms
ajax-loader-indicator-big-beige.gif
1124 ms
ok_32_beige_shdw.gif
1123 ms
bg_green.gif
1258 ms
bg_grey.gif
1155 ms
fb-logo1.gif
1156 ms
vote_points.gif
1152 ms
12743641_1194316593913786_5879536125449048699_n.png
188 ms
169046_199869436691845_4521457_n.jpg
181 ms
12316560_10207626485315997_4594704048907757277_n.jpg
198 ms
999536_1744047509067550_1061428670_n.jpg
211 ms
11846587_156314748036049_1616565830335454116_n.jpg
210 ms
12321651_1119743524727273_8128820658462449494_n.jpg
219 ms
10354686_10150004552801856_220367501106153455_n.jpg
217 ms
5673_998700756858395_6125391712781334009_n.jpg
216 ms
12189837_951227364951001_1475953582998123274_n.jpg
220 ms
10568797_930498776964447_5779934613741861569_n.jpg
224 ms
12512321_594673604022776_8431516543265717349_n.jpg
221 ms
12647149_128895014161135_7379868217895510734_n.jpg
254 ms
263522_2206998818200_5670649_n.jpg
231 ms
12122763_10208240084864007_9216824407909283022_n.jpg
232 ms
wL6VQj7Ab77.png
84 ms
s7jcwEQH7Sx.png
85 ms
vote_unvoted0.gif
1090 ms
syndication
91 ms
694144707266506752
283 ms
I6-MnjEovm5.js
99 ms
pQrUxxo5oQp.js
100 ms
zrXKFuxm0t8.jpg
431 ms
o-saFOr2iuM.jpg
2182 ms
ZnW8VPGdHsU.jpg
474 ms
QydkZpch8Nc.jpg
552 ms
QCcLepXY5zE.jpg
3690 ms
K2Iuk3Daens.jpg
3696 ms
7JohlZ4v6gY.jpg
680 ms
3ptC9pgfkAM.jpg
679 ms
W1yqHG88RVA.jpg
692 ms
Mx1WXVRqibY.jpg
694 ms
u1jOsGePdnA.jpg
695 ms
ecg06fhZOUE.jpg
696 ms
9r0BFD35uk0.jpg
1049 ms
TPDmoS_Gk0w.jpg
1176 ms
w_logo.png
145 ms
playpause.gif
154 ms
mono_iconset.png
152 ms
proxy.jpg
225 ms
CdGR-z7WIAAmAT_.jpg
346 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
54 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
76 ms
irANS_oE_normal.jpg
245 ms
Mv4fgDci_normal.jpg
242 ms
CdqYJamWoAA11YW.jpg:small
273 ms
CdqWyMgWEAEf56W.jpg:small
276 ms
CdlOq2RW8AAx9vJ.jpg:small
396 ms
CdlFAQOUIAALJZI.jpg:small
364 ms
CdgI8pQWAAAFruT.jpg:small
324 ms
Cdf5c80UIAAlSFq.jpg:small
451 ms
CdRY1adWAAA75v0.jpg:small
461 ms
CdROmADW4AA8xqT.jpg:small
408 ms
CdQ_eO8WEAA36N6.jpg:small
438 ms
CdQqM9oXIAAwUuN.jpg:small
538 ms
CdLz-e8W4AEyIOE.jpg:small
526 ms
CdLk2plWIAAEmkS.jpg:small
594 ms
CdLjBqeW0AAWW8i.jpg:small
620 ms
CdLYVUbW4AAZv6S.jpg:small
612 ms
CdHAxeTWIAApey_.jpg:small
549 ms
CdGgSghWAAIfIO3.jpg:small
603 ms
Cc8GaHbUUAIqytj.jpg:small
665 ms
Cdl13GYW8AAXXhp.jpg:small
618 ms
Cdl13LXXIAAgoGi.jpg:small
748 ms
jot
32 ms
soyuz.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
soyuz.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
Missing source maps for large first-party JavaScript
soyuz.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Soyuz.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 Soyuz.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.
soyuz.ru
Open Graph description is not detected on the main page of Soyuz. 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: