Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

azerpost.az

Azərpoçt

Page Load Speed

15.4 sec in total

First Response

2.6 sec

Resources Loaded

12.6 sec

Page Rendered

242 ms

azerpost.az screenshot

About Website

Welcome to azerpost.az homepage info - get ready to check Azerpost best content for Azerbaijan right away, or after learning these important things about azerpost.az

Visit azerpost.az

Key Findings

We analyzed Azerpost.az page load time and found that the first response time was 2.6 sec and then it took 12.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

azerpost.az performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.819

4/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

azerpost.az

2553 ms

menu.css

399 ms

style.css

596 ms

jquery.min.js

3118 ms

jqueryslidemenu.js

596 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that all of those requests were addressed to Azerpost.az and no external sources were called. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Azerpost.az.

Page Optimization Overview & Recommendations

Page size can be reduced by 276.3 kB (34%)

Content Size

808.1 kB

After Optimization

531.8 kB

In fact, the total size of Azerpost.az main page is 808.1 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. 20% of websites need less resources to load. Images take 674.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 38.9 kB

  • Original 44.3 kB
  • After minification 34.1 kB
  • After compression 5.4 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.2 kB, which is 23% 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 38.9 kB or 88% of the original size.

Image Optimization

-25%

Potential reduce by 171.3 kB

  • Original 674.5 kB
  • After minification 503.2 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, Azerpost needs image optimization as it can save up to 171.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 56.6 kB

  • Original 77.6 kB
  • After minification 70.5 kB
  • After compression 21.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 56.6 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 9.5 kB

  • Original 11.7 kB
  • After minification 6.6 kB
  • After compression 2.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. Azerpost.az needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (34%)

Requests Now

58

After Optimization

38

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

Accessibility Review

azerpost.az accessibility score

87

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

azerpost.az SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    AZ

  • Language Claimed

    N/A

  • Encoding

    KOI8-R

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azerpost.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 Azerpost.az main page’s claimed encoding is koi8-r. 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

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