5.5 sec in total
454 ms
4.8 sec
178 ms
Click here to check amazing Upacom content for Russia. Otherwise, check out these important facts you probably never knew about upacom.ru
ЮПаКом - официальный поставщик медицинского оборудования и расходных материалов в РФ
Visit upacom.ruWe analyzed Upacom.ru page load time and found that the first response time was 454 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
upacom.ru performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value21.2 s
0/100
25%
Value17.6 s
0/100
10%
Value2,710 ms
3/100
30%
Value0.029
100/100
15%
Value28.9 s
0/100
10%
454 ms
1289 ms
39 ms
33 ms
232 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 79% of them (92 requests) were addressed to the original Upacom.ru, 10% (12 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Upacom.ru.
Page size can be reduced by 5.7 MB (54%)
10.5 MB
4.8 MB
In fact, the total size of Upacom.ru main page is 10.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. Only a small number of websites need less resources to load. Images take 9.1 MB which makes up the majority of the site volume.
Potential reduce by 779.3 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 527.9 kB, which is 65% 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 779.3 kB or 96% of the original size.
Potential reduce by 4.9 MB
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, Upacom needs image optimization as it can save up to 4.9 MB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 13.9 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. Upacom.ru has all CSS files already compressed.
Number of requests can be reduced by 48 (49%)
98
50
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Upacom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
upacom.ru
454 ms
upacom.ru
1289 ms
css
39 ms
animate.min.css
33 ms
uikit.min.css
232 ms
bootstrap.min.css
431 ms
owl.carousel.min.css
325 ms
photoswipe.css
329 ms
default-skin.css
330 ms
select2.min.css
336 ms
bootstrap-tagsinput.css
342 ms
style.css
648 ms
ouislider_3.css
446 ms
fontawesome.min.css
549 ms
all.min.css
564 ms
smart_wizard_all.css
453 ms
bootstrap-select.min.css
535 ms
upacom.css
555 ms
CACOYcVd5i
582 ms
js
81 ms
jquery.js
695 ms
yii.js
533 ms
bootstrap.bundle.min.js
560 ms
owl.carousel.min.js
561 ms
nouislider.min.js
694 ms
photoswipe.min.js
713 ms
photoswipe-ui-default.min.js
713 ms
select2.min.js
714 ms
bootstrap-tagsinput.js
713 ms
uikit.min.js
840 ms
uikit-icons.min.js
836 ms
jquery.mask.js
836 ms
autoNumeric.min.js
837 ms
jquery.easing.min.js
839 ms
jquery.smartWizard.js
838 ms
wNumb.js
839 ms
js.cookie.min.js
894 ms
bootstrap-select.min.js
999 ms
defaults-ru_RU.js
999 ms
number.js
999 ms
main.js
1169 ms
header.js
1170 ms
scripts.js
1040 ms
svg4everybody.min.js
963 ms
jquery.pjax.js
959 ms
yii.validation.js
958 ms
yii.activeForm.js
1053 ms
css2
22 ms
tag.js
985 ms
120.svg
697 ms
logo.svg
699 ms
unicare.jpg
956 ms
mobile_unicare.jpg
861 ms
telegram.jpg
970 ms
mobile_telegram.jpg
958 ms
durr1.jpg
1134 ms
durr1.jpg
780 ms
mobile_durr1.jpg
1058 ms
%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80.jpg
1132 ms
mobile_%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80.jpg
1131 ms
3banosn.jpg
1215 ms
CACOYcVd5i
257 ms
init.js
1108 ms
mobile_3banosn.jpg
1017 ms
5513f3beb5799.jpg
999 ms
621d86c00fcc0140556531e4265a191b.jpg
1080 ms
55114a711fdf4.jpg
1080 ms
551997d153ec4.jpg
1079 ms
55116802e9195.png
1080 ms
5514029181cb3.jpg
957 ms
CACOYcVd5i
798 ms
55115d5b12d3a.gif
1013 ms
fa2202effe332553fa66ca1859a021c3.png
1014 ms
551402b657e15.jpg
1035 ms
551924d2094a9.jpg
1045 ms
342c03f98c95c34d93915abbe7cf3e0b.jpg
1052 ms
fa-brands-400.woff
1052 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
161 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
162 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
266 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
332 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
333 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
335 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
335 ms
fa-light-300.woff
989 ms
fa-regular-400.woff
985 ms
fa-solid-900.woff
983 ms
5741ddb6365c2df4c61772982fb4ad72.png
1086 ms
a124d21989872ea5c2cae3ad5ccafa10.jpg
918 ms
MsJRFkyOI7y9CsmZMmrYpX37ucpim9e55XHw5DT8XfIvoJDmrlUy.png
1060 ms
dhPh44KwhVKBzzRNoPjVt3r8TY0cAckbg57hPiL1HZdBVKIEEa7K.png
1134 ms
bbPFHIvA8h5a0vwJVGgk9exK9F7nGx7HlihkyqkVQAWoA5nW5vkk.jpg
919 ms
KxClC-zZzk1lLVhbMZSBFoEaj8nDfA0DtZtR5ZvsrqmMM9N6_43Z.jpg
919 ms
QqLz_z_HWg6ntL-1DjnNFkIWrA8kSwNFQNhjWYQHALPUAPg4Lbl2.jpg
929 ms
8a6ea21310b6bfc3ddcbef8930403d8b.jpg
841 ms
RqrIgRmsb6lkGmvuMTFNcIk5FWjakPZU368MB0X3Rtl1E0ccw2yl.png
1197 ms
B4oxkcPG4CemO1De_moba3jkeUFGG0jbjSAEB3dxiCBWZAUc5Y8u.jpeg
941 ms
0008426.png
840 ms
mobile_0008426.png
790 ms
a705ddd8ed46c05093c8f6a9506dd66f.jpg
793 ms
9695cae80042f06df17f75c469cb9c7d.jpg
792 ms
7195d2d36926bf87de574c5b2ec3faa8.jpg
794 ms
c12a74fdde211e3a6e4fcd806086fd1a.jpg
708 ms
mir.png
765 ms
visa.png
766 ms
master_card.png
766 ms
map.png
963 ms
sprite.svg
753 ms
advert.gif
682 ms
sync_cookie_image_decide
186 ms
bundle_ru_RU.js
232 ms
1
139 ms
upacom.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
upacom.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
upacom.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
Tap targets are not sized appropriately
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Upacom.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 Upacom.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.
upacom.ru
Open Graph description is not detected on the main page of Upacom. 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: