Tools & Wizards About Us
vidar.ru screenshot

Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

vidar.ru

Издательство ВИДАР, профессиональная медицинская литература. Новости.

Page Load Speed

2.9 sec in total

First Response

708 ms

Resources Loaded

1.7 sec

Page Rendered

581 ms

vidar.ru screenshot

About Website

Click here to check amazing Vidar content for Russia. Otherwise, check out these important facts you probably never knew about vidar.ru

Издательство ВИДАР предлагает широкий спектр медицинской литературы. Заказать и купить литературу по медицине можно на нашем сайте. Электронная библиотека книг по медицине.

Visit vidar.ru

Key Findings

We analyzed Vidar.ru page load time and found that the first response time was 708 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

vidar.ru performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

vidar.ru

708 ms

store.css

257 ms

watch.js

183 ms

Logo_Vidar_200x81.gif

128 ms

medvis-100x100.gif

294 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 80% of them (16 requests) were addressed to the original Vidar.ru, 20% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (854 ms) belongs to the original domain Vidar.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.8 kB (69%)

Content Size

124.3 kB

After Optimization

38.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vidar.ru main page is 124.3 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. Only 5% of websites need less resources to load. Javascripts take 66.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 40.4 kB

  • Original 53.5 kB
  • After minification 51.1 kB
  • After compression 13.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. 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 40.4 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 82 B

  • Original 1.1 kB
  • After minification 1.0 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. Vidar images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 43.1 kB

  • Original 66.9 kB
  • After minification 66.9 kB
  • After compression 23.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 43.1 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 2.2 kB

  • Original 2.8 kB
  • After minification 2.2 kB
  • After compression 634 B

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. Vidar.ru needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 78% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vidar. According to our analytics all requests are already optimized.

Network Requests Diagram

vidar.ru

vidar.ru

708 ms

store.css

store.css

257 ms

watch.js

watch.js

183 ms

Logo_Vidar_200x81.gif

Logo_Vidar_200x81.gif

128 ms

medvis-100x100.gif

medvis-100x100.gif

294 ms

usfd-100x100.gif

usfd-100x100.gif

255 ms

annals_100x100.gif

annals_100x100.gif

399 ms

medimage-100x100.gif

medimage-100x100.gif

421 ms

med_100x100_16.gif

med_100x100_16.gif

572 ms

smallnew.gif

smallnew.gif

293 ms

_VKONT1.PNG

_VKONT1.PNG

377 ms

facebook18.gif

facebook18.gif

418 ms

wp.gif

wp.gif

436 ms

@GetPData.asp

@GetPData.asp

854 ms

@getBooksAd.asp

@getBooksAd.asp

512 ms

watch.js

watch.js

464 ms

Cover_Annaly_PDF_b.gif

Cover_Annaly_PDF_b.gif

256 ms

Cover_Annaly_PDF_b_pv.gif

Cover_Annaly_PDF_b_pv.gif

156 ms

advert.gif

advert.gif

150 ms

1

1

168 ms

Accessibility Review

vidar.ru accessibility score

72

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

vidar.ru best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

vidar.ru SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vidar.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 Vidar.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.

Social Sharing Optimization

vidar.ru

Open Graph description is not detected on the main page of Vidar. 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: