9.6 sec in total
1.6 sec
7.3 sec
697 ms
Click here to check amazing My 18 content for Russia. Otherwise, check out these important facts you probably never knew about my18.ru
????? ??????????
Visit my18.ruWe analyzed My18.ru page load time and found that the first response time was 1.6 sec and then it took 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.
my18.ru performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.4 s
1/100
25%
Value7.4 s
27/100
10%
Value1,750 ms
10/100
30%
Value0.097
90/100
15%
Value14.8 s
8/100
10%
1601 ms
859 ms
46 ms
64 ms
282 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 74% of them (99 requests) were addressed to the original My18.ru, 4% (5 requests) were made to Mc.yandex.com and 3% (4 requests) were made to Pos.gosuslugi.ru. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain My18.ru.
Page size can be reduced by 748.3 kB (5%)
13.7 MB
13.0 MB
In fact, the total size of My18.ru main page is 13.7 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 12.9 MB which makes up the majority of the site volume.
Potential reduce by 133.9 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 133.9 kB or 72% of the original size.
Potential reduce by 544.3 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. My 18 images are well optimized though.
Potential reduce by 59.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. This website has mostly compressed JavaScripts.
Potential reduce by 10.3 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. My18.ru needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 11% of the original size.
Number of requests can be reduced by 69 (56%)
124
55
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 18. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
my18.ru
1601 ms
my18.ru
859 ms
css
46 ms
css
64 ms
bootstrap.min.css
282 ms
bootstrap-select.min.css
43 ms
jquery.fancybox.min.css
35 ms
slick-theme.css
408 ms
slick.css
409 ms
font-awesome.min.css
413 ms
select2.min.css
415 ms
jquery-ui.min.css
420 ms
fotorama.css
431 ms
main.css
680 ms
news.css
545 ms
singlenews.css
549 ms
director.css
552 ms
media-all.css
559 ms
owl.carousel.css
570 ms
owl.theme.default.css
682 ms
remodal.css
685 ms
remodal-default-theme.css
688 ms
custom_auth.css
698 ms
styles_v2.css
710 ms
bvi.min.css
814 ms
core.css
816 ms
style.css
824 ms
style.css
825 ms
template_styles.css
837 ms
core.js
1277 ms
main.polyfill.customevent.js
949 ms
dexie.bitrix.bundle.js
1227 ms
core_ls.js
957 ms
core_fx.js
962 ms
core_frame_cache.js
976 ms
jquery.min.js
33 ms
js
72 ms
spxl.js
872 ms
spxl.js
885 ms
style.css
1082 ms
script.min.js
605 ms
bootstrap.min.js
30 ms
bootstrap-select.min.js
15 ms
jquery.fancybox.min.js
7 ms
plyr.css
37 ms
isotope.pkgd.min.js
966 ms
slick.min.js
970 ms
fotorama.js
988 ms
jquery-ui.min.js
1340 ms
select2.full.min.js
1107 ms
uisearch.js
1108 ms
classie.js
976 ms
owl.carousel.js
1071 ms
remodal.js
1069 ms
main.js
1062 ms
bcode.js
1062 ms
responsivevoice.min.js
1056 ms
js.cookie.js
1265 ms
bvi.min.js
1150 ms
bvi-panel.min.js
1149 ms
my18.ru
1063 ms
ba.js
641 ms
tag.js
2016 ms
fbevents.js
132 ms
gosuslugi-logo.svg
161 ms
background.jpg
1548 ms
logo_baumansky_full.png
538 ms
%D0%B3%D0%BE%D0%B4%20%D1%81%D0%B5%D0%BC%D1%8C%D0%B81200.jpg
1547 ms
123.png
1548 ms
495b8580d429709a9234a866eaee82d0.jpg
1548 ms
4fee5a784f6b6f34d60526b948b6251c.png
1546 ms
about-bg.png
1545 ms
icon1.png
1654 ms
phone-bg.png
1652 ms
phone-slide1.jpg
1787 ms
icon3.png
1658 ms
volga.PNG
2464 ms
%D0%91%D0%B5%D0%B7%20%D0%BD%D0%B0%D0%B7%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F%20(1).png
1653 ms
%D0%97%D0%BD%D0%B0%D0%BD%D0%B8%D0%B5%20%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80.jpg
2203 ms
84e2876bb05c95d2712f156412ff9b76.png
1928 ms
2f377a1d6d81cc726076924eed851a51.png
1794 ms
ddb91794f6e7fdcdc1d8f4356ebf31e8.png
1795 ms
ece0142c6a2fab0514fcae9799b5cfc2.png
1922 ms
55272e41e32b4ae20e7d1d3fe2036d24.png
1935 ms
89a2692dabad2f3609965dcab5ed1626.png
1935 ms
4219fce52ee568a9e878a95bb1c925a8.png
2121 ms
d0a9927a3552ee3f28d38638734f14af.png
2122 ms
402ab283d93fbfbe9b785965123d57f8.png
2123 ms
f20b51b5be462fac97f6d9649e310795.png
2124 ms
icon2.png
2193 ms
left-arrow.png
2113 ms
227 ms
KFOmCnqEu92Fr1Mu5mxM.woff
127 ms
KFOlCnqEu92Fr1MmSU5fABc-.woff
226 ms
KFOkCnqEu92Fr1MmgVxMIzQ.woff
422 ms
KFOlCnqEu92Fr1MmWUlfABc-.woff
421 ms
fontawesome-webfont.woff
2377 ms
right-arrow.png
2097 ms
alronix_logo_01.png
2212 ms
749364325505995
379 ms
default_img_main_new2.jpg
2158 ms
PAA_5850.JPG
3035 ms
PAA_5343.JPG
2739 ms
Lato-Regular.woff
1359 ms
Lato-Bold.woff
1932 ms
PAA_4790.JPG
2679 ms
PAA_4210.JPG
2707 ms
115 ms
PAA_4047.JPG
2083 ms
PAA_3834.JPG
2389 ms
PAA_2924.JPG
2138 ms
PAA_2984.JPG
1629 ms
PAA_3081.JPG
1812 ms
PAA_3328.JPG
1800 ms
PAA_2479.JPG
1750 ms
PAA_2007.JPG
1784 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
210 ms
PAA_1898.JPG
1771 ms
PAA_1494.JPG
1983 ms
PAA_1163.JPG
1789 ms
PAA_0559.JPG
1817 ms
PAA_5063.jpg
1818 ms
rtrg
119 ms
PAA_5862.JPG
1706 ms
PAA_5504.JPG
1717 ms
PAA_5311.JPG
1790 ms
ajax-loader.gif
1684 ms
metrika_match.html
606 ms
advert.gif
740 ms
metrica
653 ms
sync_cookie_image_decide
142 ms
1
143 ms
1
145 ms
my18.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 input 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
my18.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
Page has valid source maps
my18.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
N/A
![]()
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My18.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 My18.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.
my18.ru
Open Graph description is not detected on the main page of My 18. 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: