Tools & Wizards About Us
zakon.by screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

zakon.by

Национальный правовой Интернет-портал Республики Беларусь

Page Load Speed

17.3 sec in total

First Response

4.9 sec

Resources Loaded

11.2 sec

Page Rendered

1.3 sec

zakon.by screenshot

About Website

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

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

Visit zakon.by

Key Findings

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

Performance Metrics

zakon.by performance score

0

Network Requests Diagram

zakon.by

4863 ms

screen.css

799 ms

adaptive.css

573 ms

animate.css

568 ms

style.css

424 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 83% of them (65 requests) were addressed to the original Zakon.by, 4% (3 requests) were made to Google-analytics.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Zakon.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 724.9 kB (48%)

Content Size

1.5 MB

After Optimization

774.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zakon.by main page is 1.5 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. 65% of websites need less resources to load. Images take 685.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 40.9 kB

  • Original 53.0 kB
  • After minification 46.4 kB
  • After compression 12.1 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 6.6 kB, which is 13% 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 40.9 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 69.3 kB

  • Original 685.1 kB
  • After minification 615.8 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. Zakon images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 463.9 kB

  • Original 592.0 kB
  • After minification 462.7 kB
  • After compression 128.1 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 463.9 kB or 78% of the original size.

CSS Optimization

-89%

Potential reduce by 150.8 kB

  • Original 169.0 kB
  • After minification 128.6 kB
  • After compression 18.2 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. Zakon.by needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (33%)

Requests Now

69

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zakon.by

zakon.by

4863 ms

screen.css

screen.css

799 ms

adaptive.css

adaptive.css

573 ms

animate.css

animate.css

568 ms

style.css

style.css

424 ms

ext.js

ext.js

575 ms

voite.js

voite.js

578 ms

WebResource.axd

WebResource.axd

739 ms

ScriptResource.axd

ScriptResource.axd

1028 ms

ScriptResource.axd

ScriptResource.axd

656 ms

jsdebug

jsdebug

485 ms

jquery.min.js

jquery.min.js

1010 ms

modernizr-custom.js

modernizr-custom.js

497 ms

jquery.debouncedresize.js

jquery.debouncedresize.js

494 ms

jquery.scrollTo.min.js

jquery.scrollTo.min.js

535 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

861 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

859 ms

sticky-kit.js

sticky-kit.js

859 ms

tooltipsy.min.js

tooltipsy.min.js

859 ms

slick.css

slick.css

1412 ms

slick.min.js

slick.min.js

1428 ms

common.js

common.js

1413 ms

css

css

133 ms

css

css

206 ms

ga.js

ga.js

178 ms

top100.cnt

top100.cnt

837 ms

bg-main.png

bg-main.png

829 ms

logo-main.png

logo-main.png

827 ms

sm_full.aspx

sm_full.aspx

828 ms

sm_full.aspx

sm_full.aspx

1780 ms

sm_full.aspx

sm_full.aspx

2545 ms

sm_full.aspx

sm_full.aspx

1440 ms

sm_full.aspx

sm_full.aspx

2198 ms

banner_207823.jpg

banner_207823.jpg

835 ms

banner_205483.jpg

banner_205483.jpg

3317 ms

sm_full.aspx

sm_full.aspx

1436 ms

sm_full.aspx

sm_full.aspx

1477 ms

sm_full.aspx

sm_full.aspx

1482 ms

sm_full.aspx

sm_full.aspx

1743 ms

banner_201473.jpg

banner_201473.jpg

1773 ms

banner_201463.jpg

banner_201463.jpg

1773 ms

banner_103973.jpg

banner_103973.jpg

2182 ms

banner_65603.jpg

banner_65603.jpg

2908 ms

banner_131643.jpg

banner_131643.jpg

2184 ms

banner_36603.jpg

banner_36603.jpg

2186 ms

banner_67983.jpg

banner_67983.jpg

2190 ms

banner_97323.jpg

banner_97323.jpg

2190 ms

banner_164843.jpg

banner_164843.jpg

2539 ms

banner_64083.jpg

banner_64083.jpg

2342 ms

banner_44463.jpg

banner_44463.jpg

2509 ms

banner_44553.jpg

banner_44553.jpg

2531 ms

astronim.png

astronim.png

2598 ms

__utm.gif

__utm.gif

572 ms

bg-header.png

bg-header.png

2524 ms

h-link1.png

h-link1.png

2344 ms

h-link2.png

h-link2.png

4688 ms

h-link3.png

h-link3.png

2387 ms

banner_208333.jpg

banner_208333.jpg

3556 ms

banner_199173.jpg

banner_199173.jpg

2550 ms

banner_201163.jpg

banner_201163.jpg

2957 ms

banner_200803.jpg

banner_200803.jpg

2337 ms

banner_201143.jpg

banner_201143.jpg

2325 ms

banner_201153.jpg

banner_201153.jpg

2538 ms

banner_201063.jpg

banner_201063.jpg

2544 ms

socials.png

socials.png

2879 ms

IgZJs4-7SA1XX_edsoXWog.ttf

IgZJs4-7SA1XX_edsoXWog.ttf

619 ms

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

616 ms

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

615 ms

icomoon.ttf

icomoon.ttf

3615 ms

hit

hit

553 ms

__utm.gif

__utm.gif

499 ms

watch.js

watch.js

493 ms

hit

hit

300 ms

ajax-loader.gif

ajax-loader.gif

2670 ms

slick.woff

slick.woff

2185 ms

slick.ttf

slick.ttf

188 ms

print.css

print.css

229 ms

adlik

adlik

225 ms

SEO Factors

zakon.by SEO score

0

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

zakon.by

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