4 sec in total
380 ms
3.5 sec
167 ms
Click here to check amazing Invitro content for Russia. Otherwise, check out these important facts you probably never knew about invitro.ru
Ищете где можно сдать анализы? Более 4000 видов исследований: анализы крови, мочи, ПЦР, инфекции, гормоны, ВИЧ и другие. Около 1900 офисов ИНВИТРО в столице и других городах. Лабораторная диагностика
Visit invitro.ruWe analyzed Invitro.ru page load time and found that the first response time was 380 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
invitro.ru performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value13.5 s
0/100
25%
Value18.4 s
0/100
10%
Value10,370 ms
0/100
30%
Value0.209
59/100
15%
Value40.9 s
0/100
10%
380 ms
817 ms
260 ms
395 ms
394 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 94% of them (60 requests) were addressed to the original Invitro.ru, 3% (2 requests) were made to Ssl.google-analytics.com and 2% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Invitro.ru.
Page size can be reduced by 397.1 kB (71%)
560.0 kB
162.9 kB
In fact, the total size of Invitro.ru main page is 560.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 367.6 kB which makes up the majority of the site volume.
Potential reduce by 88.4 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 88.4 kB or 83% of the original size.
Potential reduce by 7.4 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. Obviously, Invitro needs image optimization as it can save up to 7.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 264.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 264.1 kB or 72% of the original size.
Potential reduce by 37.2 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. Invitro.ru needs all CSS files to be minified and compressed as it can save up to 37.2 kB or 78% of the original size.
Number of requests can be reduced by 50 (82%)
61
11
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Invitro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
invitro.ru
380 ms
www.invitro.ru
817 ms
core.css
260 ms
style.css
395 ms
style.css
394 ms
style.css
396 ms
style.css
397 ms
style.css
397 ms
style.css
397 ms
style.css
524 ms
style.css
521 ms
style.css
522 ms
style.css
525 ms
style.css
526 ms
styles.css
525 ms
template_styles.css
651 ms
core.js
1066 ms
core_ajax.js
786 ms
session.js
654 ms
jquery.min.js
1073 ms
jquery.cookie.js
657 ms
google-maps-cust.js
781 ms
yandex-maps-cust.js
794 ms
script.js
794 ms
script.js
912 ms
script.js
916 ms
script.js
951 ms
highslide.js
1238 ms
region-menu.js
1088 ms
jquery.smartbanner.css
1070 ms
jquery.smartbanner2.js
1105 ms
wz_tooltip.js
1371 ms
jquery.hoverscroll.js
1224 ms
jquery.hoverscroll.css
1221 ms
script.js
1107 ms
ga.js
99 ms
opacity.png
158 ms
icq-img.gif
229 ms
logo_%20new%20309x63.jpg
314 ms
feed-icon-16x16.gif
160 ms
lk-center.png
158 ms
lk-left.png
236 ms
lk-right.png
284 ms
__utm.gif
34 ms
top-button-orange.png
174 ms
top-button.png
175 ms
top-button-ray.png
177 ms
lupa.png
230 ms
promo-zaglushka15.jpg
247 ms
question.gif
273 ms
whitelink_l.png
274 ms
whitelink_r.png
274 ms
icons-sprite.png
276 ms
watch.js
49 ms
phone.d8c20.2038.async.js
957 ms
geocity.php
314 ms
getregions.php
354 ms
getregions.php
339 ms
close.gif
131 ms
round-link-l.gif
130 ms
round-link-r.gif
133 ms
ua-flag.gif
133 ms
by-flag.gif
131 ms
kz-flag.gif
259 ms
invitro.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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
invitro.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
invitro.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Invitro.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 Invitro.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
invitro.ru
Open Graph description is not detected on the main page of Invitro. 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: