Tools & Wizards About Us
aeaxa.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

aeaxa.com

Сианьское изобилие металлургического оборудования, ООО.-

Page Load Speed

3.1 sec in total

First Response

384 ms

Resources Loaded

2.1 sec

Page Rendered

587 ms

aeaxa.com screenshot

About Website

Click here to check amazing Aeaxa content. Otherwise, check out these important facts you probably never knew about aeaxa.com

Мы специализируемся на производстве электродуговых печей для металлургического оборудования (EAF), печей для очистки стальных пакетов (LF), печей с погребенной дугой (SAF), аргонокислородных декарбони...

Visit aeaxa.com

Key Findings

We analyzed Aeaxa.com page load time and found that the first response time was 384 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

aeaxa.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.443

21/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

aeaxa.com

384 ms

aeaxa.com

412 ms

js

75 ms

esi2.css

92 ms

jquery.js

244 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 98% of them (55 requests) were addressed to the original Aeaxa.com, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Aeaxa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 405.3 kB (7%)

Content Size

5.5 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aeaxa.com main page is 5.5 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. 65% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 29.3 kB

  • Original 36.9 kB
  • After minification 31.8 kB
  • After compression 7.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 5.1 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 29.3 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 295.4 kB

  • Original 5.2 MB
  • After minification 4.9 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. Aeaxa images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 54.1 kB

  • Original 246.1 kB
  • After minification 220.1 kB
  • After compression 192.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 54.1 kB or 22% of the original size.

CSS Optimization

-24%

Potential reduce by 26.5 kB

  • Original 111.5 kB
  • After minification 111.5 kB
  • After compression 84.9 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. Aeaxa.com needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (43%)

Requests Now

51

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aeaxa.com

aeaxa.com

384 ms

aeaxa.com

aeaxa.com

412 ms

js

js

75 ms

esi2.css

esi2.css

92 ms

jquery.js

jquery.js

244 ms

wpens-public.js

wpens-public.js

243 ms

bootstrap.min.css

bootstrap.min.css

328 ms

font-awesome.min.css

font-awesome.min.css

252 ms

aoyun.css

aoyun.css

253 ms

swiper.min.css

swiper.min.css

254 ms

animate.css

animate.css

323 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

324 ms

esi2_1.css

esi2_1.css

409 ms

jquery-3.1.0.min.js

jquery-3.1.0.min.js

485 ms

popper.min.js

popper.min.js

346 ms

bootstrap.min.js

bootstrap.min.js

487 ms

owl.carousel.js

owl.carousel.js

402 ms

owlcarousel2-filter.min.js

owlcarousel2-filter.min.js

405 ms

custom.js

custom.js

505 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

503 ms

wp-embed.min.js

wp-embed.min.js

503 ms

popper.min.js

popper.min.js

504 ms

bootstrap.min.js

bootstrap.min.js

514 ms

wow.min.js

wow.min.js

561 ms

aoyun.js

aoyun.js

564 ms

swiper.min.js

swiper.min.js

568 ms

en.png

en.png

252 ms

icon_flag_ru.png

icon_flag_ru.png

253 ms

1648004841348436.jpg

1648004841348436.jpg

469 ms

1648786366753913.jpg

1648786366753913.jpg

700 ms

1648704477482150.jpg

1648704477482150.jpg

544 ms

1647683849713913.png

1647683849713913.png

627 ms

1647586066854332.png

1647586066854332.png

706 ms

1647586048578067.png

1647586048578067.png

549 ms

1647586058973516.png

1647586058973516.png

550 ms

1647586061964823.png

1647586061964823.png

627 ms

1647673363283764.jpg

1647673363283764.jpg

711 ms

1647588114605760.gif

1647588114605760.gif

633 ms

1647588120745347.gif

1647588120745347.gif

708 ms

1647588122729673.jpg

1647588122729673.jpg

708 ms

1647588343333141.png

1647588343333141.png

792 ms

1647758519863473.png

1647758519863473.png

780 ms

1647588388380831.png

1647588388380831.png

789 ms

1647758513601787.png

1647758513601787.png

788 ms

banner_curve.png

banner_curve.png

690 ms

beach-waves-loop.jpg

beach-waves-loop.jpg

691 ms

1647855788740674.jpg

1647855788740674.jpg

762 ms

fb.png

fb.png

770 ms

ins.png

ins.png

772 ms

youtube.png

youtube.png

773 ms

te.png

te.png

773 ms

in.png

in.png

735 ms

code.php

code.php

820 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

810 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

799 ms

1697528548646259.png

1697528548646259.png

462 ms

Accessibility Review

aeaxa.com accessibility score

81

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

Image elements do not have [alt] attributes

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

aeaxa.com 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

aeaxa.com SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aeaxa.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Aeaxa.com 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

aeaxa.com

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