Tools & Wizards About Us
giran.by screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

giran.by

Каталог предприятий Беларуси. Телефонный справочник фирм

Page Load Speed

22.3 sec in total

First Response

560 ms

Resources Loaded

21.4 sec

Page Rendered

285 ms

giran.by screenshot

About Website

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

Наиболее полный бизнес-справочник Республики Беларусь, насчитывающий более 60 тысяч компаний. Бесплатное размещение рекламной информации о предприятиях на нашем портале.

Visit giran.by

Key Findings

We analyzed Giran.by page load time and found that the first response time was 560 ms and then it took 21.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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

giran.by performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value1.374

0/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

giran.by

560 ms

skitter.styles.css

111 ms

mootools-core.js

318 ms

core.js

210 ms

caption.js

220 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 70% of them (59 requests) were addressed to the original Giran.by, 8% (7 requests) were made to Rtbw.acint.net and 4% (3 requests) were made to Site.yandex.net. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Ecopress.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.3 kB (15%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Giran.by main page is 2.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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 35.8 kB

  • Original 48.4 kB
  • After minification 47.4 kB
  • After compression 12.5 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 35.8 kB or 74% of the original size.

Image Optimization

-9%

Potential reduce by 136.4 kB

  • Original 1.6 MB
  • After minification 1.4 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. Giran images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 149.4 kB

  • Original 542.4 kB
  • After minification 542.3 kB
  • After compression 392.9 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 149.4 kB or 28% of the original size.

CSS Optimization

-40%

Potential reduce by 11.7 kB

  • Original 29.2 kB
  • After minification 27.9 kB
  • After compression 17.6 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. Giran.by needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (75%)

Requests Now

77

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

giran.by

giran.by

560 ms

skitter.styles.css

skitter.styles.css

111 ms

mootools-core.js

mootools-core.js

318 ms

core.js

core.js

210 ms

caption.js

caption.js

220 ms

jquery.js

jquery.js

338 ms

btloader.min.js

btloader.min.js

248 ms

base.css

base.css

245 ms

layout.css

layout.css

313 ms

menus.css

menus.css

331 ms

modules.css

modules.css

355 ms

tools.css

tools.css

356 ms

system.css

system.css

417 ms

extensions.css

extensions.css

420 ms

custom.css

custom.css

441 ms

whitenoise.css

whitenoise.css

449 ms

droidsans.css

droidsans.css

466 ms

droidsans.css

droidsans.css

463 ms

droidsans.css

droidsans.css

520 ms

style.css

style.css

524 ms

responsive.css

responsive.css

551 ms

print.css

print.css

559 ms

droidsans.css

droidsans.css

571 ms

warp.js

warp.js

576 ms

responsive.js

responsive.js

623 ms

accordionmenu.js

accordionmenu.js

627 ms

dropdownmenu.js

dropdownmenu.js

660 ms

template.js

template.js

670 ms

css

css

22 ms

adsbygoogle.js

adsbygoogle.js

199 ms

106924.js

106924.js

1038 ms

base.css

base.css

345 ms

layout.css

layout.css

353 ms

menus.css

menus.css

383 ms

modules.css

modules.css

378 ms

tools.css

tools.css

417 ms

system.css

system.css

367 ms

system.css

system.css

398 ms

system-all.css

system-all.css

406 ms

responsive.css

responsive.css

281 ms

print.css

print.css

277 ms

informer.php

informer.php

19988 ms

noise_bg.jpg

noise_bg.jpg

142 ms

logo-new1.png

logo-new1.png

397 ms

1brest1.jpg

1brest1.jpg

630 ms

1.jpg

1.jpg

530 ms

2.jpg

2.jpg

337 ms

3.jpg

3.jpg

476 ms

4.jpg

4.jpg

803 ms

5.jpg

5.jpg

550 ms

plus.png

plus.png

504 ms

all.js

all.js

898 ms

menubar.png

menubar.png

608 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

620 ms

jquery.skitter.min.js

jquery.skitter.min.js

648 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

652 ms

jquery.animate-colors-min.js

jquery.animate-colors-min.js

690 ms

DroidSans-webfont.woff

DroidSans-webfont.woff

717 ms

show_ads_impl.js

show_ads_impl.js

513 ms

totop_scroller.png

totop_scroller.png

675 ms

menu_line_item.png

menu_line_item.png

683 ms

hit

hit

398 ms

aci.js

aci.js

653 ms

hit

hit

543 ms

zrt_lookup.html

zrt_lookup.html

45 ms

ads

ads

357 ms

ads

ads

297 ms

prev.png

prev.png

107 ms

next.png

next.png

112 ms

back-box-label-black.png

back-box-label-black.png

123 ms

ajax-loader.gif

ajax-loader.gif

130 ms

suggest.js

suggest.js

370 ms

opensearch.js

opensearch.js

476 ms

ca-pub-7910718788872614

ca-pub-7910718788872614

90 ms

1

1

664 ms

watch.js

watch.js

2 ms

ymcode

ymcode

646 ms

1

1

678 ms

1

1

680 ms

1

1

682 ms

1

1

683 ms

1

1

685 ms

watch.js

watch.js

1 ms

1

1

102 ms

Accessibility Review

giran.by accessibility score

85

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

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

Page has valid source maps

SEO Factors

giran.by SEO score

90

Search Engine Optimization Advices

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

giran.by

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