Tools & Wizards About Us
preparatnik.ru screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

preparatnik.ru

Инструкции по применению препаратов

Page Load Speed

3.7 sec in total

First Response

553 ms

Resources Loaded

2.9 sec

Page Rendered

197 ms

preparatnik.ru screenshot

About Website

Visit preparatnik.ru now to see the best up-to-date Preparatnik content for Russia and also check out these interesting facts you probably never knew about preparatnik.ru

Большое разнообразие препаратов требует от пациента разбираться в инструкциях по применению к ним. На сайте Preparatnik.ru вы найдете полные аннотации к лекарствам с отзывами.

Visit preparatnik.ru

Key Findings

We analyzed Preparatnik.ru page load time and found that the first response time was 553 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

preparatnik.ru performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

preparatnik.ru

553 ms

index.php

405 ms

style.css

245 ms

engine.css

246 ms

nodisplay.css

245 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 71% of them (34 requests) were addressed to the original Preparatnik.ru, 8% (4 requests) were made to Site.yandex.net and 6% (3 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (811 ms) belongs to the original domain Preparatnik.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.6 kB (4%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Preparatnik.ru main page is 1.1 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.4 kB

  • Original 44.5 kB
  • After minification 41.0 kB
  • After compression 9.2 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 35.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 445 B

  • Original 1.0 MB
  • After minification 1.0 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. Preparatnik images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 4.0 kB

  • Original 80.5 kB
  • After minification 80.5 kB
  • After compression 76.6 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.

CSS Optimization

-20%

Potential reduce by 1.9 kB

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 7.5 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. Preparatnik.ru needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (17%)

Requests Now

42

After Optimization

35

  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Preparatnik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

preparatnik.ru

preparatnik.ru

553 ms

index.php

index.php

405 ms

style.css

style.css

245 ms

engine.css

engine.css

246 ms

nodisplay.css

nodisplay.css

245 ms

libs.js

libs.js

255 ms

ga.js

ga.js

10 ms

bg.jpg

bg.jpg

124 ms

watch.js

watch.js

6 ms

top-bg.jpg

top-bg.jpg

365 ms

logo.jpg

logo.jpg

366 ms

doc.png

doc.png

366 ms

item.png

item.png

129 ms

main-bg.png

main-bg.png

240 ms

top-mbg.png

top-mbg.png

254 ms

search-bg.jpg

search-bg.jpg

381 ms

by-disease.jpg

by-disease.jpg

362 ms

by-alphabet.jpg

by-alphabet.jpg

633 ms

new-pop.jpg

new-pop.jpg

485 ms

by-section.jpg

by-section.jpg

487 ms

admin.jpg

admin.jpg

488 ms

autositemap.php

autositemap.php

520 ms

all.js

all.js

749 ms

__utm.gif

__utm.gif

11 ms

left-block-top.jpg

left-block-top.jpg

467 ms

left-block-middle.jpg

left-block-middle.jpg

566 ms

left-block-inside.jpg

left-block-inside.jpg

568 ms

left-block-bottom.jpg

left-block-bottom.jpg

568 ms

letter.jpg

letter.jpg

594 ms

log.jpg

log.jpg

600 ms

pass.jpg

pass.jpg

689 ms

login.jpg

login.jpg

691 ms

conb.png

conb.png

691 ms

more.jpg

more.jpg

716 ms

nav-active.jpg

nav-active.jpg

721 ms

next-prev.jpg

next-prev.jpg

722 ms

bottom-mbg.png

bottom-mbg.png

811 ms

hit

hit

354 ms

lb194246_3.js

lb194246_3.js

527 ms

hit

hit

543 ms

genall.php

genall.php

322 ms

jquery.min.js

jquery.min.js

596 ms

genall.php

genall.php

490 ms

hit

hit

138 ms

suggest.js

suggest.js

376 ms

opensearch.js

opensearch.js

480 ms

search-button.png

search-button.png

124 ms

yandex-hint-rb.png

yandex-hint-rb.png

566 ms

Accessibility Review

preparatnik.ru accessibility score

88

Accessibility Issues

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

Form elements do not have associated labels

Best Practices

preparatnik.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

preparatnik.ru SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

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

preparatnik.ru

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