Tools & Wizards About Us
gorodinfo.by screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gorodinfo.by

Каталог компаний. Справочник организаций, телефоны и адреса. ГородИнфо Беларусь

Page Load Speed

19.1 sec in total

First Response

499 ms

Resources Loaded

18.1 sec

Page Rendered

533 ms

gorodinfo.by screenshot

About Website

Click here to check amazing Gorodinfo content for Belarus. Otherwise, check out these important facts you probably never knew about gorodinfo.by

Каталог компаний. Справочник организаций, телефоны и адреса. ГородИнфо Беларусь | Информационно-справочный портал города

Visit gorodinfo.by

Key Findings

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

Performance Metrics

gorodinfo.by performance score

0

Network Requests Diagram

gorodinfo.by

499 ms

grodnoinfo.by

1034 ms

jquery.min.js

568 ms

notepad.js

401 ms

jquery.js

598 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gorodinfo.by, 80% (82 requests) were made to Grodnoinfo.by and 4% (4 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (13.7 sec) relates to the external source Grodnoinfo.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 433.8 kB (37%)

Content Size

1.2 MB

After Optimization

723.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gorodinfo.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. 40% of websites need less resources to load. Images take 666.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 137.0 kB

  • Original 161.1 kB
  • After minification 152.4 kB
  • After compression 24.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. 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 137.0 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 63.6 kB

  • Original 666.3 kB
  • After minification 602.7 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. Gorodinfo images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 126.5 kB

  • Original 206.5 kB
  • After minification 205.1 kB
  • After compression 80.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 126.5 kB or 61% of the original size.

CSS Optimization

-87%

Potential reduce by 106.7 kB

  • Original 123.3 kB
  • After minification 96.2 kB
  • After compression 16.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. Gorodinfo.by needs all CSS files to be minified and compressed as it can save up to 106.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (43%)

Requests Now

96

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gorodinfo.by

gorodinfo.by

499 ms

grodnoinfo.by

grodnoinfo.by

1034 ms

jquery.min.js

jquery.min.js

568 ms

notepad.js

notepad.js

401 ms

jquery.js

jquery.js

598 ms

style.css

style.css

596 ms

platform.js

platform.js

559 ms

autocomplete.css

autocomplete.css

198 ms

autocomplete.js

autocomplete.js

362 ms

buttontop.js

buttontop.js

364 ms

share.js

share.js

229 ms

css

css

514 ms

css

css

541 ms

css

css

621 ms

buttontop.css

buttontop.css

392 ms

bootstrap.icon.css

bootstrap.icon.css

621 ms

header.png

header.png

1057 ms

top.jpg

top.jpg

739 ms

menu_back.png

menu_back.png

1309 ms

menu2.jpg

menu2.jpg

893 ms

lg.png

lg.png

412 ms

52.jpg

52.jpg

1571 ms

1.png

1.png

592 ms

2.png

2.png

743 ms

3.png

3.png

904 ms

16.png

16.png

916 ms

4.png

4.png

1031 ms

5.png

5.png

1048 ms

6.png

6.png

1071 ms

7.png

7.png

1236 ms

8.png

8.png

1256 ms

9.png

9.png

1253 ms

10.png

10.png

1269 ms

11.png

11.png

2019 ms

12.png

12.png

2219 ms

13.png

13.png

4913 ms

14.png

14.png

1455 ms

15.png

15.png

1461 ms

17.png

17.png

1645 ms

18.png

18.png

1657 ms

19.png

19.png

1706 ms

20.png

20.png

1864 ms

21.png

21.png

1957 ms

22.png

22.png

2055 ms

23.png

23.png

2088 ms

24.png

24.png

2112 ms

35.jpg

35.jpg

2332 ms

32.jpg

32.jpg

2382 ms

41.gif

41.gif

2575 ms

4160.png

4160.png

2279 ms

6004.jpg

6004.jpg

2340 ms

acode.js

acode.js

328 ms

2187.jpg

2187.jpg

2432 ms

watch.js

watch.js

74 ms

watch.js

watch.js

74 ms

ya-share-cnt.html

ya-share-cnt.html

60 ms

watch.js

watch.js

3 ms

b-share-icon.png

b-share-icon.png

151 ms

b-share_counter_large.png

b-share_counter_large.png

163 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

2857 ms

837 ms

share_count

share_count

2037 ms

dk

dk

861 ms

share.php

share.php

701 ms

fql.query

fql.query

287 ms

wm

wm

331 ms

2182.png

2182.png

2776 ms

6005.png

6005.png

3224 ms

2480.jpg

2480.jpg

2760 ms

76.jpg

76.jpg

1942 ms

6019.jpg

6019.jpg

2955 ms

6043.png

6043.png

2712 ms

2092.jpg

2092.jpg

2840 ms

1.jpg

1.jpg

3035 ms

6054.jpg

6054.jpg

2907 ms

6068.jpg

6068.jpg

3424 ms

6074.jpg

6074.jpg

5055 ms

nologo.png

nologo.png

2884 ms

6072.png

6072.png

3130 ms

6071.jpg

6071.jpg

3619 ms

6070.jpg

6070.jpg

5067 ms

6069.jpg

6069.jpg

4243 ms

6067.jpg

6067.jpg

5149 ms

6065.png

6065.png

6557 ms

6046.jpg

6046.jpg

5989 ms

6055.gif

6055.gif

4265 ms

43.jpg

43.jpg

5506 ms

34.jpg

34.jpg

5401 ms

46.jpg

46.jpg

5674 ms

nav.png

nav.png

4795 ms

ph.png

ph.png

4892 ms

em.png

em.png

5395 ms

one-f.png

one-f.png

5251 ms

two-f.png

two-f.png

5203 ms

adlik

adlik

284 ms

three-f.png

three-f.png

5426 ms

qrgorodinfo.gif

qrgorodinfo.gif

5285 ms

49.gif

49.gif

13721 ms

osn.png

osn.png

5693 ms

search.jpg

search.jpg

5215 ms

poisk.png

poisk.png

5191 ms

up-arrow.png

up-arrow.png

5038 ms

SEO Factors

gorodinfo.by SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gorodinfo.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 Gorodinfo.by main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

gorodinfo.by

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