Tools & Wizards About Us
alloplant.ru screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

alloplant.ru

Аллоплант — Всероссийский центр глазной и пластической хирургии

Page Load Speed

6.5 sec in total

First Response

629 ms

Resources Loaded

4.5 sec

Page Rendered

1.3 sec

alloplant.ru screenshot

About Website

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

Официальный сайт ФГБУ Всероссийский центр глазной и пластической хирургии Минздрава России

Visit alloplant.ru

Key Findings

We analyzed Alloplant.ru page load time and found that the first response time was 629 ms and then it took 5.8 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

alloplant.ru performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

alloplant.ru

629 ms

alloplant.ru

1267 ms

kernel_main_v1.css

366 ms

ui.design-tokens.min.css

486 ms

ui.font.opensans.min.css

365 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 76% of them (41 requests) were addressed to the original Alloplant.ru, 6% (3 requests) were made to Cdnjs.cloudflare.com and 4% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Alloplant.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.9 kB (26%)

Content Size

2.2 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Alloplant.ru main page is 2.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. 25% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 134.6 kB

  • Original 215.6 kB
  • After minification 204.9 kB
  • After compression 81.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 134.6 kB or 62% of the original size.

Image Optimization

-4%

Potential reduce by 56.3 kB

  • Original 1.5 MB
  • After minification 1.4 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. Alloplant images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 3.9 kB

  • Original 95.0 kB
  • After minification 95.0 kB
  • After compression 91.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. This website has mostly compressed JavaScripts.

CSS Optimization

-89%

Potential reduce by 362.2 kB

  • Original 405.1 kB
  • After minification 338.5 kB
  • After compression 42.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. Alloplant.ru needs all CSS files to be minified and compressed as it can save up to 362.2 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (54%)

Requests Now

50

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

alloplant.ru

alloplant.ru

629 ms

alloplant.ru

alloplant.ru

1267 ms

kernel_main_v1.css

kernel_main_v1.css

366 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

486 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

365 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

486 ms

page_1065b1246892a8bea1c19519acc7c461_v1.css

page_1065b1246892a8bea1c19519acc7c461_v1.css

369 ms

template_dfb608e1f1a23fa45afb6e1aa31b4276_v1.css

template_dfb608e1f1a23fa45afb6e1aa31b4276_v1.css

1212 ms

core.min.js

core.min.js

1091 ms

kernel_main_v1.js

kernel_main_v1.js

1103 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

728 ms

template_c1dcea31364ccfec5aa1c218c195231e_v1.js

template_c1dcea31364ccfec5aa1c218c195231e_v1.js

971 ms

css2

css2

37 ms

jquery-ui.min.css

jquery-ui.min.css

38 ms

jquery-ui.min.js

jquery-ui.min.js

53 ms

jquery.nice-select.min.js

jquery.nice-select.min.js

72 ms

js

js

125 ms

ba.js

ba.js

285 ms

embed

embed

352 ms

geo.svg

geo.svg

128 ms

time.svg

time.svg

123 ms

mail.svg

mail.svg

123 ms

search.svg

search.svg

128 ms

eye.png

eye.png

130 ms

calendar-icon.gif

calendar-icon.gif

131 ms

0402eeqcob7y2eeyt3ymovnv9tfny7ik.jpg

0402eeqcob7y2eeyt3ymovnv9tfny7ik.jpg

366 ms

alloplant.ru

alloplant.ru

748 ms

sr3c1xen9fh38upfoklntzijuzjgtplj.jpg

sr3c1xen9fh38upfoklntzijuzjgtplj.jpg

369 ms

549fneimq13n2r7oazhkqpojbmock3mm.jpg

549fneimq13n2r7oazhkqpojbmock3mm.jpg

969 ms

v3twypih29xbbv7xhzaf0z9vj6izfri9.jpg

v3twypih29xbbv7xhzaf0z9vj6izfri9.jpg

613 ms

28wifqp677rktcv4tg868v2i6r6az62j.svg

28wifqp677rktcv4tg868v2i6r6az62j.svg

251 ms

uo1b8q148nyhzjt7gsnvbidzapz2y968.svg

uo1b8q148nyhzjt7gsnvbidzapz2y968.svg

375 ms

eg7fs6fbohgmc9eztcxux79gkvlyada1.svg

eg7fs6fbohgmc9eztcxux79gkvlyada1.svg

486 ms

7lyyedi9xv0ql9vk4w3yuro0pjg1y7g1.svg

7lyyedi9xv0ql9vk4w3yuro0pjg1y7g1.svg

492 ms

9nnwy2yu79ddl6oijci3enc6uuw2wal4.svg

9nnwy2yu79ddl6oijci3enc6uuw2wal4.svg

497 ms

u0kw26qfs37rnhvuzwhhgw0r9o8rx0a0.svg

u0kw26qfs37rnhvuzwhhgw0r9o8rx0a0.svg

608 ms

d49taurtyi3sslrrb25mqqdqmq9fg5r3.svg

d49taurtyi3sslrrb25mqqdqmq9fg5r3.svg

615 ms

441zl18rzjma7iej8pf04nvir8v1msd7.svg

441zl18rzjma7iej8pf04nvir8v1msd7.svg

619 ms

bn8qnoxodb11jtay2d7cg05ayasjqexi.svg

bn8qnoxodb11jtay2d7cg05ayasjqexi.svg

729 ms

g1bs826i79odgyfy8070s20uap7a40fu.svg

g1bs826i79odgyfy8070s20uap7a40fu.svg

732 ms

7sr2bouqqxenpymhc9dsjsmxm7m4an0e.png

7sr2bouqqxenpymhc9dsjsmxm7m4an0e.png

1240 ms

footer_logo.svg

footer_logo.svg

986 ms

ponpx9khag9dofj18z9r693i2rksvpu0.jpg

ponpx9khag9dofj18z9r693i2rksvpu0.jpg

849 ms

footer_eye.svg

footer_eye.svg

853 ms

fb.svg

fb.svg

867 ms

yt.svg

yt.svg

970 ms

ok.svg

ok.svg

974 ms

vk.svg

vk.svg

990 ms

font

font

46 ms

tag.js

tag.js

846 ms

bx_stat

bx_stat

184 ms

js

js

64 ms

advert.gif

advert.gif

708 ms

sync_cookie_image_decide

sync_cookie_image_decide

155 ms

Accessibility Review

alloplant.ru accessibility score

77

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

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

alloplant.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

High

Browser errors were logged to the console

SEO Factors

alloplant.ru SEO score

92

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

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 Alloplant.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 Alloplant.ru 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

alloplant.ru

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