5.7 sec in total
491 ms
5 sec
196 ms
Click here to check amazing Medcom content for Russia. Otherwise, check out these important facts you probably never knew about medcom.ru
Продажа оборудования экстренной помощи Медплант, проктологического оборудования Кварц
Visit medcom.ruWe analyzed Medcom.ru page load time and found that the first response time was 491 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
medcom.ru performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value9.3 s
1/100
25%
Value48.3 s
0/100
10%
Value5,240 ms
0/100
30%
Value0.034
100/100
15%
Value44.2 s
0/100
10%
491 ms
638 ms
996 ms
123 ms
359 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 47% of them (68 requests) were addressed to the original Medcom.ru, 29% (43 requests) were made to St6-21.vk.com and 6% (9 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 443.0 kB (15%)
3.0 MB
2.6 MB
In fact, the total size of Medcom.ru main page is 3.0 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. 55% of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 36.1 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 11.5 kB, which is 25% 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 36.1 kB or 77% of the original size.
Potential reduce by 12.1 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. Medcom images are well optimized though.
Potential reduce by 322.1 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 322.1 kB or 14% of the original size.
Potential reduce by 72.6 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. Medcom.ru needs all CSS files to be minified and compressed as it can save up to 72.6 kB or 14% of the original size.
Number of requests can be reduced by 99 (70%)
141
42
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medcom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
medcom.ru
491 ms
medcom.ru
638 ms
context.js
996 ms
style.css
123 ms
main.css
359 ms
dropdowntabs.js
361 ms
style.css
362 ms
style.css
362 ms
style.css
467 ms
style.css
469 ms
style.css
478 ms
style.css
478 ms
style.css
478 ms
core.min.js
722 ms
protobuf.min.js
699 ms
model.min.js
585 ms
rest.client.min.js
595 ms
pull.client.min.js
602 ms
jquery-1.12.4.min.js
720 ms
script.js
702 ms
script.js
713 ms
script.js
721 ms
jquery.cookie.js
813 ms
script.js
818 ms
zp.js
670 ms
tools.css
477 ms
blocks.css
484 ms
base.css
485 ms
slaed.css
486 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
221 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
240 ms
ba.js
285 ms
buttom.gif
372 ms
headbg.png
120 ms
theader.jpg
121 ms
e0j1rhzq80z0tno9ark288rhtil7op0p.gif
239 ms
medcom.png
122 ms
tabmenu.png
119 ms
spacer.png
117 ms
homebtn.png
232 ms
menubrd.png
238 ms
searchform.png
239 ms
ub0degv2mzm8vrqpqy0tc9o521k0jp0b.jpg
244 ms
oc7t0u262tjdq5gfnqbg87vr8z3x1x0n.png
243 ms
l3wrf4xzouwfxjmlvflapp5l7t3b8ynx.jpg
352 ms
i5jjzvauwguujv8j40l40r58lqovmkf1.jpg
361 ms
2f4747tmycbl80bjusnaxy2zb412tf9e.jpg
365 ms
nfkxu1u1jsa4p3bw0vazj63m2by06omc.png
362 ms
suhkro9hqptk4kv3cjeu4eg7w2wsch9i.jpg
376 ms
vfatlh39k1vky8ieihkjqsecno8my2vf.png
371 ms
7wc6k4unpnnxwvrj54530b25jcw2tlut.jpg
471 ms
i42zisunav4im00cgz2784f39y1ar054.jpg
484 ms
spacer.png
468 ms
menu_links.png
468 ms
smb_left.png
478 ms
smb_right.png
482 ms
smb_left_top.png
573 ms
smb_right_top.png
586 ms
blockright_head.png
585 ms
blockleft_t2.png
586 ms
blockleft_t2_h2.png
609 ms
upload.gif
112 ms
blockleft_t2_h1.png
602 ms
aci.js
519 ms
widget_community.php
304 ms
heading_left.png
670 ms
smb_bottom.png
683 ms
smb_right_bottom.png
686 ms
smb_left_bottom.png
689 ms
footerbg.png
697 ms
footbox_brd.png
702 ms
footmenu_bg.png
785 ms
watch.js
2 ms
version.js
222 ms
widget_community.php
391 ms
footmenu_left.png
718 ms
toptop.png
721 ms
footlogo.png
723 ms
footinfo_brd.png
730 ms
modal_close.png
735 ms
loader_nav2101149047_3.js
396 ms
fonts_cnt.c7a76efe.css
924 ms
lite.ca486089.css
645 ms
lang3_2.js
460 ms
polyfills.097fc8eb.js
597 ms
vkui.43318ab6.css
679 ms
xdm.js
506 ms
ui_common.5f35f406.css
593 ms
react.6a15a5cc.js
779 ms
vkui.a2e1063b.js
968 ms
vkcom-kit.ec0885e5.css
800 ms
vkcom-kit.5f538c81.js
987 ms
vkcom-kit-icons.7d6c55ae.js
875 ms
state-management.d517d148.js
889 ms
architecture-mobx.906cf75b.js
901 ms
audioplayer-lib.93b52d88.css
965 ms
audioplayer-lib.8f87c867.js
1088 ms
common.122262c3.js
1682 ms
ui_common.b1037836.css
1001 ms
ui_common.3cee9418.js
1059 ms
audioplayer.7787a5d3.css
1049 ms
audioplayer.df8804ec.js
1067 ms
widget_community.4978d481.css
1083 ms
5441c5ed.4aafa0df.js
1146 ms
aa3c5e05.9cee08bd.js
1150 ms
likes.33883160.css
1148 ms
likes.a07d934f.js
1171 ms
react.84cfd9aa.js
1200 ms
vkcom-kit.d9ac7596.css
1241 ms
vkcom-kit.e87a9984.js
1248 ms
vkui.7bcdeecd.js
1411 ms
vkcom-kit-icons.e6e6c43d.js
1260 ms
audioplayer-lib.85b39ca5.css
1286 ms
audioplayer-lib.199ceacc.js
1417 ms
architecture-mobx.d853b516.js
1344 ms
state-management.e5a289bd.js
1347 ms
c3d11fba.296f7859.js
1376 ms
0fc69f32.fefb81c0.js
1440 ms
bx_stat
190 ms
buttom.gif
526 ms
cycounter
555 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
332 ms
community.be2fc20a.css
934 ms
base.474fcd2c.css
888 ms
e7eaa3a9.14a1bc53.js
917 ms
57703e15.6ed459e0.js
874 ms
edb6ffde.ddbbc7d2.js
1282 ms
community.4a273bbc.js
757 ms
PsxqTvTsJ_OqK9DuHMmBDPkdDzQiNV9N-nOugh702q8LevUJM8cI2mxHCwdCzMZlLRdPyMt3NQc3ARB0dZXJPLai.jpg
346 ms
f09f94a5.png
111 ms
QulWsGFAn5k.png
589 ms
UIAsQ7dgDnu0_RBHKiUkRA5KQt8QFlNe-vFXYZlR2WUdrnqK5pgAu8YbpjnADijnXQ2xz1v7plrYDZfFn6E8Y8b9.jpg
473 ms
eckJ4Xf4B7dqsdgfcIJrvx8muT58UbzwhpdndzN1F-yjVR8cZ5yNlbC1Qw20Epbx3OV-yE5UXsMqAlKFBgFZmPZD.jpg
443 ms
8wYZQFM9plK8wG9FpuG0GeQCEoVRnW5D__kXonRpvAI2mMKew0jf9EYZMVVpJkneh9VsX6OHlvRc91auEPF_wefj.jpg
345 ms
OCd6v3eS16dbvF8OO1qvhAmnOicBDwIAKe-2NwJG6XV5MJqV-uxaidIBImmX1uW5DRXwl4Ue.jpg
480 ms
upload.gif
89 ms
I3aFFnTvPBYkZJH9b8gfZ1dkd3b1UbtoPW3qZOjB8-DsGmvYG4ipLhOcARQLZSKQjm7neG6FlsoOLJL-LEQBP_TS.jpg
486 ms
Phhp3pwksAJllzG9oCxG309ENKwAU6tHPWfMqD1iw-z83podK9xlDDnGk74XU_2TL777G9DglppOKbcRSBfsTo6P.jpg
510 ms
rEeant6NeY3vlSPrQXlbznZX5x_C9IngbIa46Izj8-dRAR5naRPamLl7dVPb6fLKF1nXOqKRvf9HcwJ_HE-gID6i.jpg
511 ms
K-MWicJWodQwVkX4aGcpRD9-SoZTNs832bX6UFyNX5U7NAl6BhTfKAsvyBhhVFW3vGEfsuklJRvd_lunArFTkAmg.jpg
457 ms
Kphyf3vJL28qcOqj7ID3uxjHTOnWMxy5A8hbYSetdMnuL5hxrSL11tMcf3RtELonBkJQK_mBeqNZG96yc8_zA8RC.jpg
508 ms
56MdlxLJTGrm7xWqiD1_xwMFhLETnZ8wCMws90hBhrzftSMVK0jb_QXnjYOOVY8CaPgMg7yxj1slwn1SNU5qwYf0.jpg
468 ms
cVZzW5ygafW6ck3zjVQGdDnDnii93Q0hcctM49GIetls5djLe-GOn_Ka2D60KrEMIOYyOHHS.jpg
500 ms
55XLew7RTjk.jpg
511 ms
impression.html
136 ms
extra.js
262 ms
medcom.ru accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
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
medcom.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
medcom.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Medcom.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 Medcom.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.
medcom.ru
Open Graph description is not detected on the main page of Medcom. 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: