5.9 sec in total
633 ms
4.7 sec
607 ms
Click here to check amazing Vsekratko content for Russia. Otherwise, check out these important facts you probably never knew about vsekratko.ru
Краткие содержания, пересказы и изложения кратких содержаний произведений по главам. Кратко Евгении Онегин, Мертвые души, Дубровский, Капитанская дочка, Война и мир, Отцы и дети, Преступление и наказа...
Visit vsekratko.ruWe analyzed Vsekratko.ru page load time and found that the first response time was 633 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
vsekratko.ru performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value2.1 s
96/100
25%
Value3.1 s
93/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value2.1 s
99/100
10%
633 ms
239 ms
375 ms
511 ms
255 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Vsekratko.ru, 51% (44 requests) were made to St6-21.vk.com and 9% (8 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 525.7 kB (18%)
2.9 MB
2.4 MB
In fact, the total size of Vsekratko.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. 45% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 66.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 66.8 kB or 77% of the original size.
Potential reduce by 4.2 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. Vsekratko images are well optimized though.
Potential reduce by 382.5 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 382.5 kB or 17% of the original size.
Potential reduce by 72.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. Vsekratko.ru needs all CSS files to be minified and compressed as it can save up to 72.3 kB or 14% of the original size.
Number of requests can be reduced by 63 (78%)
81
18
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vsekratko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
vsekratko.ru
633 ms
style.css
239 ms
share.js
375 ms
form.js
511 ms
openapi.js
255 ms
jquery.min.js
8 ms
cnt.share.js
428 ms
logo3.png
121 ms
banner_right_l.gif
502 ms
intro.orf
205 ms
jquery.min.js
163 ms
cuprum.orf
127 ms
ga.js
8 ms
__utm.gif
16 ms
hit
256 ms
_form.js
94 ms
yandex-hint.png
93 ms
hit
533 ms
openapi.318ba3d5a50b8d6990cb0284cb0e0963.js
233 ms
counter2
283 ms
upload.gif
116 ms
ya-share-cnt.html
250 ms
watch.js
2 ms
b-share-icon.png
346 ms
b-share_counter_large.png
429 ms
widget_community.php
307 ms
share_count
808 ms
fql.query
60 ms
share.php
178 ms
loader_nav21085582594_3.js
473 ms
fonts_cnt.c7a76efe.css
1023 ms
lite.93f44416.css
721 ms
lang3_2.js
520 ms
polyfills.dae7dc72.js
715 ms
vkui.388c7a16.css
801 ms
xdm.js
625 ms
ui_common.b88d9de7.css
712 ms
react.6a15a5cc.js
896 ms
vkcom-kit.821c0982.css
939 ms
vkcom-kit.22a50b29.js
1107 ms
vkui.55891411.js
1064 ms
vkcom-kit-icons.818eaff7.js
994 ms
architecture-mobx.4e49bc0d.js
1001 ms
state-management.94ab436a.js
1065 ms
audioplayer-lib.93b52d88.css
1082 ms
audioplayer-lib.977d2417.js
1199 ms
common.6bb838ef.js
1746 ms
7f463667.2f09ffd3.js
1115 ms
ui_common.b1037836.css
1136 ms
ui_common.5a3ae89b.js
1176 ms
audioplayer.7787a5d3.css
1191 ms
audioplayer.a6e96a25.js
1194 ms
widget_community.4978d481.css
1223 ms
5441c5ed.4aafa0df.js
1272 ms
aa3c5e05.3f71e48c.js
1282 ms
likes.33883160.css
1271 ms
likes.863c53eb.js
1292 ms
vkcom-kit.27db8b45.css
1319 ms
vkcom-kit.34732429.js
1377 ms
react.84cfd9aa.js
1376 ms
vkui.c3a00357.js
1475 ms
vkcom-kit-icons.9854351b.js
1385 ms
architecture-mobx.d853b516.js
1423 ms
audioplayer-lib.85b39ca5.css
1454 ms
audioplayer-lib.2a9d3e65.js
1551 ms
state-management.e5a289bd.js
1479 ms
c3d11fba.5504cac7.js
1515 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
447 ms
community.be2fc20a.css
914 ms
base.ec2ae8ae.css
879 ms
0fc69f32.2199e165.js
872 ms
e7eaa3a9.0425872f.js
886 ms
57703e15.c98d81ac.js
830 ms
edb6ffde.550285ea.js
1223 ms
community.d3ba8a5d.js
739 ms
c_584d6646.jpg
584 ms
QulWsGFAn5k.png
589 ms
nhvIpczTiJReLEG03zziBJCUWNqbov0Gffa-xQvVDXeYDe5h6XdulDbMaGELaiZdDShwRPyFanZhvQkJVB3iZLE2.jpg
443 ms
GV-HJDIqplVdMC76Nu1XAg8sufKzRR2cDEEr5Le8Np-f2HeC2LgIFi3KoHtX3vcxJT_YTo8JhyKINef6pnUaibfb.jpg
472 ms
fwrFb2fS5zYJ0ubTTYLPx4yr9Ik9YlVUD1P1vOZG2y5CdrLeXtqGit5INxOfTC_F0yVUjfC21RGcr031ho-lbbkS.jpg
456 ms
oeW6h9sFt1JLcZ_POrf45B1DmpyXl6Q9NL-3YFtH-Klva7kRMgYGlmIoRiq9gpdVv1maH1p6.jpg
322 ms
NG5e0ze_fEMQCPpQm9LrOfKIQHEOxSGVZbsAWADnXjMU2G7Zb1f-M7obroHZxQA2t9Aum7AA.jpg
476 ms
1CI-hqiTwKIhxYRXKYfv5DeeihVZCkk25AWFK78SSCqIHzC3hXSiUoGNBFxEpR1WQDjIPfN0YYfwohoyBqHpkby7.jpg
486 ms
BYx-b8AjbdWbeII0Dxu1S0GpW4DjywLbVPmg6-moKQQWEMX046OeeBsmBUn9fgn1DW-u5A.jpg
485 ms
mmv1pcj63C4.png
593 ms
3zWC6-ABTvbiXug5EZTj1yeIGMqM-krhdRf0HZqoM0RAxcyZMv9ttG63_uPmKLghj7WhlE-GBvH28ur6HJUqR7Jg.jpg
360 ms
upload.gif
87 ms
vsekratko.ru accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
vsekratko.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
vsekratko.ru SEO score
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
![]()
RU
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vsekratko.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 Vsekratko.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.
vsekratko.ru
Open Graph description is not detected on the main page of Vsekratko. 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: