11.3 sec in total
604 ms
8.7 sec
2 sec
Welcome to dszn.ru homepage info - get ready to check Dszn best content for Russia right away, or after learning these important things about dszn.ru
Департамент труда и социальной защиты населения города Москвы
Visit dszn.ruWe analyzed Dszn.ru page load time and found that the first response time was 604 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dszn.ru performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value15.7 s
0/100
25%
Value19.1 s
0/100
10%
Value6,480 ms
0/100
30%
Value0.007
100/100
15%
Value26.0 s
0/100
10%
604 ms
4182 ms
740 ms
838 ms
90 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 93% of them (87 requests) were addressed to the original Dszn.ru, 2% (2 requests) were made to Mc.yandex.ru and 2% (2 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Dszn.ru.
Page size can be reduced by 2.6 MB (75%)
3.5 MB
871.5 kB
In fact, the total size of Dszn.ru main page is 3.5 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. CSS take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 401.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. This page needs HTML code to be minified as it can gain 116.4 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 401.7 kB or 83% of the original size.
Potential reduce by 776.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 776.2 kB or 58% of the original size.
Potential reduce by 1.5 MB
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. Dszn.ru needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 86% of the original size.
Number of requests can be reduced by 56 (88%)
64
8
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dszn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
dszn.ru
604 ms
dszn.ru
4182 ms
font_ios.css
740 ms
bootstrap.min.css
838 ms
bootstrap-datetimepicker.css
90 ms
font-awesome.min.css
84 ms
main.css
1174 ms
mcdir-calc.css
114 ms
dev.css
892 ms
version.css
146 ms
print.css
767 ms
jquery.fancybox.min.css
345 ms
jquery.min.js
534 ms
bootstrap.js
250 ms
moment.min.js
1179 ms
tempust.min.js
1179 ms
bootstrap-datetimepicker.min.js
1175 ms
galleria-1.5.7.min.js
715 ms
jquery.validate.js
1170 ms
jquery.validate.add-method.js
1172 ms
jquery.validate.ru.min.js
1174 ms
jquery.validate.site.min.js
1171 ms
jquery.cookie.js
1752 ms
jquery-ui.js
1172 ms
content-lazy-load.js
1292 ms
jquery.mCustomScrollbar.min.js
1173 ms
main.js
1462 ms
route.rules.js
1292 ms
jquery.lazy.min.js
1380 ms
im.js
1528 ms
mcdir-calc.js
1461 ms
dev.js
1462 ms
main-press-center.js
1511 ms
promo-block.js
1615 ms
ready-banner.js
1602 ms
map-widget.js
1675 ms
widget-wrapper-callback.js
1685 ms
806 ms
yandex.mapController.js
1701 ms
js.cookie.js
1893 ms
user.location.js
1894 ms
jquery.fancybox.min.js
1704 ms
search.js
1930 ms
spelling.js
1707 ms
technical-support.js
1724 ms
yii.js
1682 ms
jquery.inputmask.bundle.js
1482 ms
04d60c65efb8ab5ac229f4c89aaeaf07ff655f75.svg
1128 ms
e37203be03ffa0d32e7728bfb78fc295
1141 ms
203e532a6de9c73b1c384a2de58f2e6c
1329 ms
65f522613f74727a35593eafd12cdd57
1266 ms
ecd41c656b43a51851f31f58811fa522
1273 ms
b517f7c614c2d45471c059678d6380c2
1016 ms
d6e05b45521d5732b24d7c5afb89c5e5
1272 ms
98c5b1b129bf18b6a7a7b2d91e3bbe11
2141 ms
a097cdc579a51b69cec3e071d80ed42f
1437 ms
0a92ba9d450b3462217f6cc60dd8f516
1359 ms
0362cd578b9e3486b53a2553d4228d80
1437 ms
47a73ad211a8460fb268ef11e5f5c7fa
1754 ms
dbb1b08b26cc249318d8500fd176ae3d
1663 ms
cce1324ee0ae34a6231269e289bc93cd
1740 ms
45b10d24db1e63b60182adde18aec26a
1741 ms
tag.js
890 ms
GolosText-Regular.woff
1320 ms
watch.js
79 ms
GolosText-Medium.woff
1218 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
229 ms
GolosText-DemiBold.woff
1315 ms
Golostextbold.woff
1315 ms
icomoon.ttf
1316 ms
als_sector-bold.woff
1325 ms
als_sector.woff
1570 ms
GOSTUI2.woff
1235 ms
GOSTUI2-Medium.woff
1311 ms
GOSTUI2-Bold.woff
1252 ms
37c3028230dd1f9e6258fd5be5ee943c2d7857c1.svg
1242 ms
rtrg
204 ms
2d6e0ed25e3ea3b3aaf745bb3d39a71a5605a822.svg
1241 ms
fc3b26bbf5bb50db8ca7fbebd8718cf8e5c0d782.svg
1380 ms
footer-icon2.svg
1297 ms
jquery.mousewheel.min.js
141 ms
footer-icon3.svg
1309 ms
full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js
1947 ms
soc-box-icon-vk.svg
1300 ms
soc-box-st-icon-vk.svg
1162 ms
soc-box-icon-youtube.svg
1187 ms
soc-box-st-icon-youtube.svg
1385 ms
soc-box-icon-od.svg
1377 ms
soc-box-st-icon-od.svg
1183 ms
soc-box-icon-tg.svg
1015 ms
soc-box-st-icon-tg.svg
946 ms
SFUIText-Regular.woff
848 ms
SFUIText-Semibold.woff
849 ms
SFUIText-Bold.woff
868 ms
dszn.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
dszn.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
dszn.ru SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Dszn.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 Dszn.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.
dszn.ru
Open Graph description is not detected on the main page of Dszn. 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: