Tools & Wizards About Us
ipool.by screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

ipool.by

Оборудование для бассейнов в Минске - широкий ассортимент под любые задачи

Page Load Speed

3.7 sec in total

First Response

379 ms

Resources Loaded

3.1 sec

Page Rendered

222 ms

ipool.by screenshot

About Website

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

Оборудование для бассейнов: фильтры, трубы, насосы, фитинг, закладные элементы, электрооборудование. Услуги по строительству и монтажу бассейнов в Минске по доступным ценам

Visit ipool.by

Key Findings

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

Performance Metrics

ipool.by performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

ipool.by

379 ms

ipool.by

1022 ms

css

20 ms

ui.design-tokens.min.css

122 ms

ui.font.opensans.min.css

242 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Ipool.by, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ipool.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.6 kB (14%)

Content Size

1.2 MB

After Optimization

998.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 68.1 kB

  • Original 83.6 kB
  • After minification 58.6 kB
  • After compression 15.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 24.9 kB, which is 30% 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 68.1 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 27.9 kB

  • Original 745.2 kB
  • After minification 717.3 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. Ipool images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 54.0 kB

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

CSS Optimization

-26%

Potential reduce by 8.6 kB

  • Original 33.7 kB
  • After minification 33.7 kB
  • After compression 25.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. Ipool.by needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

48

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ipool.by

ipool.by

379 ms

ipool.by

ipool.by

1022 ms

css

css

20 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

122 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

242 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

340 ms

ss_admin.min.css

ss_admin.min.css

342 ms

page_a071adca97423af9f637b04d68344886_v1.css

page_a071adca97423af9f637b04d68344886_v1.css

346 ms

template_1ec49c992573432f816e31bdbb76ea45_v1.css

template_1ec49c992573432f816e31bdbb76ea45_v1.css

357 ms

popup.min.css

popup.min.css

362 ms

core.min.js

core.min.js

611 ms

kernel_main_v1.js

kernel_main_v1.js

678 ms

protobuf.min.js

protobuf.min.js

566 ms

model.min.js

model.min.js

461 ms

core_promise.min.js

core_promise.min.js

474 ms

rest.client.min.js

rest.client.min.js

482 ms

pull.client.min.js

pull.client.min.js

695 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

594 ms

ss_admin.min.js

ss_admin.min.js

602 ms

template_ebd216d3cdca96fee6a5e5425f3c3228_v1.js

template_ebd216d3cdca96fee6a5e5425f3c3228_v1.js

795 ms

page_160d5aeae62681762765eedddde460cc_v1.js

page_160d5aeae62681762765eedddde460cc_v1.js

712 ms

ba.js

ba.js

275 ms

top-bg.jpg

top-bg.jpg

144 ms

menu-bg.png

menu-bg.png

141 ms

logo.png

logo.png

142 ms

menu-bg2.png

menu-bg2.png

145 ms

ico-basket.png

ico-basket.png

143 ms

98eca2fdd36c0106e1a5eeb720f9e4d7.jpg

98eca2fdd36c0106e1a5eeb720f9e4d7.jpg

459 ms

d38463412140ae2d4d8fdab319e10776.jpg

d38463412140ae2d4d8fdab319e10776.jpg

451 ms

36a851ae30a9637c3af2951a56e922aa.jpg

36a851ae30a9637c3af2951a56e922aa.jpg

339 ms

76e040b68117c2b4a2ad53a6a2cf7a89.jpg

76e040b68117c2b4a2ad53a6a2cf7a89.jpg

590 ms

ico-new.png

ico-new.png

240 ms

5goraxnmg44oopl4q14an8uac87umd63.jpg

5goraxnmg44oopl4q14an8uac87umd63.jpg

242 ms

ytynjz8a6y9jxnuwwl3sp94vbygg0ggz.png

ytynjz8a6y9jxnuwwl3sp94vbygg0ggz.png

480 ms

ico-popular.png

ico-popular.png

364 ms

yxnaucxzkuenyz87644cvlvqqtf80tep.jpg

yxnaucxzkuenyz87644cvlvqqtf80tep.jpg

451 ms

yjayfrqfm732wed12y1kax4qj5wfwaea.jpg

yjayfrqfm732wed12y1kax4qj5wfwaea.jpg

486 ms

ago9fpndneitlpbui38e6om48isdab7b.jpg

ago9fpndneitlpbui38e6om48isdab7b.jpg

563 ms

logo-sm.png

logo-sm.png

563 ms

ico-fb.png

ico-fb.png

575 ms

ico-vk.png

ico-vk.png

600 ms

ico-youtube.jpg

ico-youtube.jpg

606 ms

ico-g+.jpg

ico-g+.jpg

675 ms

opensans-regular.woff

opensans-regular.woff

620 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjM.woff

80 ms

opensans-light.woff

opensans-light.woff

638 ms

opensans-semibold.woff

opensans-semibold.woff

651 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQUwaEQXjM.woff

84 ms

opensans-bold.woff

opensans-bold.woff

782 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQUwaEQXjM.woff

85 ms

slider-txt-bg.png

slider-txt-bg.png

670 ms

ico-loupe.png

ico-loupe.png

730 ms

basket.png

basket.png

730 ms

footer-bg.jpg

footer-bg.jpg

745 ms

watch.js

watch.js

35 ms

analytics.js

analytics.js

41 ms

slider-dot.png

slider-dot.png

625 ms

collect

collect

14 ms

bx_stat

bx_stat

181 ms

Accessibility Review

ipool.by accessibility score

83

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

Links do not have a discernible name

Best Practices

ipool.by best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ipool.by SEO score

77

Search Engine Optimization Advices

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

ipool.by

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