Tools & Wizards About Us
antaris.az screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

antaris.az

Antaris - Ofis Ləvazimatları, Dəftərxana. Onlayn Sifariş

Page Load Speed

695 ms in total

First Response

206 ms

Resources Loaded

376 ms

Page Rendered

113 ms

antaris.az screenshot

About Website

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

Ofis ləvazimatları, dəftərxana məhsulları,kreslo və seyflər mövcuddur. Hər növ dəftərxana və ofis ləvazimatları üçün ən doğru ünvan,Antaris

Visit antaris.az

Key Findings

We analyzed Antaris.az page load time and found that the first response time was 206 ms and then it took 489 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

antaris.az performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value48.0 s

0/100

25%

SI (Speed Index)

Value34.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,120 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value51.7 s

0/100

10%

Network Requests Diagram

antaris.az

206 ms

styles.css

28 ms

jquery-1.11.2.min.js

131 ms

imageSizer.js

57 ms

mainpage.js

55 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 80.7 kB (55%)

Content Size

146.8 kB

After Optimization

66.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Antaris.az main page is 146.8 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. Only 10% of websites need less resources to load. Javascripts take 100.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 2.1 kB

  • Original 3.0 kB
  • After minification 2.6 kB
  • After compression 870 B

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 452 B, which is 15% 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 2.1 kB or 71% of the original size.

Image Optimization

-16%

Potential reduce by 5.6 kB

  • Original 34.7 kB
  • After minification 29.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. Obviously, Antaris needs image optimization as it can save up to 5.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 65.6 kB

  • Original 100.5 kB
  • After minification 99.4 kB
  • After compression 34.8 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 65.6 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 7.3 kB

  • Original 8.7 kB
  • After minification 7.7 kB
  • After compression 1.4 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. Antaris.az needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Antaris. According to our analytics all requests are already optimized.

Network Requests Diagram

antaris.az

antaris.az

206 ms

styles.css

styles.css

28 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

131 ms

imageSizer.js

imageSizer.js

57 ms

mainpage.js

mainpage.js

55 ms

logo.png

logo.png

57 ms

background.png

background.png

28 ms

folder-opened.png

folder-opened.png

50 ms

folder-closed.png

folder-closed.png

51 ms

arrow.gif

arrow.gif

52 ms

Accessibility Review

antaris.az accessibility score

75

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

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

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

High

Page has valid source maps

SEO Factors

antaris.az SEO score

92

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    AZ

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antaris.az can be misinterpreted by Google and other search engines. Our service has detected that Azerbaijani is used on the page, and it does not match the claimed English language. Our system also found out that Antaris.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

antaris.az

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