Tools & Wizards About Us
i-on.by screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

i-on.by

I-ON.BY - Интернет-магазин в Могилёве. Компьютерная и бытовая техника

Page Load Speed

4.6 sec in total

First Response

1.2 sec

Resources Loaded

3.2 sec

Page Rendered

136 ms

i-on.by screenshot

About Website

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

Интернет-магазин компьютерной и бытовой техники в Могилёве. Огромный каталог товаров в Могилёве по низким ценам с доставкой на дом

Visit i-on.by

Key Findings

We analyzed I-on.by page load time and found that the first response time was 1.2 sec and then it took 3.4 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

i-on.by performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.336

34/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

i-on.by

1238 ms

i-on.by

619 ms

m.css

119 ms

logo2.png

227 ms

logo_min.png

316 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original I-on.by, 3% (1 request) were made to and 3% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain I-on.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.3 kB (8%)

Content Size

835.5 kB

After Optimization

765.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I-on.by main page is 835.5 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 583.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 61.6 kB

  • Original 76.7 kB
  • After minification 64.7 kB
  • After compression 15.2 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 12.0 kB, which is 16% 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 61.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 6.1 kB

  • Original 583.6 kB
  • After minification 577.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. I ON images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 159.6 kB
  • After minification 159.6 kB
  • After compression 158.3 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

-10%

Potential reduce by 1.5 kB

  • Original 15.6 kB
  • After minification 15.6 kB
  • After compression 14.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. I-on.by has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (8%)

Requests Now

36

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i-on.by

i-on.by

1238 ms

i-on.by

i-on.by

619 ms

m.css

m.css

119 ms

logo2.png

logo2.png

227 ms

logo_min.png

logo_min.png

316 ms

jq-3.3.1.js

jq-3.3.1.js

350 ms

m.js

m.js

340 ms

m.css

m.css

398 ms

h.jpg

h.jpg

391 ms

nav2.png

nav2.png

291 ms

vel.png

vel.png

326 ms

mts.png

mts.png

333 ms

search.png

search.png

337 ms

1.png

1.png

920 ms

2.png

2.png

665 ms

3.png

3.png

554 ms

4.png

4.png

556 ms

5.png

5.png

517 ms

mobile-130x90.jpg

mobile-130x90.jpg

518 ms

notebook-130x90.jpg

notebook-130x90.jpg

642 ms

videocard-130x90.jpg

videocard-130x90.jpg

642 ms

tv-130x90.jpg

tv-130x90.jpg

667 ms

mather-130x90.jpg

mather-130x90.jpg

670 ms

operativa-130x90.jpg

operativa-130x90.jpg

766 ms

naushniki-130x90.jpg

naushniki-130x90.jpg

765 ms

cpu-130x90.jpg

cpu-130x90.jpg

776 ms

no_image-130x90.png

no_image-130x90.png

776 ms

monitor-130x90.jpg

monitor-130x90.jpg

780 ms

+AAAAIAAAAAAAGMAAEAAAAAAAAAAAAAAAAAAAAFAAAAAAAAAAAAAAAAAQAAAAIAAHQAAFAAAAUAAAAAAA4ArgABAAAAAAABAA4AAAABAAAAAAACAA4ARwABAAAAAAADAA4AJAABAAAAAAAEAA4AVQABAAAAAAAFABYADgABAAAAAAAGAAcAMgABAAAAAAAKADQAYwADAAEECQABAA4AAAADAAEECQACAA4ARwADAAEECQADAA4AJAADAAEECQAEAA4AVQADAAEECQAFABYADgADAAEECQAGAA4AOQADAAEECQAKADQAYwBpAGMAbwBtAG8AbwBuAFYAZQByAHMAaQBvAG4AIAAxAC4AMABpAGMAbwBtAG8AbwBuaWNvbW9vbgBpAGMAbwBtAG8AbwBuAFIAZQBnAHUAbABhAHIAaQBjAG8AbQBvAG8AbgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==

+AAAAIAAAAAAAGMAAEAAAAAAAAAAAAAAAAAAAAFAAAAAAAAAAAAAAAAAQAAAAIAAHQAAFAAAAUAAAAAAA4ArgABAAAAAAABAA4AAAABAAAAAAACAA4ARwABAAAAAAADAA4AJAABAAAAAAAEAA4AVQABAAAAAAAFABYADgABAAAAAAAGAAcAMgABAAAAAAAKADQAYwADAAEECQABAA4AAAADAAEECQACAA4ARwADAAEECQADAA4AJAADAAEECQAEAA4AVQADAAEECQAFABYADgADAAEECQAGAA4AOQADAAEECQAKADQAYwBpAGMAbwBtAG8AbwBuAFYAZQByAHMAaQBvAG4AIAAxAC4AMABpAGMAbwBtAG8AbwBuaWNvbW9vbgBpAGMAbwBtAG8AbwBuAFIAZQBnAHUAbABhAHIAaQBjAG8AbQBvAG8AbgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==

0 ms

zakazat2.png

zakazat2.png

647 ms

garantiya2.png

garantiya2.png

647 ms

econom2.png

econom2.png

647 ms

vibor2.png

vibor2.png

647 ms

dostavka2.png

dostavka2.png

650 ms

help2.png

help2.png

769 ms

footer2.jpg

footer2.jpg

770 ms

pay3.png

pay3.png

758 ms

tag.js

tag.js

885 ms

top100.js

top100.js

545 ms

Accessibility Review

i-on.by accessibility score

73

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

i-on.by 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

i-on.by SEO score

82

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 I-on.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 I-on.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

i-on.by

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