7.3 sec in total
539 ms
6.3 sec
517 ms
Welcome to sweli.ru homepage info - get ready to check Sweli best content for Russia right away, or after learning these important things about sweli.ru
Портал про медицину, здоровье и семью
Visit sweli.ruWe analyzed Sweli.ru page load time and found that the first response time was 539 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sweli.ru performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.1 s
12/100
25%
Value11.4 s
5/100
10%
Value4,500 ms
0/100
30%
Value0.123
83/100
15%
Value43.2 s
0/100
10%
539 ms
1214 ms
160 ms
139 ms
275 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 39% of them (64 requests) were addressed to the original Sweli.ru, 27% (44 requests) were made to St6-21.vk.com and 4% (7 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source St6-21.vk.com.
Page size can be reduced by 538.1 kB (12%)
4.5 MB
3.9 MB
In fact, the total size of Sweli.ru main page is 4.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. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 83.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 20.6 kB, which is 20% 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 83.7 kB or 80% of the original size.
Potential reduce by 36.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. Sweli images are well optimized though.
Potential reduce by 337.9 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 337.9 kB or 12% of the original size.
Potential reduce by 80.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. Sweli.ru needs all CSS files to be minified and compressed as it can save up to 80.3 kB or 13% of the original size.
Number of requests can be reduced by 102 (65%)
156
54
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 67 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
sweli.ru
539 ms
www.sweli.ru
1214 ms
adsbygoogle.js
160 ms
k2.css
139 ms
styles.css
275 ms
font-awesome.min.css
409 ms
mootools-core.js
544 ms
core.js
409 ms
jquery.min.js
546 ms
jquery-noconflict.js
412 ms
jquery-migrate.min.js
410 ms
k2.js
543 ms
caption.js
544 ms
browser-detect.js
545 ms
mootools-more.js
817 ms
bootstrap.css
848 ms
template.css
683 ms
style1.css
679 ms
responsive.css
681 ms
platform.js
71 ms
gotop.js
274 ms
context.js
939 ms
sh404sefsocial.js
680 ms
common.deg.min.css
1111 ms
meganews.css
855 ms
jquery.hoverIntent.minified.js
853 ms
jquery.omenu.1.0.js
851 ms
widgets.js
92 ms
show_ads_impl.js
243 ms
gotop.js
680 ms
openapi.318ba3d5a50b8d6990cb0284cb0e0963.js
300 ms
openapi.318ba3d5a50b8d6990cb0284cb0e0963.js
251 ms
aci.js
838 ms
navigation.css
139 ms
webfont.js
84 ms
vt_logo_style1.png
373 ms
br.png
174 ms
1-4.jpg
174 ms
1-2.jpg
173 ms
1-3.jpg
174 ms
1-1.jpg
268 ms
3-4.jpg
368 ms
3-2.jpg
370 ms
3-3.jpg
372 ms
3-1.jpg
371 ms
2-4.jpg
427 ms
2-2.jpg
455 ms
2-3.jpg
456 ms
2-1.jpg
458 ms
4-4.jpg
457 ms
4-2.jpg
489 ms
4-3.jpg
529 ms
4-1.jpg
553 ms
0db1de2be923c3b4164afc35f61cb61a_XL.jpg
715 ms
507172a02821b85089d3dcb57ba79989_XL.jpg
711 ms
9217346f41a5b7e8e45bd1d2bf97a850_XL.jpg
714 ms
30033458e7237f5676a81459cd1e537b_XL.jpg
737 ms
e791ab626e6785062374d45b25cc6e7f_XL.jpg
820 ms
c085772a56cb0ee61878d6b4d0081774_XL.jpg
823 ms
att.png
830 ms
all.js
60 ms
vt_logo_style1.png
792 ms
zrt_lookup.html
73 ms
ads
162 ms
all.js
1005 ms
css
110 ms
all.js
54 ms
1.jpg
719 ms
4.jpg
879 ms
2.jpg
844 ms
8.jpg
848 ms
3.jpg
854 ms
line_best.png
853 ms
pl1.png
854 ms
line_gray.jpg
979 ms
yell.png
900 ms
icon2.jpg
907 ms
upload.gif
136 ms
widget_community.php
405 ms
hit
573 ms
watch.js
6 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
99 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
64 ms
fastbutton
61 ms
arrows4.png
739 ms
stick.png
739 ms
like.php
210 ms
settings
112 ms
postmessageRelay
73 ms
developers.google.com
358 ms
544727282-postmessagerelay.js
41 ms
rpc:shindig_random.js
10 ms
button.856debeac157d9669cf51e73a08fbc93.js
35 ms
75yG2MucyVP.js
107 ms
cb=gapi.loaded_0
33 ms
FEppCFCt76d.png
94 ms
embeds
102 ms
loader_nav21098907335_3.js
464 ms
fonts_cnt.c7a76efe.css
1130 ms
lite.93f44416.css
827 ms
lang3_2.js
481 ms
polyfills.c3a1b892.js
825 ms
vkui.388c7a16.css
916 ms
xdm.js
756 ms
ui_common.54e472db.css
848 ms
react.6a15a5cc.js
1032 ms
vkcom-kit.46f7449b.css
1041 ms
vkcom-kit.83b486d3.js
1201 ms
vkcom-kit-icons.780e6c65.js
1101 ms
vkui.55891411.js
1219 ms
architecture-mobx.b1015542.js
1199 ms
state-management.94ab436a.js
1200 ms
audioplayer-lib.93b52d88.css
1206 ms
audioplayer-lib.3321ac20.js
1301 ms
common.e1d31bcf.js
1962 ms
7f463667.2f09ffd3.js
1242 ms
ui_common.b1037836.css
1242 ms
ui_common.cea23e66.js
1288 ms
audioplayer.7787a5d3.css
1304 ms
audioplayer.35efc358.js
1328 ms
widget_community.4978d481.css
1320 ms
5441c5ed.4aafa0df.js
1389 ms
aa3c5e05.1a400e87.js
1393 ms
likes.33883160.css
1390 ms
likes.ad9fb1a1.js
1405 ms
vkcom-kit.3d97e67b.css
1424 ms
vkcom-kit.7af88850.js
1504 ms
react.84cfd9aa.js
1502 ms
vkui.177fea38.js
1638 ms
vkcom-kit-icons.172a0099.js
1489 ms
architecture-mobx.d853b516.js
1526 ms
audioplayer-lib.85b39ca5.css
1567 ms
audioplayer-lib.67144f68.js
1678 ms
state-management.e5a289bd.js
1601 ms
c3d11fba.475e3ac7.js
1616 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ru.html
75 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
620 ms
jquery.min.js
616 ms
community.be2fc20a.css
899 ms
base.ec2ae8ae.css
885 ms
0fc69f32.aea48755.js
892 ms
e7eaa3a9.0425872f.js
890 ms
57703e15.ed6fd4c4.js
832 ms
edb6ffde.69277bd5.js
1223 ms
community.640f3bc9.js
760 ms
suggest.js
127 ms
opensearch.js
199 ms
yandex-hint-rb.png
238 ms
9obIb-nw888CuHgdE0bxy-9qD7RnXQzZOoSKZav9mSM7aFp5fRuA8fARyTDsqnQYl6bg6w.jpg
471 ms
QulWsGFAn5k.png
620 ms
daSjWtnfc_tqobocBLMrDaHohQh_bdpfPPGOJpYNu5_8qDNKIt02PUkpTZ2680caBqb8awKbj0AXV7WLy8VKhC26.jpg
543 ms
eVGFkVKBq8lHNnxm9TX3ogY-qIJAPH0i8OBkFI86MwJkNCpJRaVvRwr3D7WuZWqpcCQWlI1I.jpg
343 ms
jja7i0VjeZ34gtb_0V4tvEaWpTdKMRsx_y1X_KwOtf9zyqFnyuS43bnkk68MS4uu8q6WweMM.jpg
448 ms
NgHm-VXIwXmqdDGW6qTGKqg08BQ9cvphbuEjL1SeB3QpTgmu5knRKw1ZQenN6EwP_aC6PbVx.jpg
546 ms
tKB_4Z89DZX9yclUylOFbfkBv-b25Rjlbz8_8vf1BDVn1Vp44JqXUTlnXZeWCKyMyFrCfK7R.jpg
546 ms
ID6AXQyA3EczqDrDipWQnx1ql7nhtLseAo7-uOQi7JleBuYnAyJVjp_s-fBSGJllYJ3apJR32SMqzBNgRotWc5Ij.jpg
518 ms
FVI-8XxKcvJBWSlzGuIGOtMoWArOmr_a3cbq6pmNkSqYfyY_q30uK1a9vm1siQ1ZsE8UXpJW0ANh8EYJo8NfTneE.jpg
539 ms
Bmw53-yS7FZkQ6LdA7_4R6skO7gX2V1q4J2MnmR_s20Lr111rSO8BqWgaj2ypAjOyfMXcIGGoRDEOZpQFVRxs4TK.jpg
545 ms
vdLmrpPWvDv7vF0Qnyw2b0_AXRRsULWnDuELGcN6_ztpAFJCsj_Eze2VZIw_T93l7KoZKUvC0SZ0It6hJLHzdeLb.jpg
448 ms
Blr9F5CCDAILJc057kc7zTjhsPycaq3THYhpaSfU61BGI8taLHOdNVGIqMmPdoiG3zLSt96v2kK0u4OaOA-FWhiX.jpg
473 ms
s-aNK9rudGeWPZTTNnENXWjpMgNCJkJkoqMOuB9-4M2inreGl1pNRxy2RS5VH35tgbPxGdRJhO0wvuWwZkizi3lM.jpg
525 ms
or4JxvxEqdLek_N7TrJhlzI6VZFWTvMtA39bB8b45ls-6nkFbWjsa_sh-7_OkJkgIyZzI8A1.jpg
341 ms
upload.gif
88 ms
sweli.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
Image elements do not have [alt] attributes
Links do not have a discernible name
sweli.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
Issues were logged in the Issues panel in Chrome Devtools
sweli.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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweli.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 Sweli.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.
sweli.ru
Open Graph description is not detected on the main page of Sweli. 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: