3.3 sec in total
152 ms
2.6 sec
516 ms
Click here to check amazing Axsource content. Otherwise, check out these important facts you probably never knew about axsource.com
Visit axsource.comWe analyzed Axsource.com page load time and found that the first response time was 152 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
axsource.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value7.9 s
3/100
25%
Value9.7 s
11/100
10%
Value1,530 ms
13/100
30%
Value0.225
55/100
15%
Value14.5 s
9/100
10%
152 ms
321 ms
323 ms
33 ms
164 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 61% of them (34 requests) were addressed to the original Axsource.com, 25% (14 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Axsource.com.
Page size can be reduced by 179.1 kB (5%)
3.7 MB
3.5 MB
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. 70% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 179.0 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.0 kB or 87% of the original size.
Potential reduce by 0 B
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.
Potential reduce by 62 B
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.
Potential reduce by 0 B
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.
Number of requests can be reduced by 5 (13%)
38
33
The browser has sent 38 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 6 to 1 for JavaScripts and as a result speed up the page load time.
axsource.com
152 ms
www.axsource.com
321 ms
06f810759c81426eb3ef625ca7289dd9.css
323 ms
css
33 ms
jquery.min.js
164 ms
js
69 ms
76c496897e076896f9647a7f161096d0.js
277 ms
css
53 ms
gtm.js
115 ms
Axsource-Logo-Dark.svg
107 ms
Axsource-Logo.svg
135 ms
AX-HOme-Hero01-21.jpg
278 ms
home-mobile-4.jpg
218 ms
Axsource-Hero-Title-IMG-01.svg
247 ms
Ax-BG-01.svg
250 ms
Digital-Transformation-IMG-01-20.png
661 ms
CTA-arrow-0111.svg
304 ms
Regulatory20.png
508 ms
CTA-arrow-3.svg
301 ms
Abstract-NG011111.jpg
558 ms
Medical-Devices-IMG01.png
330 ms
Food-Beverage-IMGM.png
559 ms
Pharmaceuticals-iMG.png
509 ms
NHPs-OTCs-IMG.png
435 ms
Cannabis-IMG01.png
489 ms
Cosmetics-IMG01.png
542 ms
Hospitality-IMG.png
611 ms
API-IMGs.png
613 ms
Retail-IMG001.png
646 ms
Healthcare-IMG.png
776 ms
Vision-BG-01-1-scaled.jpg
818 ms
Joib-Axsource-BG01.jpg
716 ms
Footer-CTA-BG-01.jpg
776 ms
microsoft.webp
699 ms
SPL-SPM-labeling-768x378-1.webp
711 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_M-bw.ttf
66 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_M-bw.ttf
89 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_M-bw.ttf
91 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_M-bw.ttf
88 ms
icomoon.woff
684 ms
fontawesome-webfont.svg
868 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
90 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
90 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
89 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
91 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
91 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
92 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
92 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
92 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
92 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
93 ms
js
98 ms
analytics.js
35 ms
collect
42 ms
collect
24 ms
fontawesome-webfont.woff
158 ms
axsource.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
axsource.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
axsource.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
axsource.com
Open Graph description is not detected on the main page of Axsource. 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: