Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

axiory.com

Trade Forex | CFDs & Exchange Products | Axiory Global

Page Load Speed

1.3 sec in total

First Response

231 ms

Resources Loaded

767 ms

Page Rendered

347 ms

axiory.com screenshot

About Website

Welcome to axiory.com homepage info - get ready to check Axiory best content for South Africa right away, or after learning these important things about axiory.com

Trade FX, CFDs and invest in Stocks and ETFs with a leading, multi-asset, award-winning, Forex broker. Discover Axiory Today.

Visit axiory.com

Key Findings

We analyzed Axiory.com page load time and found that the first response time was 231 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

axiory.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value3,980 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

axiory.com

231 ms

css_cm_TfMqXkBxBdXWAhaHXr5pRMteEVrw_swuzyqQ-aok.css

128 ms

modernizr-2.5.3-respond-1.1.0.min.js

79 ms

jquery.min.js

30 ms

jquery.cycle.all.js

82 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 66% of them (29 requests) were addressed to the original Axiory.com, 7% (3 requests) were made to Assets1.chat.freshdesk.com and 7% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (352 ms) belongs to the original domain Axiory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 662.6 kB (35%)

Content Size

1.9 MB

After Optimization

1.2 MB

In fact, the total size of Axiory.com main page is 1.9 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. 55% of websites need less resources to load. Images take 935.2 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 15.3 kB

  • Original 24.1 kB
  • After minification 23.4 kB
  • After compression 8.8 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 15.3 kB or 63% of the original size.

Image Optimization

-2%

Potential reduce by 21.5 kB

  • Original 935.2 kB
  • After minification 913.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. Axiory images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 275.4 kB

  • Original 522.3 kB
  • After minification 484.5 kB
  • After compression 246.9 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 275.4 kB or 53% of the original size.

CSS Optimization

-90%

Potential reduce by 350.4 kB

  • Original 388.6 kB
  • After minification 387.5 kB
  • After compression 38.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. Axiory.com needs all CSS files to be minified and compressed as it can save up to 350.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (42%)

Requests Now

43

After Optimization

25

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

Accessibility Review

axiory.com accessibility score

89

Accessibility Issues

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.

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 valid value for its [lang] attribute.

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

Links do not have a discernible name

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

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

Missing source maps for large first-party JavaScript

SEO Factors

axiory.com SEO score

83

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

Document doesn't have a valid hreflang

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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