Tools & Wizards About Us
doctorhiller.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 0

    Best Practices

  • 89

    SEO

    Google-friendlier than
    66% of websites

doctorhiller.com

Клиника профессора Якова Гиллера — Клиника швейцарского профессора Якова Гиллера

Page Load Speed

4.9 sec in total

First Response

515 ms

Resources Loaded

3.8 sec

Page Rendered

586 ms

doctorhiller.com screenshot

About Website

Click here to check amazing Doctorhiller content for Russia. Otherwise, check out these important facts you probably never knew about doctorhiller.com

Центр лечения наркомании и алкоголизма швейцарского профессора Якова Гиллера предлагает действенное лечение зависимостей по уникальной методике.

Visit doctorhiller.com

Key Findings

We analyzed Doctorhiller.com page load time and found that the first response time was 515 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

doctorhiller.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.303

39/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

doctorhiller.com

515 ms

wp-emoji-release.min.js

215 ms

jquery.js

258 ms

autoptimize_6ccd40045c10e36cd9c62834594cb54a.js

964 ms

watch.js

50 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 96% of them (49 requests) were addressed to the original Doctorhiller.com, 2% (1 request) were made to Mc.yandex.ru and 2% (1 request) were made to Code.jivosite.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Doctorhiller.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (41%)

Content Size

3.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Doctorhiller.com main page is 3.2 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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 139.9 kB

  • Original 172.4 kB
  • After minification 172.0 kB
  • After compression 32.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 139.9 kB or 81% of the original size.

Image Optimization

-20%

Potential reduce by 374.6 kB

  • Original 1.8 MB
  • After minification 1.5 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, Doctorhiller needs image optimization as it can save up to 374.6 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 783.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 311.5 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 783.4 kB or 72% of the original size.

CSS Optimization

-19%

Potential reduce by 20.5 kB

  • Original 107.3 kB
  • After minification 107.3 kB
  • After compression 86.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. Doctorhiller.com needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

doctorhiller.com

doctorhiller.com

515 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

215 ms

jquery.js

jquery.js

258 ms

autoptimize_6ccd40045c10e36cd9c62834594cb54a.js

autoptimize_6ccd40045c10e36cd9c62834594cb54a.js

964 ms

watch.js

watch.js

50 ms

bffon.png

bffon.png

240 ms

ru.png

ru.png

118 ms

en.png

en.png

234 ms

de.png

de.png

235 ms

logo_new_300-1.png

logo_new_300-1.png

356 ms

%D1%85%D0%B8%D0%BB%D0%BB%D0%B5%D1%80_%D0%BB%D0%BE%D0%B3%D0%BE_76.png

%D1%85%D0%B8%D0%BB%D0%BB%D0%B5%D1%80_%D0%BB%D0%BE%D0%B3%D0%BE_76.png

2297 ms

baner-right-2.png

baner-right-2.png

583 ms

reviews-button.jpg

reviews-button.jpg

351 ms

ypages.png

ypages.png

358 ms

Uso.png

Uso.png

468 ms

Cataloxy.png

Cataloxy.png

475 ms

Doctor.png

Doctor.png

478 ms

YP.png

YP.png

585 ms

Medihost.png

Medihost.png

595 ms

logo_BW_FOOTER.png

logo_BW_FOOTER.png

598 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%803.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%803.png

1050 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8006.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8006.png

1048 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80001.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80001.png

1069 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8001.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8001.png

1075 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8005.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8005.png

1044 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80002.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80002.png

1284 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80003.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80003.png

1173 ms

icomoon-the7-social-icons-16x16.ttf

icomoon-the7-social-icons-16x16.ttf

1123 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

439 ms

style.css

style.css

325 ms

pp-00.php

pp-00.php

414 ms

pp-01.php

pp-01.php

417 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%803-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%803-150x150.png

349 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8006-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8006-150x150.png

356 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80001-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80001-150x150.png

446 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8001-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8001-150x150.png

445 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8005-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%8005-150x150.png

443 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80002-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80002-150x150.png

467 ms

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80003-150x150.png

%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80003-150x150.png

476 ms

1-1.png

1-1.png

547 ms

2.png

2.png

549 ms

3-1.png

3-1.png

552 ms

4.png

4.png

692 ms

5.png

5.png

583 ms

img.png

img.png

664 ms

7.png

7.png

665 ms

8.png

8.png

790 ms

font-awesome.css

font-awesome.css

482 ms

main.min.css

main.min.css

247 ms

post-type.css

post-type.css

122 ms

V1TvmzXPdN

V1TvmzXPdN

357 ms

Accessibility Review

doctorhiller.com accessibility score

57

Accessibility Issues

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

doctorhiller.com SEO score

89

Search Engine Optimization Advices

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

Social Sharing Optimization

doctorhiller.com

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