Tools & Wizards About Us
pieroth.ru screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 57

    SEO

    Google-friendlier than
    20% of websites

pieroth.ru

Элитные вина от компании Пирот. Купить вино вы можете в Москве и Санкт-петербурге. Pieroth - всегда качественное и натуральное эксклюзивное вино.

Page Load Speed

5.7 sec in total

First Response

568 ms

Resources Loaded

4.9 sec

Page Rendered

228 ms

pieroth.ru screenshot

About Website

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

Элитные вина от компании Пирот нельзя купить в гипермаркетах, винных бутиках, попробовать в ресторанах, поскольку оно продается напрямую ценителям вин как эксклюзивный товар.

Visit pieroth.ru

Key Findings

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

Performance Metrics

pieroth.ru performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

pieroth.ru

568 ms

pieroth.ru

666 ms

style.css

142 ms

contact_ots.css

284 ms

filestyle.css

415 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 83% of them (38 requests) were addressed to the original Pieroth.ru, 9% (4 requests) were made to Yastatic.net and 4% (2 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 78.6 kB (15%)

Content Size

509.6 kB

After Optimization

430.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 53.2 kB

  • Original 65.5 kB
  • After minification 65.1 kB
  • After compression 12.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 53.2 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 17.3 kB

  • Original 323.8 kB
  • After minification 306.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. Pieroth images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 5.8 kB

  • Original 110.8 kB
  • After minification 110.3 kB
  • After compression 105.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

-25%

Potential reduce by 2.4 kB

  • Original 9.6 kB
  • After minification 9.6 kB
  • After compression 7.2 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. Pieroth.ru needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (44%)

Requests Now

41

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pieroth.ru

pieroth.ru

568 ms

pieroth.ru

pieroth.ru

666 ms

style.css

style.css

142 ms

contact_ots.css

contact_ots.css

284 ms

filestyle.css

filestyle.css

415 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

427 ms

brauser.js

brauser.js

429 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

574 ms

jquery.simplemodal.js

jquery.simplemodal.js

434 ms

jquery.cookie.js

jquery.cookie.js

425 ms

ajaxupload.3.5.js

ajaxupload.3.5.js

553 ms

jquery-ui-1.8.19.custom.min.js

jquery-ui-1.8.19.custom.min.js

857 ms

share.js

share.js

502 ms

fon.jpg

fon.jpg

142 ms

watch.js

watch.js

4 ms

vk.png

vk.png

143 ms

fb.png

fb.png

143 ms

ok.png

ok.png

142 ms

vline.gif

vline.gif

144 ms

104.jpg

104.jpg

550 ms

fon_up.gif

fon_up.gif

278 ms

fon_up_1.gif

fon_up_1.gif

283 ms

uznayte.gif

uznayte.gif

283 ms

call2.gif

call2.gif

424 ms

anketu.gif

anketu.gif

284 ms

st.gif

st.gif

420 ms

viptel.gif

viptel.gif

424 ms

pieroth_pic.jpg

pieroth_pic.jpg

705 ms

Pieroth_Estate_12_101142011.jpg

Pieroth_Estate_12_101142011.jpg

565 ms

news_line.gif

news_line.gif

560 ms

824.jpg

824.jpg

566 ms

798.jpg

798.jpg

565 ms

news_line1.gif

news_line1.gif

687 ms

fon_footer.png

fon_footer.png

684 ms

1120

1120

2764 ms

b-share-form-button.png

b-share-form-button.png

467 ms

watch.js

watch.js

1 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

654 ms

ui-bg_flat_0_aaaaaa_40x100.png

ui-bg_flat_0_aaaaaa_40x100.png

655 ms

ui-bg_highlight-soft_75_cccccc_1x100.png

ui-bg_highlight-soft_75_cccccc_1x100.png

655 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

772 ms

ui-bg_glass_75_e6e6e6_1x400.png

ui-bg_glass_75_e6e6e6_1x400.png

791 ms

ui-bg_glass_75_dadada_1x400.png

ui-bg_glass_75_dadada_1x400.png

794 ms

b-share-form-button_share__icon.png

b-share-form-button_share__icon.png

555 ms

b-share-icon.png

b-share-icon.png

688 ms

b-share-popup_down__tail.png

b-share-popup_down__tail.png

737 ms

Accessibility Review

pieroth.ru accessibility score

85

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pieroth.ru best practices score

75

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

SEO Factors

pieroth.ru SEO score

57

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

pieroth.ru

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