Tools & Wizards About Us
vperemen.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

vperemen.com

Лечение зависимостей в Москве

Page Load Speed

6.7 sec in total

First Response

630 ms

Resources Loaded

5 sec

Page Rendered

1.1 sec

vperemen.com screenshot

About Website

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

Лечение химических зависимостей в Москве - клиника Вита

Visit vperemen.com

Key Findings

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

Performance Metrics

vperemen.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

vperemen.com

630 ms

www.vperemen.com

1109 ms

css2

43 ms

fancybox.css

53 ms

bootstrap-reboot.css

157 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 67% of them (62 requests) were addressed to the original Vperemen.com, 5% (5 requests) were made to Gstatic.com and 4% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Vperemen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 226.6 kB (21%)

Content Size

1.1 MB

After Optimization

878.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vperemen.com 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. 50% of websites need less resources to load. Javascripts take 691.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 91.4 kB

  • Original 112.9 kB
  • After minification 86.8 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 26.1 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 91.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 1.2 kB

  • Original 130.7 kB
  • After minification 129.5 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. Vperemen images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 7.7 kB

  • Original 691.4 kB
  • After minification 689.1 kB
  • After compression 683.7 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

-74%

Potential reduce by 126.2 kB

  • Original 169.6 kB
  • After minification 137.4 kB
  • After compression 43.3 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. Vperemen.com needs all CSS files to be minified and compressed as it can save up to 126.2 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (35%)

Requests Now

85

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vperemen.com

vperemen.com

630 ms

www.vperemen.com

www.vperemen.com

1109 ms

css2

css2

43 ms

fancybox.css

fancybox.css

53 ms

bootstrap-reboot.css

bootstrap-reboot.css

157 ms

bootstrap-grid.css

bootstrap-grid.css

466 ms

style.css

style.css

793 ms

logo.svg

logo.svg

635 ms

doctor.webp

doctor.webp

789 ms

info-1.webp

info-1.webp

790 ms

info-2.webp

info-2.webp

876 ms

876 ms

jquery-3.6.1.min.js

jquery-3.6.1.min.js

30 ms

fancybox.umd.js

fancybox.umd.js

50 ms

api.js

api.js

77 ms

js

js

77 ms

KJVfTG8DvK

KJVfTG8DvK

873 ms

scripts.js

scripts.js

615 ms

personal_marsel.jpg

personal_marsel.jpg

777 ms

personal_guzel.jpg

personal_guzel.jpg

871 ms

epishin-stanislav-min.png

epishin-stanislav-min.png

962 ms

personal_yura.jpg

personal_yura.jpg

1410 ms

img-1.webp

img-1.webp

1254 ms

img-2.webp

img-2.webp

1252 ms

img-3.webp

img-3.webp

1257 ms

img-4.webp

img-4.webp

1709 ms

img-5.webp

img-5.webp

1405 ms

img-6.webp

img-6.webp

1416 ms

sert-1-small.webp

sert-1-small.webp

1410 ms

sert-2-small.webp

sert-2-small.webp

1412 ms

sert-3-small.webp

sert-3-small.webp

2335 ms

sert-4-small.webp

sert-4-small.webp

1566 ms

img-7.webp

img-7.webp

1572 ms

promo-1.webp

promo-1.webp

1567 ms

promo-2.webp

promo-2.webp

1572 ms

ivC9i9cBK9LlFlZRnaZebkq214ZuV3DHFCRUFUYL.webp

ivC9i9cBK9LlFlZRnaZebkq214ZuV3DHFCRUFUYL.webp

1721 ms

n4OjyJQeylsWlSxLPBuhIpn5jHDS26UjpFK6Su2P.webp

n4OjyJQeylsWlSxLPBuhIpn5jHDS26UjpFK6Su2P.webp

1725 ms

JuTZ2Q9eWt9oOWdqmDaGlNtlvArflgjiCxdBdUdl.webp

JuTZ2Q9eWt9oOWdqmDaGlNtlvArflgjiCxdBdUdl.webp

1728 ms

medicine-logo.webp

medicine-logo.webp

1729 ms

oplata-1.svg

oplata-1.svg

2301 ms

oplata-2.svg

oplata-2.svg

1880 ms

oplata-3.svg

oplata-3.svg

1885 ms

support.png

support.png

1887 ms

e690f6dd33c8870d6972.yandex.ru.js

e690f6dd33c8870d6972.yandex.ru.js

739 ms

react-with-dom.min.js

react-with-dom.min.js

980 ms

6e8704ebcb22889362fe.yandex.ru.js

6e8704ebcb22889362fe.yandex.ru.js

1247 ms

b1af1c6c4b43fd3a0457.yandex.ru.js

b1af1c6c4b43fd3a0457.yandex.ru.js

1721 ms

icon-phone.svg

icon-phone.svg

1071 ms

icon-mail.svg

icon-mail.svg

1217 ms

icon-menu.svg

icon-menu.svg

1218 ms

icon-chevron-down.svg

icon-chevron-down.svg

1625 ms

doctor-say-hello.png

doctor-say-hello.png

1222 ms

icon-date.svg

icon-date.svg

1372 ms

stages-bg.svg

stages-bg.svg

1374 ms

icon-diamond.svg

icon-diamond.svg

1377 ms

icon-user-red.svg

icon-user-red.svg

1912 ms

icon-heart-red.svg

icon-heart-red.svg

1913 ms

recaptcha__en.js

recaptcha__en.js

46 ms

tag.js

tag.js

933 ms

icon-wallet-red.svg

icon-wallet-red.svg

1862 ms

icon-diamond-red.svg

icon-diamond-red.svg

1588 ms

icon-book-red.svg

icon-book-red.svg

1620 ms

KJVfTG8DvK

KJVfTG8DvK

677 ms

anchor

anchor

49 ms

icon-truck-red.svg

icon-truck-red.svg

1635 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

12 ms

iEboSLOEGWLfUwE4vWMJoC4GcDs_D5t26QLNgGwKBCM.js

iEboSLOEGWLfUwE4vWMJoC4GcDs_D5t26QLNgGwKBCM.js

65 ms

webworker.js

webworker.js

64 ms

logo_48.png

logo_48.png

53 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

39 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

44 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

47 ms

recaptcha__en.js

recaptcha__en.js

13 ms

icon-smile-red.svg

icon-smile-red.svg

1362 ms

icon-home-red.svg

icon-home-red.svg

1393 ms

icon-chevron-right.svg

icon-chevron-right.svg

1497 ms

icon-call.svg

icon-call.svg

1367 ms

icon-heart.svg

icon-heart.svg

1394 ms

icon-honey.svg

icon-honey.svg

1474 ms

icon-drop.svg

icon-drop.svg

1474 ms

icon-medical.svg

icon-medical.svg

1471 ms

icon-prick.svg

icon-prick.svg

1344 ms

icon-book.svg

icon-book.svg

1359 ms

KJVfTG8DvK

KJVfTG8DvK

573 ms

icon-check.svg

icon-check.svg

1386 ms

icon-play.svg

icon-play.svg

1467 ms

icon-rectangle.svg

icon-rectangle.svg

1333 ms

advert.gif

advert.gif

795 ms

sync_cookie_image_decide

sync_cookie_image_decide

150 ms

1

1

151 ms

bundle_ru_RU.js

bundle_ru_RU.js

227 ms

1

1

138 ms

Accessibility Review

vperemen.com accessibility score

80

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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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.

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

vperemen.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

vperemen.com SEO score

90

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vperemen.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Vperemen.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

vperemen.com

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