Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

giz.by

Товары для здоровья, гигиены, дома и сада - Интернет-магазин giz.by

Page Load Speed

23.2 sec in total

First Response

786 ms

Resources Loaded

20.7 sec

Page Rendered

1.6 sec

giz.by screenshot

About Website

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

Интернет-магазине медицинской техники (медтехники), товаров для здоровья и красоты, ортопедические товары и др

Visit giz.by

Key Findings

We analyzed Giz.by page load time and found that the first response time was 786 ms and then it took 22.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

giz.by performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

giz.by

786 ms

giz.by

1656 ms

kernel_main.css

280 ms

page_cb23d2df13a7e821bda3d0a1601a8f43.css

277 ms

template_03e6991e99da88d2a4a310456d0d7eac.css

677 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 81% of them (107 requests) were addressed to the original Giz.by, 3% (4 requests) were made to Google.com and 2% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Track.hubrus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (31%)

Content Size

3.9 MB

After Optimization

2.7 MB

In fact, the total size of Giz.by main page is 3.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 216.7 kB

  • Original 245.7 kB
  • After minification 153.3 kB
  • After compression 29.0 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 92.4 kB, which is 38% 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 216.7 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 162.0 kB

  • Original 2.5 MB
  • After minification 2.3 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. Giz images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 552.7 kB

  • Original 756.0 kB
  • After minification 711.9 kB
  • After compression 203.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 552.7 kB or 73% of the original size.

CSS Optimization

-69%

Potential reduce by 267.7 kB

  • Original 389.4 kB
  • After minification 386.8 kB
  • After compression 121.8 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. Giz.by needs all CSS files to be minified and compressed as it can save up to 267.7 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (18%)

Requests Now

121

After Optimization

99

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

Accessibility Review

giz.by accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

giz.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 Giz.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 Giz.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

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