Tools & Wizards About Us
e-kommunal.uz screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e-kommunal.uz

E-kommunal

Page Load Speed

12.4 sec in total

First Response

601 ms

Resources Loaded

11.5 sec

Page Rendered

281 ms

e-kommunal.uz screenshot

About Website

Visit e-kommunal.uz now to see the best up-to-date E Kommunal content for Uzbekistan and also check out these interesting facts you probably never knew about e-kommunal.uz

Портал коммунального хозяйства и жилищного фонда

Visit e-kommunal.uz

Key Findings

We analyzed E-kommunal.uz page load time and found that the first response time was 601 ms and then it took 11.8 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

e-kommunal.uz performance score

0

Network Requests Diagram

601 ms

core.css

362 ms

style.css

378 ms

style.css

379 ms

core.js

741 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 88% of them (60 requests) were addressed to the original E-kommunal.uz, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Teploenergo.uz. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain E-kommunal.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 443.3 kB (35%)

Content Size

1.3 MB

After Optimization

834.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-kommunal.uz main page is 1.3 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. 30% of websites need less resources to load. Images take 764.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 30.4 kB

  • Original 40.3 kB
  • After minification 34.9 kB
  • After compression 9.9 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 5.4 kB, which is 14% 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 30.4 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 66.3 kB

  • Original 764.4 kB
  • After minification 698.1 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. E Kommunal images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 291.7 kB

  • Original 405.4 kB
  • After minification 371.0 kB
  • After compression 113.7 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 291.7 kB or 72% of the original size.

CSS Optimization

-81%

Potential reduce by 54.8 kB

  • Original 67.9 kB
  • After minification 58.6 kB
  • After compression 13.0 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. E-kommunal.uz needs all CSS files to be minified and compressed as it can save up to 54.8 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Kommunal. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

601 ms

core.css

core.css

362 ms

style.css

style.css

378 ms

style.css

style.css

379 ms

core.js

core.js

741 ms

core_ajax.js

core_ajax.js

920 ms

session.js

session.js

738 ms

reset.css

reset.css

747 ms

style.css

style.css

935 ms

userstyles.css

userstyles.css

947 ms

jquery.min.js

jquery.min.js

3705 ms

jquery-ui.min.js

jquery-ui.min.js

5691 ms

jquery.dropdownPlain.js

jquery.dropdownPlain.js

1120 ms

jquery.jcarousel.js

jquery.jcarousel.js

1489 ms

informer_png.php

informer_png.php

800 ms

COST.PNG

COST.PNG

2859 ms

mini_baner_2.png

mini_baner_2.png

749 ms

uz-certified.gif

uz-certified.gif

750 ms

iduz.png

iduz.png

806 ms

texture.gif

texture.gif

186 ms

bg.png

bg.png

371 ms

logo.png

logo.png

560 ms

rss.png

rss.png

372 ms

header.png

header.png

936 ms

search.png

search.png

383 ms

eb2cd930eaaaf3fffc6a622a480e01e9.jpg

eb2cd930eaaaf3fffc6a622a480e01e9.jpg

726 ms

0556809aa79b87f8e3aef119bd63da21.jpg

0556809aa79b87f8e3aef119bd63da21.jpg

749 ms

bb9fe2b9e98c35417cdfca6fe7f2b4b5.jpg

bb9fe2b9e98c35417cdfca6fe7f2b4b5.jpg

756 ms

80a23037b2a1afb99d1c3bb85f22c1b7.JPG

80a23037b2a1afb99d1c3bb85f22c1b7.JPG

1722 ms

0399ded7bfb389e59dd3ffdf762d0ba7.png

0399ded7bfb389e59dd3ffdf762d0ba7.png

1177 ms

0423db3d105ff2a55c8220f08f3ddce0.jpg

0423db3d105ff2a55c8220f08f3ddce0.jpg

1274 ms

21072087b931828e835c6aaa9cba709a.jpg

21072087b931828e835c6aaa9cba709a.jpg

1130 ms

4cddf1e074c05309a8566bda8b8bf27c.jpg

4cddf1e074c05309a8566bda8b8bf27c.jpg

1128 ms

mygovuz_service.jpg

mygovuz_service.jpg

1710 ms

ek_mini.gif

ek_mini.gif

1490 ms

078d5b1e08cff37288b4b9816bd5bc69.jpg

078d5b1e08cff37288b4b9816bd5bc69.jpg

2054 ms

598c196eacdc832b8dbfdcd2efc8f525.JPG

598c196eacdc832b8dbfdcd2efc8f525.JPG

2181 ms

442a0ff2da40cdaf80c58e8fbf623379.jpg

442a0ff2da40cdaf80c58e8fbf623379.jpg

2191 ms

bf103af2a810aacf5b37a339c8f6cdc7.jpg

bf103af2a810aacf5b37a339c8f6cdc7.jpg

2674 ms

2e5a6ad3666fe1ad39b15e2d970aad2f.jpg

2e5a6ad3666fe1ad39b15e2d970aad2f.jpg

2456 ms

20ffa0af47056b461c563e1d76722e45.jpg

20ffa0af47056b461c563e1d76722e45.jpg

2825 ms

u-pay-logo.jpg

u-pay-logo.jpg

2422 ms

obrasheniya.png

obrasheniya.png

796 ms

news.png

news.png

2562 ms

territory.png

territory.png

2784 ms

base.png

base.png

2821 ms

jkh.png

jkh.png

2943 ms

info.png

info.png

3065 ms

help.png

help.png

3160 ms

opros.png

opros.png

3184 ms

mobile_app.png

mobile_app.png

3195 ms

active.png

active.png

3321 ms

hover.png

hover.png

3451 ms

news_bg.png

news_bg.png

3528 ms

like.gif

like.gif

3529 ms

comment.gif

comment.gif

3532 ms

cnt.png

cnt.png

384 ms

ga.js

ga.js

39 ms

__utm.gif

__utm.gif

26 ms

getCommentsCount.php

getCommentsCount.php

3621 ms

getCommentsCount.php

getCommentsCount.php

3564 ms

getCommentsCount.php

getCommentsCount.php

3694 ms

getCommentsCount.php

getCommentsCount.php

3806 ms

getCommentsCount.php

getCommentsCount.php

3671 ms

getCommentsCount.php

getCommentsCount.php

3537 ms

l-button.png

l-button.png

3439 ms

r-button.png

r-button.png

3554 ms

dot.png

dot.png

3521 ms

SEO Factors

e-kommunal.uz SEO score

0

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-kommunal.uz 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 E-kommunal.uz 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

e-kommunal.uz

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