Tools & Wizards About Us
granir.by screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    35% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

granir.by

Изготовление памятников в Минске. Изделия из гранита

Page Load Speed

6.1 sec in total

First Response

471 ms

Resources Loaded

4.7 sec

Page Rendered

854 ms

granir.by screenshot

About Website

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

Изготовление памятников в Минске из натурального гранита. Благоустройство могил по всей территории Республики Беларусь. Доступные цены. Высокое качество.

Visit granir.by

Key Findings

We analyzed Granir.by page load time and found that the first response time was 471 ms and then it took 5.6 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

granir.by performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.123

84/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

Network Requests Diagram

granir.by

471 ms

granir.by

627 ms

app.css

311 ms

js

110 ms

jquery.mCustomScrollbar.min.css

496 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 29% of them (28 requests) were addressed to the original Granir.by, 56% (55 requests) were made to St6-21.vk.com and 6% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source St6-21.vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 358.4 kB (6%)

Content Size

5.8 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Granir.by main page is 5.8 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. 65% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.9 kB

  • Original 29.3 kB
  • After minification 22.3 kB
  • After compression 6.4 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 7.0 kB, which is 24% 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 22.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 9.3 kB

  • Original 3.4 MB
  • After minification 3.4 MB

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. Granir images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 250.9 kB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.5 MB

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 250.9 kB or 14% of the original size.

CSS Optimization

-13%

Potential reduce by 75.4 kB

  • Original 576.0 kB
  • After minification 576.0 kB
  • After compression 500.6 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. Granir.by needs all CSS files to be minified and compressed as it can save up to 75.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (68%)

Requests Now

88

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

granir.by

granir.by

471 ms

granir.by

granir.by

627 ms

app.css

app.css

311 ms

js

js

110 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

496 ms

jquery.min.js

jquery.min.js

26 ms

custom.js

custom.js

617 ms

js

js

70 ms

ready-photo.png

ready-photo.png

960 ms

anortozit.png

anortozit.png

866 ms

leznik.png

leznik.png

900 ms

pokostovsky.png

pokostovsky.png

895 ms

tokovsky.png

tokovsky.png

959 ms

maslovsky.png

maslovsky.png

995 ms

gabbro.png

gabbro.png

1142 ms

slide-img-1.png

slide-img-1.png

1330 ms

slide-img-2.png

slide-img-2.png

1229 ms

slide-img-3.png

slide-img-3.png

1209 ms

slide-img-4.png

slide-img-4.png

1225 ms

slide-img-5.png

slide-img-5.png

1129 ms

css

css

37 ms

front-bg.png

front-bg.png

1035 ms

steps-bg.png

steps-bg.png

924 ms

ready-bg.png

ready-bg.png

1002 ms

vase-bg.png

vase-bg.png

1002 ms

promo-bg.png

promo-bg.png

1014 ms

granit-list-bg.png

granit-list-bg.png

1056 ms

order-call-bg.png

order-call-bg.png

1095 ms

400.woff

400.woff

832 ms

400.woff

400.woff

714 ms

100.woff

100.woff

915 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

970 ms

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

openapi.318ba3d5a50b8d6990cb0284cb0e0963.js

267 ms

zoomIn.png

zoomIn.png

489 ms

zoomOut.png

zoomOut.png

511 ms

close.png

close.png

519 ms

widget_community_messages.php

widget_community_messages.php

217 ms

loader_nav210916458538_3.js

loader_nav210916458538_3.js

182 ms

fonts_cnt.c7a76efe.css

fonts_cnt.c7a76efe.css

945 ms

lite.93f44416.css

lite.93f44416.css

649 ms

lang3_2.js

lang3_2.js

533 ms

c3d11fba.475e3ac7.js

c3d11fba.475e3ac7.js

521 ms

community_messages.js

community_messages.js

549 ms

react.6a15a5cc.js

react.6a15a5cc.js

736 ms

vkcom-kit.063a54b3.css

vkcom-kit.063a54b3.css

735 ms

vkcom-kit.053ba440.js

vkcom-kit.053ba440.js

982 ms

vkcom-kit-icons.780e6c65.js

vkcom-kit-icons.780e6c65.js

808 ms

vkui.55891411.js

vkui.55891411.js

985 ms

architecture-mobx.b1015542.js

