Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

richstone.by

Натуральный камень купить в Минске, Беларусь виды камня для облицовки, отделки, цена, натуральный камень изделия

Page Load Speed

7.3 sec in total

First Response

477 ms

Resources Loaded

6.5 sec

Page Rendered

327 ms

richstone.by screenshot

About Website

Visit richstone.by now to see the best up-to-date Richstone content for Belarus and also check out these interesting facts you probably never knew about richstone.by

Изделия из натурального и искусственного камня - плитка, столешницы, ступени, подоконники, камины заказывайте здесь. Широкий выбор. Доступные цены.

Visit richstone.by

Key Findings

We analyzed Richstone.by page load time and found that the first response time was 477 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

richstone.by performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.154

75/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

richstone.by

477 ms

richstone.by

1698 ms

ui.design-tokens.min.css

121 ms

ui.font.opensans.min.css

240 ms

main.popup.bundle.min.css

338 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 72% of them (63 requests) were addressed to the original Richstone.by, 3% (3 requests) were made to Mc.yandex.ru and 3% (3 requests) were made to Stoneland.bitrix24.ru. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Tindalini.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 642.0 kB (28%)

Content Size

2.3 MB

After Optimization

1.6 MB

In fact, the total size of Richstone.by main page is 2.3 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. 60% of websites need less resources to load. Images take 919.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 510.4 kB

  • Original 637.1 kB
  • After minification 631.0 kB
  • After compression 126.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 510.4 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 18.3 kB

  • Original 919.5 kB
  • After minification 901.2 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. Richstone images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 80.9 kB

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

CSS Optimization

-32%

Potential reduce by 32.4 kB

  • Original 100.6 kB
  • After minification 100.6 kB
  • After compression 68.1 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. Richstone.by needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (33%)

Requests Now

75

After Optimization

50

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

Accessibility Review

richstone.by accessibility score

76

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

richstone.by 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

richstone.by SEO score

83

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

    N/A

  • Encoding

    UTF-8

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

Open Graph data is detected on the main page of Richstone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: