Tools & Wizards About Us
axsource.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

axsource.com

Empowering Digital Transformation with Microsoft D365

Page Load Speed

2.5 sec in total

First Response

112 ms

Resources Loaded

1.9 sec

Page Rendered

545 ms

axsource.com screenshot

About Website

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

Committed to providing powerful solutions based on rising technology and scripting corporate agility. Let us help you get there with our integrated solutions.

Visit axsource.com

Key Findings

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

Performance Metrics

axsource.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

axsource.com

112 ms

www.axsource.com

305 ms

68871ade87b81cb86c4a387aaa1880cd.css

169 ms

css

32 ms

jquery.min.js

159 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 84% of them (37 requests) were addressed to the original Axsource.com, 7% (3 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (502 ms) belongs to the original domain Axsource.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.7 kB (6%)

Content Size

3.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 208.7 kB

  • Original 238.0 kB
  • After minification 234.6 kB
  • After compression 29.3 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 208.7 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.1 MB
  • After minification 3.1 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. Axsource images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 192.8 kB
  • After minification 192.8 kB
  • After compression 192.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 184.3 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.

Requests Breakdown

Number of requests can be reduced by 8 (21%)

Requests Now

39

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

axsource.com

axsource.com

112 ms

www.axsource.com

www.axsource.com

305 ms

68871ade87b81cb86c4a387aaa1880cd.css

68871ade87b81cb86c4a387aaa1880cd.css

169 ms

css

css

32 ms

jquery.min.js

jquery.min.js

159 ms

js

js

68 ms

0f8b29b6534fd625fee404ab17cae771.js

0f8b29b6534fd625fee404ab17cae771.js

316 ms

css

css

40 ms

gtm.js

gtm.js

104 ms

Axsource-Logo-Dark.svg

Axsource-Logo-Dark.svg

75 ms

Axsource-Logo.svg

Axsource-Logo.svg

73 ms

AX-HOme-Hero01-21.jpg

AX-HOme-Hero01-21.jpg

143 ms

home-mobile-4.jpg

home-mobile-4.jpg

110 ms

Axsource-Hero-Title-IMG-01.svg

Axsource-Hero-Title-IMG-01.svg

111 ms

Ax-BG-01.svg

Ax-BG-01.svg

173 ms

Digital-Transformation-IMG-01-20.png

Digital-Transformation-IMG-01-20.png

360 ms

CTA-arrow-0111.svg

CTA-arrow-0111.svg

174 ms

AXSource-image-1.png

AXSource-image-1.png

363 ms

CTA-arrow-3.svg

CTA-arrow-3.svg

220 ms

Abstract-NG011111.jpg

Abstract-NG011111.jpg

222 ms

Medical-Devices-IMG01.png

Medical-Devices-IMG01.png

313 ms

Food-Beverage-IMGM.png

Food-Beverage-IMGM.png

315 ms

Pharmaceuticals-iMG.png

Pharmaceuticals-iMG.png

228 ms

NHPs-OTCs-IMG.png

NHPs-OTCs-IMG.png

258 ms

Cannabis-IMG01.png

Cannabis-IMG01.png

283 ms

Cosmetics-IMG01.png

Cosmetics-IMG01.png

312 ms

Hospitality-IMG.png

Hospitality-IMG.png

337 ms

API-IMGs.png

API-IMGs.png

367 ms

Retail-IMG001.png

Retail-IMG001.png

416 ms

Healthcare-IMG.png

Healthcare-IMG.png

420 ms

Vision-BG-01-1-scaled.jpg

Vision-BG-01-1-scaled.jpg

393 ms

Joib-Axsource-BG01.jpg

Joib-Axsource-BG01.jpg

420 ms

Footer-CTA-BG-01.jpg

Footer-CTA-BG-01.jpg

482 ms

logo.svg

logo.svg

425 ms

microsoft.webp

microsoft.webp

449 ms

twitter-icn-01-2.svg

twitter-icn-01-2.svg

473 ms

FB-icn-01-1.svg

FB-icn-01-1.svg

475 ms

Linked-in-icn-1.svg

Linked-in-icn-1.svg

476 ms

Yt-icn-01-1.svg

Yt-icn-01-1.svg

480 ms

SPL-SPM-labeling-768x378-1.webp

SPL-SPM-labeling-768x378-1.webp

502 ms

font

font

72 ms

font

font

95 ms

icomoon.woff

icomoon.woff

453 ms

font

font

94 ms

Accessibility Review

axsource.com accessibility score

84

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.

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

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

axsource.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

axsource.com SEO score

96

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

axsource.com

Open Graph data is detected on the main page of Axsource. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: