Tools & Wizards About Us
leprf.ru screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

leprf.ru

ЛЭПРФ

Page Load Speed

4.5 sec in total

First Response

524 ms

Resources Loaded

3.6 sec

Page Rendered

338 ms

leprf.ru screenshot

About Website

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

Интернет-магазин

Visit leprf.ru

Key Findings

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

leprf.ru performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value15.6 s

7/100

10%

Network Requests Diagram

leprf.ru

524 ms

leprf.ru

1253 ms

ui.design-tokens.min.css

503 ms

ui.font.opensans.min.css

383 ms

main.popup.bundle.min.css

508 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 65% of them (15 requests) were addressed to the original Leprf.ru, 17% (4 requests) were made to Fonts.gstatic.com and 9% (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 Leprf.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (85%)

Content Size

1.4 MB

After Optimization

213.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Leprf.ru main page is 1.4 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. CSS take 792.6 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 445.2 kB

  • Original 491.4 kB
  • After minification 367.4 kB
  • After compression 46.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. This page needs HTML code to be minified as it can gain 124.0 kB, which is 25% 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 445.2 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 918 B

  • Original 99.4 kB
  • After minification 98.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. Leprf images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 3.8 kB

  • Original 6.7 kB
  • After minification 6.7 kB
  • After compression 2.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.8 kB or 57% of the original size.

CSS Optimization

-92%

Potential reduce by 726.6 kB

  • Original 792.6 kB
  • After minification 761.7 kB
  • After compression 66.0 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. Leprf.ru needs all CSS files to be minified and compressed as it can save up to 726.6 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (53%)

Requests Now

15

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

leprf.ru

leprf.ru

524 ms

leprf.ru

leprf.ru

1253 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

503 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

383 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

508 ms

css

css

30 ms

template_60a697f8a925a98073743d1505b4d7c3_v1.css

template_60a697f8a925a98073743d1505b4d7c3_v1.css

1136 ms

core.min.js

core.min.js

908 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

632 ms

template_c23b46c3d6627d1f07d37865961a29c6_v1.js

template_c23b46c3d6627d1f07d37865961a29c6_v1.js

1254 ms

ba.js

ba.js

285 ms

logotype.png

logotype.png

435 ms

logo.png

logo.png

127 ms

picture.loading.svg

picture.loading.svg

129 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aX8.ttf

149 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aX8.ttf

285 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aX8.ttf

272 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aX8.ttf

312 ms

a4051eb32350f3de0547a4c2dc1e9b79.svg

a4051eb32350f3de0547a4c2dc1e9b79.svg

127 ms

832 ms

backgroung.jpg

backgroung.jpg

384 ms

bottom_back.png

bottom_back.png

137 ms

bx_stat

bx_stat

185 ms

Accessibility Review

leprf.ru accessibility score

65

Accessibility Issues

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

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

[id] attributes on active, focusable elements are not unique

Best Practices

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

leprf.ru SEO score

81

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

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

leprf.ru

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