architecture-mobx.b1015542.js

842 ms

state-management.94ab436a.js

state-management.94ab436a.js

850 ms

audioplayer-lib.93b52d88.css

audioplayer-lib.93b52d88.css

895 ms

audioplayer-lib.3321ac20.js

audioplayer-lib.3321ac20.js

1044 ms

palette.7a214ae3.css

palette.7a214ae3.css

980 ms

palette.f6379b46.js

palette.f6379b46.js

992 ms

sticker-lib.72942183.css

sticker-lib.72942183.css

1022 ms

sticker-lib.50cb0ba5.js

sticker-lib.50cb0ba5.js

1035 ms

common.9b1ff2f7.js

common.9b1ff2f7.js

1755 ms

e64d31af.3e58e6c0.js

e64d31af.3e58e6c0.js

1054 ms

782f47a3.38fd93c4.js

782f47a3.38fd93c4.js

1084 ms

39820787.47f9da1e.js

39820787.47f9da1e.js

1107 ms

fc936a0f.c2d7e178.js

fc936a0f.c2d7e178.js

1127 ms

f3627a66.f28d62e2.js

f3627a66.f28d62e2.js

1217 ms

emoji.39f546de.css

emoji.39f546de.css

1132 ms

emoji.4e5c7260.js

emoji.4e5c7260.js

1173 ms

7f463667.2f09ffd3.js

7f463667.2f09ffd3.js

1192 ms

ui_common.b1037836.css

ui_common.b1037836.css

1214 ms

ui_common.7023cefe.js

ui_common.7023cefe.js

1219 ms

b691fd56.7e596ee3.js

b691fd56.7e596ee3.js

1352 ms

ui_media_selector.33883160.css

ui_media_selector.33883160.css

1273 ms

ui_media_selector.8493a65a.js

ui_media_selector.8493a65a.js

1306 ms

xdm.js

xdm.js

1303 ms

f528815f.082e1657.js

f528815f.082e1657.js

1308 ms

upload.b1037836.css

upload.b1037836.css

1353 ms

upload.0afeb76b.js

upload.0afeb76b.js

1390 ms

stickers.00218c43.css

stickers.00218c43.css

1394 ms

lang3_0.js

lang3_0.js

790 ms

lite.bcf10ece3464fec8b554bde483fa2494.js

lite.bcf10ece3464fec8b554bde483fa2494.js

464 ms

vkui.388c7a16.css

vkui.388c7a16.css

963 ms

widget_community_messages.06a7f227.css

widget_community_messages.06a7f227.css

901 ms

notifier.fcca6e68.css

notifier.fcca6e68.css

789 ms

ui_common.54e472db.css

ui_common.54e472db.css

762 ms

ui_media_selector.2e6f2ad1.css

ui_media_selector.2e6f2ad1.css

757 ms

base.ec2ae8ae.css

base.ec2ae8ae.css

728 ms

stickers.feb0045e.js

stickers.feb0045e.js

700 ms

openapi.js

openapi.js

753 ms

EQ7Y5PUQ7MZtt_k3Nf8kTVC89cA1FHsS0RoLXiwQJmxtzYAUBYvAmUPqeEDKLzzB6Os1uvJu.jpg

EQ7Y5PUQ7MZtt_k3Nf8kTVC89cA1FHsS0RoLXiwQJmxtzYAUBYvAmUPqeEDKLzzB6Os1uvJu.jpg

359 ms

QulWsGFAn5k.png

QulWsGFAn5k.png

471 ms

w_chat_icon.png

w_chat_icon.png

89 ms

w_chat_logo.png

w_chat_logo.png

90 ms

widgets_logo_white.svg

widgets_logo_white.svg

91 ms

chats.png

chats.png

82 ms

community_messages_widget_small_logo.svg

community_messages_widget_small_logo.svg

87 ms

emoji_smile_icon.svg

emoji_smile_icon.svg

83 ms

upload.gif

upload.gif

167 ms

roboto400.woff

roboto400.woff

292 ms

roboto500.woff

roboto500.woff

260 ms

roboto300.woff

roboto300.woff

277 ms

roboto700.woff

roboto700.woff

281 ms

Accessibility Review

granir.by accessibility score

85

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.

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

granir.by best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

granir.by SEO score

85

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

High

robots.txt is not valid

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

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

granir.by

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