Tools & Wizards About Us
stat.gov.az screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

stat.gov.az

Azərbaycan Respublikasının Dövlət Statistika Komitəsi

Page Load Speed

3.7 sec in total

First Response

569 ms

Resources Loaded

2.8 sec

Page Rendered

256 ms

stat.gov.az screenshot

About Website

Click here to check amazing Stat Gov content. Otherwise, check out these important facts you probably never knew about stat.gov.az

Azərbaycan Respublikasının Dövlət Statistika Komitəsinin rəsmi internet səhifəsi

Visit stat.gov.az

Key Findings

We analyzed Stat.gov.az page load time and found that the first response time was 569 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

stat.gov.az performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.19

65/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

stat.gov.az

569 ms

style.css

196 ms

menu_style.css

387 ms

bls_combined.css

387 ms

secondary_menu.css

388 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 Stat.gov.az, 7% (5 requests) were made to Openstat.net and 3% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (980 ms) belongs to the original domain Stat.gov.az.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.9 kB (47%)

Content Size

264.9 kB

After Optimization

141.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stat.gov.az main page is 264.9 kB. 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 151.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 49.1 kB

  • Original 58.7 kB
  • After minification 47.9 kB
  • After compression 9.6 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 10.8 kB, which is 18% 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 49.1 kB or 84% of the original size.

Image Optimization

-22%

Potential reduce by 32.9 kB

  • Original 151.6 kB
  • After minification 118.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. Obviously, Stat Gov needs image optimization as it can save up to 32.9 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 11.3 kB

  • Original 18.3 kB
  • After minification 18.3 kB
  • After compression 7.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 11.3 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 30.6 kB

  • Original 36.3 kB
  • After minification 25.7 kB
  • After compression 5.7 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. Stat.gov.az needs all CSS files to be minified and compressed as it can save up to 30.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (47%)

Requests Now

64

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stat.gov.az

stat.gov.az

569 ms

style.css

style.css

196 ms

menu_style.css

menu_style.css

387 ms

bls_combined.css

bls_combined.css

387 ms

secondary_menu.css

secondary_menu.css

388 ms

function.js

function.js

389 ms

jquery-2.1.4.min.js

jquery-2.1.4.min.js

597 ms

jcarousellite_1.0.1c4.js

jcarousellite_1.0.1c4.js

398 ms

ajax_az.js

ajax_az.js

575 ms

text_slider.js

text_slider.js

578 ms

link_click_counter_az.js

link_click_counter_az.js

876 ms

click_counter_az.js

click_counter_az.js

882 ms

webeke.png

webeke.png

387 ms

border.gif

border.gif

195 ms

border-middle.gif

border-middle.gif

193 ms

bg_body.gif

bg_body.gif

199 ms

gerb_az.gif

gerb_az.gif

193 ms

azstat.jpg

azstat.jpg

199 ms

barcurrent_big.gif

barcurrent_big.gif

385 ms

1px.gif

1px.gif

385 ms

archive.gif

archive.gif

387 ms

bmt_2016.gif

bmt_2016.gif

395 ms

more.gif

more.gif

396 ms

logo_3(120x90).gif

logo_3(120x90).gif

577 ms

logo_4(120x90).gif

logo_4(120x90).gif

578 ms

bmf4.gif

bmf4.gif

578 ms

home.gif

home.gif

388 ms

email.gif

email.gif

388 ms

map.gif

map.gif

397 ms

faq.png

faq.png

398 ms

bigbox.gif

bigbox.gif

449 ms

1px.gif

1px.gif

457 ms

wsd_az.jpg

wsd_az.jpg

961 ms

rss_.png

rss_.png

580 ms

toggle-up.gif

toggle-up.gif

591 ms

toggle-dn.gif

toggle-dn.gif

592 ms

map_az.gif

map_az.gif

641 ms

Und1.gif

Und1.gif

655 ms

stat_az.gif

stat_az.gif

769 ms

statistics_www_az.gif

statistics_www_az.gif

788 ms

link_gov.az.gif

link_gov.az.gif

788 ms

Baku_link_az_.gif

Baku_link_az_.gif

830 ms

link_nmr.gif

link_nmr.gif

843 ms

virtualkarabakh_az.gif

virtualkarabakh_az.gif

961 ms

mobile_version.png

mobile_version.png

980 ms

9172.gif

9172.gif

315 ms

database_base.png

database_base.png

324 ms

datatable.png

datatable.png

327 ms

arrow-normal.gif

arrow-normal.gif

499 ms

certification.gif

certification.gif

501 ms

checklist.gif

checklist.gif

503 ms

fetch_az.php

fetch_az.php

717 ms

topLinkBg.gif

topLinkBg.gif

489 ms

searchFormBg11.gif

searchFormBg11.gif

509 ms

searchInput.gif

searchInput.gif

509 ms

searchSubmit.gif

searchSubmit.gif

674 ms

know_hover.gif

know_hover.gif

676 ms

aggression.png

aggression.png

676 ms

gboxtop_2_22.gif

gboxtop_2_22.gif

678 ms

cnt.js

cnt.js

356 ms

2292055.js

2292055.js

129 ms

digits

digits

131 ms

cnt

cnt

254 ms

space.gif

space.gif

194 ms

f.gif

f.gif

130 ms

pixel

pixel

18 ms

pixel

pixel

16 ms

collect

collect

120 ms

Accessibility Review

stat.gov.az accessibility score

71

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

Form elements do not have associated labels

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.

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

stat.gov.az 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

SEO Factors

stat.gov.az SEO score

96

Search Engine Optimization Advices

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

    AZ

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stat.gov.az can be misinterpreted by Google and other search engines. Our service has detected that Azerbaijani 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 Stat.gov.az 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

stat.gov.az

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