Tools & Wizards About Us
imarket.by screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

imarket.by

Онлайн гипермаркет iMarket.by - интернет магазин в Минске с доставкой по Беларуси

Page Load Speed

3.6 sec in total

First Response

390 ms

Resources Loaded

3.1 sec

Page Rendered

205 ms

imarket.by screenshot

About Website

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

Покупайте в iMarket.by - онлайн-гипермаркете электроники, бытовой техники, товаров для дома и семьи. Скидки и специальные предложения. Собственная доставка по Минску и РБ. Пункты выдачи во всех област...

Visit imarket.by

Key Findings

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

imarket.by performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value3,110 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

imarket.by

390 ms

imarket.by

1181 ms

jquery.js

447 ms

core.min.css

239 ms

style.css

357 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 76% of them (39 requests) were addressed to the original Imarket.by, 6% (3 requests) were made to Google.com and 6% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Imarket.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 663.9 kB (47%)

Content Size

1.4 MB

After Optimization

747.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imarket.by main page is 1.4 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. Javascripts take 682.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 572.1 kB

  • Original 663.5 kB
  • After minification 542.8 kB
  • After compression 91.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 120.7 kB, which is 18% 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 572.1 kB or 86% of the original size.

Image Optimization

-14%

Potential reduce by 8.2 kB

  • Original 58.4 kB
  • After minification 50.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. Obviously, IMarket needs image optimization as it can save up to 8.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 80.6 kB

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

CSS Optimization

-44%

Potential reduce by 3.1 kB

  • Original 6.9 kB
  • After minification 4.4 kB
  • After compression 3.9 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. Imarket.by needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 44% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imarket.by

imarket.by

390 ms

imarket.by

imarket.by

1181 ms

jquery.js

jquery.js

447 ms

core.min.css

core.min.css

239 ms

style.css

style.css

357 ms

additional_all.css

additional_all.css

357 ms

styles.css

styles.css

359 ms

template_styles.css

template_styles.css

364 ms

core.min.js

core.min.js

631 ms

all.js

all.js

438 ms

api.js

api.js

36 ms

main.js

main.js

1015 ms

jquery.min.js

jquery.min.js

20 ms

ba.js

ba.js

313 ms

load.gif

load.gif

178 ms

viber.svg

viber.svg

175 ms

vk.svg

vk.svg

177 ms

telegram.svg

telegram.svg

178 ms

fb.svg

fb.svg

176 ms

whatsapp.svg

whatsapp.svg

265 ms

mail.svg

mail.svg

262 ms

phone.svg

phone.svg

264 ms

jam_messages-tablet.svg

jam_messages-tablet.svg

264 ms

search.svg

search.svg

266 ms

imarket_logo.svg

imarket_logo.svg

349 ms

jam_messages.svg

jam_messages.svg

352 ms

compare-basket.png

compare-basket.png

360 ms

recaptcha__en.js

recaptcha__en.js

170 ms

2-min.gif

2-min.gif

305 ms

profile-20.svg

profile-20.svg

318 ms

double_ring.svg

double_ring.svg

407 ms

2.gif

2.gif

412 ms

logo_payments.png

logo_payments.png

424 ms

velcom.png

velcom.png

423 ms

mts.png

mts.png

443 ms

life.png

life.png

523 ms

mobile_phone.png

mobile_phone.png

523 ms

Gilroyregular.ttf

Gilroyregular.ttf

646 ms

Gilroylight.ttf

Gilroylight.ttf

544 ms

Gilroymedium.ttf

Gilroymedium.ttf

559 ms

Gilroysemibold.ttf

Gilroysemibold.ttf

587 ms

Gilroyextrabold.ttf

Gilroyextrabold.ttf

618 ms

icomoon.ttf

icomoon.ttf

728 ms

fallback

fallback

28 ms

fallback

fallback

36 ms

bx_stat

bx_stat

184 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

35 ms

logo_48.png

logo_48.png

3 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

17 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

18 ms

Accessibility Review

imarket.by accessibility score

85

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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

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.

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

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

imarket.by best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

High

Missing source maps for large first-party JavaScript

SEO Factors

imarket.by SEO score

92

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

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

imarket.by

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