7.9 sec in total
1.3 sec
6.4 sec
241 ms
Visit ottobock.ru now to see the best up-to-date Ottobock content for Russia and also check out these interesting facts you probably never knew about ottobock.ru
Добро пожаловать на официальный сайт компании Ottobock в России
Visit ottobock.ruWe analyzed Ottobock.ru page load time and found that the first response time was 1.3 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ottobock.ru performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value11.5 s
0/100
25%
Value11.7 s
4/100
10%
Value3,820 ms
1/100
30%
Value0.138
79/100
15%
Value15.9 s
6/100
10%
1279 ms
2555 ms
313 ms
723 ms
26 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 48% of them (19 requests) were addressed to the original Ottobock.ru, 48% (19 requests) were made to Media.ottobock.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ottobock.ru.
Page size can be reduced by 616.5 kB (38%)
1.6 MB
1.0 MB
In fact, the total size of Ottobock.ru main page is 1.6 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. 35% of websites need less resources to load. Images take 866.5 kB which makes up the majority of the site volume.
Potential reduce by 53.5 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 53.5 kB or 82% of the original size.
Potential reduce by 27.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. Ottobock images are well optimized though.
Potential reduce by 430.8 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 430.8 kB or 74% of the original size.
Potential reduce by 105.0 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. Ottobock.ru needs all CSS files to be minified and compressed as it can save up to 105.0 kB or 82% of the original size.
We found no issues to fix!
38
38
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ottobock. According to our analytics all requests are already optimized.
ottobock.ru
1279 ms
www.ottobock.ru
2555 ms
style.css
313 ms
script_js.js
723 ms
analytics.js
26 ms
icon_facebook-2.png
1151 ms
icon_youtube-2.png
1142 ms
icon_googleplus.png
1144 ms
icon_twitter-2.png
1151 ms
c-leg_user_16_9_stage_thumbnail-2.jpg
1151 ms
genu_arexa_user_16_9_stage_thumbnail.jpg
1153 ms
avantgarde_user_16_9_stage_thumbnail.jpg
1345 ms
30527-beratung_0317_169-4c_16_9_stage_thumbnail.jpg
1353 ms
icon_facebook_footer.png
1355 ms
icon_youtube_footer.png
1365 ms
icon_googleplus_footer.png
1367 ms
icon_twitter_footer.png
1366 ms
logo_svg.svg
206 ms
icons_ltr_svg.svg
310 ms
icon_vk.png
215 ms
icon_instagram.png
220 ms
circles_left.png
220 ms
%D0%BF%D0%B0%D1%80%D0%B0%D0%BB%D0%B8%D0%BC%D0%BF%D0%B8%D0%B9%D1%81%D0%BA%D0%B8%D0%B9-%D1%81%D0%BF%D0%BE%D1%80%D1%82_16_9_stage_thumbnail.jpg
497 ms
icon_vk_footer.png
497 ms
collect
14 ms
update_js.js
106 ms
headquarters_ottobock_16_9_teaser_threecolumn.jpg
1191 ms
employees_ottobock_16_9_teaser_threecolumn-5.jpg
1199 ms
dialog-epaper_16_9_teaser_threecolumn.jpg
1198 ms
c-leg_user_24_9_stage-2.jpg
1513 ms
genu_arexa_user_24_9_stage.jpg
1555 ms
avantgarde_user_24_9_stage.jpg
1543 ms
30527-beratung_0317_169-4c_24_9_stage.jpg
1724 ms
fitness_day_2015_16_9_teaser_threecolumn.jpg
308 ms
%D0%B2%D1%8B%D1%81%D1%82%D0%B0%D0%B2%D0%BA%D0%B0-%C2%AB%D0%B8%D0%BD%D1%82%D0%B5%D1%80%D0%B0%D1%86%D0%B8%D1%8F.-%D0%B6%D0%B8%D0%B7%D0%BD%D1%8C.-%D0%BE%D0%B1%D1%89%D0%B5%D1%81%D1%82%D0%B2%D0%BE%C2%BB_16_9_teaser_threecolumn.jpg
306 ms
0_specialists_catalogues_16_9_teaser_threecolumn.jpg
208 ms
online_shops_16_9_teaser_threecolumn.jpg
208 ms
partners_16_9_teaser_threecolumn.jpg
214 ms
social_responsibility_16_9_teaser_threecolumn.jpg
421 ms
%D0%BF%D0%B0%D1%80%D0%B0%D0%BB%D0%B8%D0%BC%D0%BF%D0%B8%D0%B9%D1%81%D0%BA%D0%B8%D0%B9-%D1%81%D0%BF%D0%BE%D1%80%D1%82_24_9_stage.jpg
739 ms
ottobock.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-*] attributes do not match their roles
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ottobock.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
ottobock.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ottobock.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 Ottobock.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.
ottobock.ru
Open Graph description is not detected on the main page of Ottobock. 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: