Tools & Wizards About Us
belwater.by screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

belwater.by

Сантехника в Минске, купить сантехнику в интернет-магазине Belwater.by

Page Load Speed

4.4 sec in total

First Response

482 ms

Resources Loaded

3.2 sec

Page Rendered

695 ms

belwater.by screenshot

About Website

Welcome to belwater.by homepage info - get ready to check Belwater best content for Belarus right away, or after learning these important things about belwater.by

Сантехника в интернет-магазине Belwater.by по лучшим ценам! ✔Доставка по Минску бесплатно от 70 BYN, осуществляется доставка по РБ. Купить сантехнику в Минске со ✔скидкой по тел.: ☎+375 (29) 690 84 00...

Visit belwater.by

Key Findings

We analyzed Belwater.by page load time and found that the first response time was 482 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

belwater.by performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value1,640 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.379

27/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

belwater.by

482 ms

belwater.by

663 ms

system.base.css

122 ms

system.messages.css

243 ms

system.theme.css

341 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 54% of them (32 requests) were addressed to the original Belwater.by, 34% (20 requests) were made to Belwater.io.activecloud.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Belwater.io.activecloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 474.6 kB (49%)

Content Size

959.7 kB

After Optimization

485.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Belwater.by main page is 959.7 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. 40% of websites need less resources to load. Javascripts take 494.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 48.0 kB

  • Original 60.4 kB
  • After minification 57.3 kB
  • After compression 12.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. 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 48.0 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 13.1 kB

  • Original 300.7 kB
  • After minification 287.6 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. Belwater images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 378.2 kB

  • Original 494.7 kB
  • After minification 420.9 kB
  • After compression 116.5 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 378.2 kB or 76% of the original size.

CSS Optimization

-34%

Potential reduce by 35.2 kB

  • Original 103.9 kB
  • After minification 102.7 kB
  • After compression 68.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. Belwater.by needs all CSS files to be minified and compressed as it can save up to 35.2 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (61%)

Requests Now

51

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

belwater.by

belwater.by

482 ms

belwater.by

belwater.by

663 ms

system.base.css

system.base.css

122 ms

system.messages.css

system.messages.css

243 ms

system.theme.css

system.theme.css

341 ms

dc_ajax_add_cart.css

dc_ajax_add_cart.css

345 ms

jquery.ui.core.min.css

jquery.ui.core.min.css

358 ms

jquery.ui.theme.min.css

jquery.ui.theme.min.css

361 ms

date.css

date.css

363 ms

datepicker.1.7.css

datepicker.1.7.css

365 ms

field.css

field.css

451 ms

node.css

node.css

459 ms

user.css

user.css

476 ms

youtube.css

youtube.css

481 ms

views.css

views.css

483 ms

ckeditor.css

ckeditor.css

484 ms

colorbox_style.css

colorbox_style.css

564 ms

ctools.css

ctools.css

573 ms

panels.css

panels.css

593 ms

modal.css

modal.css

599 ms

bootstrap-select.min.css

bootstrap-select.min.css

602 ms

slick.css

slick.css

604 ms

swiper.min.css

swiper.min.css

675 ms

wx_theme.style.css

wx_theme.style.css

919 ms

js_2LTPOyP50CQ-wS4q4OiC9U5u3jfPUlf5RTzfb343KPY.js

js_2LTPOyP50CQ-wS4q4OiC9U5u3jfPUlf5RTzfb343KPY.js

718 ms

js_EOb3npEogqagYAT0Vb17QrIztQCYFuyH8ZZBfSaUKf4.js

js_EOb3npEogqagYAT0Vb17QrIztQCYFuyH8ZZBfSaUKf4.js

1316 ms

bootstrap.min.js

bootstrap.min.js

29 ms

js_jHCYbEhnxePM2Hcl2fVHUoFVmuokAhlUNuN8WDqHT14.js

js_jHCYbEhnxePM2Hcl2fVHUoFVmuokAhlUNuN8WDqHT14.js

994 ms

js_d7yZEzBJSF94odP74dLURtL4vjCeVAuvZfmtKKSlxJw.js

js_d7yZEzBJSF94odP74dLURtL4vjCeVAuvZfmtKKSlxJw.js

766 ms

js_bJEzAofzB7nu6kVfP6vI74x4Xc84QKE-yaEcGi7tDdA.js

js_bJEzAofzB7nu6kVfP6vI74x4Xc84QKE-yaEcGi7tDdA.js

1128 ms

js_clrC6xIhrSIJlfTPWk5oeH6pvHxUPGKqgGtq_ThIHKg.js

js_clrC6xIhrSIJlfTPWk5oeH6pvHxUPGKqgGtq_ThIHKg.js

1252 ms

js_I6VZA3AF8hmzGOVNSdbeJmw_b-9PxNIUYR5GqaSCpHA.js

js_I6VZA3AF8hmzGOVNSdbeJmw_b-9PxNIUYR5GqaSCpHA.js

833 ms

css

css

38 ms

gtm.js

gtm.js

66 ms

sprite.png

sprite.png

273 ms

logo.png

logo.png

125 ms

287_0.jpg

287_0.jpg

284 ms

bezymyannyy888889_0.jpg

bezymyannyy888889_0.jpg

253 ms

62325533.jpg

62325533.jpg

243 ms

so-ready-decisions.jpg

so-ready-decisions.jpg

131 ms

so-prices.png

so-prices.png

137 ms

so-water.jpg

so-water.jpg

375 ms

so-guarantee.png

so-guarantee.png

256 ms

f00000506.jpg

f00000506.jpg

284 ms

bezymyannyy_1.jpg

bezymyannyy_1.jpg

365 ms

screenshot_20200927-103627_gallery.jpg

screenshot_20200927-103627_gallery.jpg

397 ms

screenshot_20200927-103748_gallery.jpg

screenshot_20200927-103748_gallery.jpg

396 ms

payment-methods.png

payment-methods.png

466 ms

wx_theme.style.css

wx_theme.style.css

365 ms

search-submit.jpg

search-submit.jpg

116 ms

divider.png

divider.png

121 ms

webxayc-logo.png

webxayc-logo.png

123 ms

bg_tab.png

bg_tab.png

119 ms

KFOmCnqEu92Fr1Mu5mxP.ttf

KFOmCnqEu92Fr1Mu5mxP.ttf

29 ms

KFOlCnqEu92Fr1MmEU9fABc9.ttf

KFOlCnqEu92Fr1MmEU9fABc9.ttf

45 ms

KFOlCnqEu92Fr1MmSU5fABc9.ttf

KFOlCnqEu92Fr1MmSU5fABc9.ttf

46 ms

KFOlCnqEu92Fr1MmWUlfABc9.ttf

KFOlCnqEu92Fr1MmWUlfABc9.ttf

44 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

381 ms

icomoon.ttf

icomoon.ttf

343 ms

Accessibility Review

belwater.by accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

Heading elements are not in a sequentially-descending order

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

belwater.by SEO score

84

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

belwater.by

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