Tools & Wizards About Us
aznar.az screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

aznar.az

AZNAR Natural Products | сайт компании | AZNAR

Page Load Speed

4.3 sec in total

First Response

708 ms

Resources Loaded

3.1 sec

Page Rendered

485 ms

aznar.az screenshot

About Website

Welcome to aznar.az homepage info - get ready to check AZNAR best content for Russia right away, or after learning these important things about aznar.az

Visit aznar.az

Key Findings

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

Performance Metrics

aznar.az performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,720 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

aznar.az

708 ms

vendor.css

265 ms

style.css

403 ms

dev.css

274 ms

228 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 86% of them (50 requests) were addressed to the original Aznar.az, 14% (8 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Aznar.az.

Page Optimization Overview & Recommendations

Page size can be reduced by 833.3 kB (11%)

Content Size

7.7 MB

After Optimization

6.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aznar.az main page is 7.7 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. 70% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 179.4 kB

  • Original 202.8 kB
  • After minification 182.2 kB
  • After compression 23.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. 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 179.4 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 254.3 kB

  • Original 7.0 MB
  • After minification 6.7 MB

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. AZNAR images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 240.1 kB

  • Original 342.8 kB
  • After minification 334.0 kB
  • After compression 102.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 240.1 kB or 70% of the original size.

CSS Optimization

-89%

Potential reduce by 159.6 kB

  • Original 179.2 kB
  • After minification 142.1 kB
  • After compression 19.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. Aznar.az needs all CSS files to be minified and compressed as it can save up to 159.6 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aznar.az

aznar.az

708 ms

vendor.css

vendor.css

265 ms

style.css

style.css

403 ms

dev.css

dev.css

274 ms

228 ms

library.min.js

library.min.js

459 ms

plugin.min.js

plugin.min.js

544 ms

script.js

script.js

290 ms

dev.js

dev.js

394 ms

1.jpg

1.jpg

669 ms

2.jpg

2.jpg

459 ms

%D0%BF%D1%80%D0%BE%D0%B4%D1%8D%D0%BA%D1%81%D0%BF%D0%BE%202016_360-270.jpg

%D0%BF%D1%80%D0%BE%D0%B4%D1%8D%D0%BA%D1%81%D0%BF%D0%BE%202016_360-270.jpg

1459 ms

%D0%BF%D1%80%D0%BE%D0%B4%D1%8D%D0%BA%D1%81%D0%BF%D0%BE%202016_360-270%20%D0%BB%D1%83%D1%87%D1%88%D0%B8%D0%B9%20%D0%BF%D1%80%D0%BE%D0%B4%D1%83%D0%BA%D1%82.jpg

%D0%BF%D1%80%D0%BE%D0%B4%D1%8D%D0%BA%D1%81%D0%BF%D0%BE%202016_360-270%20%D0%BB%D1%83%D1%87%D1%88%D0%B8%D0%B9%20%D0%BF%D1%80%D0%BE%D0%B4%D1%83%D0%BA%D1%82.jpg

1464 ms

zoom%20grante%20360-270.jpg

zoom%20grante%20360-270.jpg

1494 ms

9.jpg

9.jpg

836 ms

5.jpg

5.jpg

809 ms

3.jpg

3.jpg

1038 ms

4.jpg

4.jpg

1038 ms

635 ms

logo.svg

logo.svg

612 ms

3-1.svg

3-1.svg

776 ms

4-1.svg

4-1.svg

777 ms

5-1.svg

5-1.svg

778 ms

4-2.svg

4-2.svg

810 ms

3-2.svg

3-2.svg

810 ms

1-2.svg

1-2.svg

820 ms

1-right-1.svg

1-right-1.svg

913 ms

2-1.svg

2-1.svg

921 ms

1-1.svg

1-1.svg

958 ms

1-2.svg

1-2.svg

1047 ms

2-1.svg

2-1.svg

1054 ms

2-2.svg

2-2.svg

1095 ms

3-1.svg

3-1.svg

1166 ms

3-2.svg

3-2.svg

1169 ms

4-1.svg

4-1.svg

1182 ms

4-2.svg

4-2.svg

1188 ms

7-1.svg

7-1.svg

1201 ms

7-2.svg

7-2.svg

1268 ms

1.jpg

1.jpg

1433 ms

2.png

2.png

1434 ms

3.png

3.png

2116 ms

factoy-1.png

factoy-1.png

1624 ms

boxes-1.png

boxes-1.png

1339 ms

4.png

4.png

1789 ms

5.png

5.png

1786 ms

PTSans-Bold.woff

PTSans-Bold.woff

1545 ms

PFAgoraSerifPro-Regular.svg

PFAgoraSerifPro-Regular.svg

1597 ms

PFAgoraSerifPro-Regular.woff

PFAgoraSerifPro-Regular.woff

1484 ms

PTSans-Regular.woff

PTSans-Regular.woff

1502 ms

Circe-Bold.svg

Circe-Bold.svg

1573 ms

Circe-Bold.woff

Circe-Bold.woff

1236 ms

preloader.gif

preloader.gif

1301 ms

combine.js

combine.js

455 ms

combine.js

combine.js

696 ms

util_cursor_storage_grab.cur

util_cursor_storage_grab.cur

114 ms

util_cursor_storage_grabbing.cur

util_cursor_storage_grabbing.cur

115 ms

util_cursor_storage_help.cur

util_cursor_storage_help.cur

242 ms

util_cursor_storage_zoom_in.cur

util_cursor_storage_zoom_in.cur

242 ms

Accessibility Review

aznar.az accessibility score

84

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

aznar.az best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

aznar.az SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Aznar.az 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 Aznar.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

aznar.az

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