Tools & Wizards About Us
lador.ru screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

lador.ru

Трубы бесшовные (горячекатаный и холоднокатаные), ГОСТ на металлопрокат, трубы электросварные (круглые и профильные), профнастил и металлоизделия - Уз...

Page Load Speed

3.9 sec in total

First Response

513 ms

Resources Loaded

3.2 sec

Page Rendered

174 ms

lador.ru screenshot

About Website

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

Стальные трубы, прокат, профили. Скачать ГОСТ на металлопрокат (черный, цветной, нержавеющий) – арматура, швеллер и другая металлопродукция

Visit lador.ru

Key Findings

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

Performance Metrics

lador.ru performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.191

64/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

lador.ru

513 ms

lador.ru

608 ms

common.css

132 ms

menu.js

262 ms

calculator.js

391 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 88% of them (29 requests) were addressed to the original Lador.ru, 6% (2 requests) were made to Yastatic.net and 6% (2 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (895 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.4 kB (42%)

Content Size

280.9 kB

After Optimization

161.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 118.3 kB

  • Original 144.6 kB
  • After minification 142.2 kB
  • After compression 26.3 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 118.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 189 B

  • Original 44.5 kB
  • After minification 44.4 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. Lador images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 286 B

  • Original 88.2 kB
  • After minification 88.2 kB
  • After compression 87.9 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

-17%

Potential reduce by 601 B

  • Original 3.5 kB
  • After minification 3.5 kB
  • After compression 2.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. Lador.ru needs all CSS files to be minified and compressed as it can save up to 601 B or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (63%)

Requests Now

30

After Optimization

11

  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lador. 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 as a result speed up the page load time.

Network Requests Diagram

lador.ru

lador.ru

513 ms

lador.ru

lador.ru

608 ms

common.css

common.css

132 ms

menu.js

menu.js

262 ms

calculator.js

calculator.js

391 ms

es5-shims.min.js

es5-shims.min.js

471 ms

share.js

share.js

692 ms

ico_home_a.gif

ico_home_a.gif

131 ms

ico_map_p.gif

ico_map_p.gif

146 ms

ico_mail.gif

ico_mail.gif

146 ms

logo_lador.gif

logo_lador.gif

261 ms

dsgn_phone_top.gif

dsgn_phone_top.gif

275 ms

top_pic_default_01.jpg

top_pic_default_01.jpg

418 ms

g1.jpg

g1.jpg

391 ms

g2.jpg

g2.jpg

406 ms

g3.jpg

g3.jpg

509 ms

dsgn_phone_bottom.jpg

dsgn_phone_bottom.jpg

521 ms

bgr_bottom.gif

bgr_bottom.gif

453 ms

top_pic_default_02.jpg

top_pic_default_02.jpg

452 ms

menu_item_p_01.gif

menu_item_p_01.gif

457 ms

menu_item_p_02.gif

menu_item_p_02.gif

465 ms

menu_item_p_03.gif

menu_item_p_03.gif

551 ms

menu_item_p_04.gif

menu_item_p_04.gif

568 ms

menu_item_p_05.gif

menu_item_p_05.gif

581 ms

menu_item_p_06.gif

menu_item_p_06.gif

586 ms

menu_item_p_07.gif

menu_item_p_07.gif

589 ms

menu_item_p_08.gif

menu_item_p_08.gif

595 ms

menu_item_p_09.gif

menu_item_p_09.gif

676 ms

menu_item_p_10.gif

menu_item_p_10.gif

697 ms

menu_item_p_11.gif

menu_item_p_11.gif

711 ms

menu_item_p_12.gif

menu_item_p_12.gif

718 ms

watch.js

watch.js

0 ms

tag.js

tag.js

895 ms

Accessibility Review

lador.ru accessibility score

80

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

lador.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

lador.ru SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lador.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lador.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

lador.ru

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