5.7 sec in total
1.5 sec
3.9 sec
282 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.5 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
my18.ru performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value15.5 s
0/100
25%
Value10.9 s
6/100
10%
Value1,920 ms
8/100
30%
Value0.08
94/100
15%
Value21.2 s
1/100
10%
1517 ms
10 ms
290 ms
290 ms
296 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 94% of them (72 requests) were addressed to the original My18.ru, 4% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain My18.ru.
Page size can be reduced by 1.7 MB (60%)
2.7 MB
1.1 MB
In fact, the total size of My18.ru main page is 2.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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 54.2 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 7.9 kB, which is 12% 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 54.2 kB or 80% of the original size.
Potential reduce by 979.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, My 18 needs image optimization as it can save up to 979.7 kB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 530.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 530.0 kB or 73% of the original size.
Potential reduce by 90.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 90.3 kB or 87% of the original size.
Number of requests can be reduced by 33 (43%)
76
43
The browser has sent 76 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 18 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
my18.ru
1517 ms
jquery.min.js
10 ms
rokbox-style.css
290 ms
style1.css
290 ms
attachments1.css
296 ms
attachments.css
295 ms
template.css
302 ms
mootools-core.js
712 ms
core.js
431 ms
caption.js
432 ms
mootools-more.js
1170 ms
rokbox.js
733 ms
rokbox-config.js
451 ms
attachments_refresh.js
574 ms
behaviour.js
574 ms
jwplayer.min.js
1206 ms
silverlight.js
859 ms
wmvplayer.js
861 ms
AC_QuickTime.js
853 ms
template.css
1145 ms
slider_m.css
1006 ms
slider.js
890 ms
phocagallery.css
866 ms
modal.css
876 ms
boxplus.css
927 ms
boxplus.darksquare.css
1014 ms
modal.js
1017 ms
boxplus.js
1163 ms
boxplus.lang.js
1043 ms
analytics.js
29 ms
background.png
153 ms
menu_dots.png
148 ms
name.png
214 ms
vosklznak.png
501 ms
sport_tantsy.png
389 ms
ruki.png
586 ms
kniga.png
456 ms
img-zay.png
358 ms
knigi_anons2.png
652 ms
twitterbird.png
646 ms
corner_my18lyc.png
537 ms
corner_my18news.png
608 ms
corner_my18nsnews.png
644 ms
corner_my18ssnews.png
683 ms
corner_my18dsinews.png
733 ms
corner_my18cdonews.png
760 ms
%D0%9E%D1%87%D0%B8%D0%B5%D0%B2%D0%B0%20%D0%A0%D0%B0%D0%B8%D1%81%D0%B0%20%D0%90%D0%BB%D0%B5%D0%BA%D1%81%D0%B0%D0%BD%D0%B4%D1%80%D0%BE%D0%B2%D0%BD%D0%B0.jpg
788 ms
42_%20%20%2015-1153.jpg
790 ms
134_DSC_0094.JPG
795 ms
%D0%95%D0%BB%D0%B5%D0%BD%D0%B0%20%D0%98%D0%B2%D0%B0%D0%BD%D0%BE%D0%B2%D0%BD%D0%B0%20%D0%9C%D0%BE%D0%BB%D1%87%D0%B0%D0%BD%D0%BE%D0%B2%D0%B0.jpg
830 ms
%D0%A5%D0%BE%D1%85%D0%BE%D0%BD%D1%8C%20%D0%98%D1%80%D0%B8%D0%BD%D0%B0%20%D0%98%D0%B2%D0%B0%D0%BD%D0%BE%D0%B2%D0%BD%D0%B0.jpg
879 ms
mincult12.gif
911 ms
ruki_2.png
1075 ms
vnd.jpg
934 ms
phoca_thumb_m_dsc_0019.jpg
939 ms
phoca_thumb_m_img_7561.jpg
976 ms
phoca_thumb_m_img_9071.jpg
1026 ms
phoca_thumb_m_img_6224.jpg
1062 ms
phoca_thumb_m_img_6109.jpg
1078 ms
f.png
1084 ms
B.png
1123 ms
s.png
1169 ms
collect
10 ms
collect
65 ms
collect
30 ms
t.png
1148 ms
yt.png
1149 ms
rss.png
1125 ms
CISCO.png
1084 ms
doska-2.jpg
1122 ms
vlevo.png
1109 ms
vpravo.png
1146 ms
Sayt_20.jpg
1009 ms
loading.png
981 ms
transparent.gif
920 ms
buttons.png
921 ms
resize.png
932 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
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
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
RU
UTF-8
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), while the claimed language is Russian. Our system also found out that My18.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.
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: