Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

prup.ru

Сервис проверки доменов

Page Load Speed

2.6 sec in total

First Response

640 ms

Resources Loaded

1.8 sec

Page Rendered

148 ms

prup.ru screenshot

About Website

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

Сервис проверки доменов

Visit prup.ru

Key Findings

We analyzed Prup.ru page load time and found that the first response time was 640 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

prup.ru performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

prup.ru

640 ms

style.css

779 ms

150x150.gif

701 ms

logo.gif

234 ms

monitor-on.gif

246 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 91% of them (43 requests) were addressed to the original Prup.ru, 2% (1 request) were made to Telderi.ru and 2% (1 request) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (779 ms) belongs to the original domain Prup.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.4 kB (51%)

Content Size

56.1 kB

After Optimization

27.7 kB

In fact, the total size of Prup.ru main page is 56.1 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 26.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 19.7 kB

  • Original 26.4 kB
  • After minification 25.7 kB
  • After compression 6.8 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 19.7 kB or 74% of the original size.

Image Optimization

-12%

Potential reduce by 2.5 kB

  • Original 20.6 kB
  • After minification 18.1 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. Obviously, Prup needs image optimization as it can save up to 2.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 36 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 1.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

-79%

Potential reduce by 6.3 kB

  • Original 8.0 kB
  • After minification 6.4 kB
  • After compression 1.7 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. Prup.ru needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (28%)

Requests Now

46

After Optimization

33

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

Accessibility Review

prup.ru accessibility score

51

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[accesskey] values are not unique

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

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

SEO Factors

prup.ru SEO score

54

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

High

Document uses plugins

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prup.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 Prup.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

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