Tools & Wizards About Us
lgrstroy.ru screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lgrstroy.ru

Интернет-магазин стройматериалов «ЛидерГрупп Строй», строительные материалы с доставкой

Page Load Speed

4.6 sec in total

First Response

535 ms

Resources Loaded

3.9 sec

Page Rendered

146 ms

lgrstroy.ru screenshot

About Website

Welcome to lgrstroy.ru homepage info - get ready to check Lgrstroy best content for Russia right away, or after learning these important things about lgrstroy.ru

Компания «ЛидерГрупп Строй» реализует широчайший ассортимент строительных материалов для отделки и ремонта.

Visit lgrstroy.ru

Key Findings

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

Performance Metrics

lgrstroy.ru performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value14,270 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

lgrstroy.ru

535 ms

lgrstroy.ru

901 ms

core.min.js

399 ms

kernel_main_v1.js

534 ms

core_ls.min.js

403 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 40% of them (25 requests) were addressed to the original Lgrstroy.ru, 51% (32 requests) were made to App.uiscom.ru and 3% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (957 ms) relates to the external source Gso.amocrm.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 464.0 kB (47%)

Content Size

995.6 kB

After Optimization

531.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Lgrstroy.ru main page is 995.6 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. 60% of websites need less resources to load. HTML takes 524.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 438.5 kB

  • Original 524.3 kB
  • After minification 521.9 kB
  • After compression 85.7 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 438.5 kB or 84% of the original size.

JavaScript Optimization

-6%

Potential reduce by 25.3 kB

  • Original 458.3 kB
  • After minification 458.3 kB
  • After compression 433.0 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

-1%

Potential reduce by 168 B

  • Original 13.1 kB
  • After minification 13.1 kB
  • After compression 12.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. Lgrstroy.ru has all CSS files already compressed.

Requests Breakdown

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

Requests Now

57

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lgrstroy.ru

lgrstroy.ru

535 ms

lgrstroy.ru

lgrstroy.ru

901 ms

core.min.js

core.min.js

399 ms

kernel_main_v1.js

kernel_main_v1.js

534 ms

core_ls.min.js

core_ls.min.js

403 ms

protobuf.min.js

protobuf.min.js

534 ms

model.min.js

model.min.js

401 ms

rest.client.min.js

rest.client.min.js

402 ms

pull.client.min.js

pull.client.min.js

532 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

667 ms

intlTelInput.min.js

intlTelInput.min.js

542 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

543 ms

currency-core.bundle.min.js

currency-core.bundle.min.js

664 ms

core_currency.min.js

core_currency.min.js

677 ms

template_395d6d9429af920e49e2e31a8a1fdc92_v1.js

template_395d6d9429af920e49e2e31a8a1fdc92_v1.js

803 ms

page_b182cdd5e2ee57405955cb9d757a068b_v1.js

page_b182cdd5e2ee57405955cb9d757a068b_v1.js

678 ms

cs.min.js

cs.min.js

951 ms

intlTelInput.min.css

intlTelInput.min.css

546 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

663 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

666 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

668 ms

script.min.js

script.min.js

668 ms

MuseoSansCyrl-300.woff

MuseoSansCyrl-300.woff

150 ms

uinext2020min.ttf

uinext2020min.ttf

139 ms

MuseoSansCyrl-500.woff

MuseoSansCyrl-500.woff

159 ms

MuseoSansCyrl-700.woff

MuseoSansCyrl-700.woff

273 ms

button.js

button.js

957 ms

fbevents.js

fbevents.js

43 ms

tag.js

tag.js

844 ms

132 ms

comagic.widgets.min.js

comagic.widgets.min.js

241 ms

760 ms

sitephone.min.js

sitephone.min.js

305 ms

sitephone_rack.html

sitephone_rack.html

360 ms

sitephone_label.html

sitephone_label.html

360 ms

sitephone_simple.html

sitephone_simple.html

372 ms

sitephone.html

sitephone.html

373 ms

sitephone_times_options.html

sitephone_times_options.html

373 ms

consultant.min.js

consultant.min.js

424 ms

consultant_chat_bot_message.html

consultant_chat_bot_message.html

551 ms

consultant_chat_bot_email_message.html

consultant_chat_bot_email_message.html

551 ms

consultant_chat_bot_retention_btn_message.html

consultant_chat_bot_retention_btn_message.html

552 ms

consultant_chat_bot_rating_message.html

consultant_chat_bot_rating_message.html

552 ms

consultant_chat_bot_vcard_message.html

consultant_chat_bot_vcard_message.html

551 ms

consultant_chat_visitor_file_message.html

consultant_chat_visitor_file_message.html

553 ms

consultant_chat_operator_file_message.html

consultant_chat_operator_file_message.html

598 ms

consultant_chat_operator_message.html

consultant_chat_operator_message.html

598 ms

consultant_chat_visitor_message.html

consultant_chat_visitor_message.html

616 ms

consultant_chat_system_message.html

consultant_chat_system_message.html

617 ms

consultant_label.html

consultant_label.html

618 ms

consultant_rack.html

consultant_rack.html

669 ms

consultant_chat.html

consultant_chat.html

715 ms

consultant_chat_group_selector.html

consultant_chat_group_selector.html

717 ms

consultant_offline_message.html

consultant_offline_message.html

738 ms

personal_form.min.js

personal_form.min.js

739 ms

personal_form.html

personal_form.html

741 ms

call_generator3.min.js

call_generator3.min.js

791 ms

call_generator.html

call_generator.html

833 ms

time_options.html

time_options.html

835 ms

offline_message_generator2.min.js

offline_message_generator2.min.js

864 ms

offline_message_generator2.html

offline_message_generator2.html

865 ms

advert.gif

advert.gif

639 ms

sync_cookie_image_decide

sync_cookie_image_decide

135 ms

Accessibility Review

lgrstroy.ru accessibility score

70

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

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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

Links do not have a discernible name

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

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.

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

lgrstroy.ru SEO score

92

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

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

lgrstroy.ru

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