10.5 sec in total
891 ms
9.5 sec
154 ms
Welcome to ecom.axa.com.sg homepage info - get ready to check Ecom AXA best content for Singapore right away, or after learning these important things about ecom.axa.com.sg
AXA Singapore is one of the world's leading insurance companies. We Provide innovative insurance solutions for both personal and business needs.
Visit ecom.axa.com.sgWe analyzed Ecom.axa.com.sg page load time and found that the first response time was 891 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ecom.axa.com.sg performance score
891 ms
715 ms
1213 ms
37 ms
542 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 65% of them (66 requests) were addressed to the original Ecom.axa.com.sg, 6% (6 requests) were made to Google-analytics.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Cdev-c-la9cs-salesforceliveagent-com.proactive-uat.axa.com.sg.
Page size can be reduced by 2.1 MB (78%)
2.8 MB
621.6 kB
In fact, the total size of Ecom.axa.com.sg main page is 2.8 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. 45% of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 380.5 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 380.5 kB or 91% of the original size.
Potential reduce by 74 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. Obviously, Ecom AXA needs image optimization as it can save up to 74 B or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.8 MB
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 1.8 MB or 75% of the original size.
Number of requests can be reduced by 73 (82%)
89
16
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecom AXA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
ecom.axa.com.sg
891 ms
ecom.axa.com.sg
715 ms
1213 ms
bootstrap.css
37 ms
angular-material.min.css
542 ms
daterangepicker.css
515 ms
style.css
569 ms
importer.css
586 ms
importer_.css
587 ms
api.js
49 ms
tc_directsales_header.js
95 ms
moment.min.js
765 ms
underscore-min.js
689 ms
jquery.min.js
876 ms
angular.min.js
1099 ms
angular-animate.min.js
839 ms
angular-aria.min.js
804 ms
angular-material.min.js
1373 ms
algoliasearch.angular.min.js
1165 ms
angular-messages.min.js
990 ms
angular-route.min.js
1090 ms
angular-credit-cards.js
1048 ms
angular-base64.js
1177 ms
mdPickers.js
1221 ms
daterangepicker.js
1312 ms
angular-daterangepicker.js
1309 ms
zz-extend-daterangepicker.js
1393 ms
ng-device-detector.min.js
1363 ms
re-tree.js
1426 ms
angular-load.min.js
1514 ms
crypto-js.js
1712 ms
app.js
1582 ms
directConfig.js
1578 ms
miscCtrl.js
1605 ms
agentCtrl.js
1633 ms
AppCtrl.js
1697 ms
addonCtrl.js
1752 ms
offerCtrl.js
1768 ms
policyCtrl.js
1860 ms
paymentCtrl.js
1812 ms
gtom.js
1911 ms
tc_directsales_footer.js
89 ms
deployment.js
3555 ms
livechat.css
1905 ms
inspectlet.js
22 ms
marketingFactory.js
1459 ms
offerFactory.js
1435 ms
planFactory.js
1460 ms
policyFactory.js
1506 ms
recaptcha__en.js
23 ms
productFactory.js
1533 ms
1824077748
53 ms
emailFactory.js
1412 ms
tagCommanderFactory.js
1444 ms
bcFactory.js
1384 ms
carFactory.js
1452 ms
SourceSansPro-Regular.otf
1937 ms
SourceSansPro-Light.otf
1679 ms
SourceSansPro-Bold.otf
1820 ms
analytics.js
27 ms
hotjar-411261.js
220 ms
css
73 ms
collect
18 ms
collect
49 ms
hit.xiti
12 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
48 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
32 ms
reach
545 ms
home.html
187 ms
MultiNoun.jsonp
2632 ms
visit-data
1130 ms
icomoon.ttf
963 ms
icomoon.ttf
963 ms
reach
1054 ms
arrow_right.svg
891 ms
agent_icon.svg
904 ms
mail.svg
906 ms
call_back.svg
945 ms
call_us.svg
927 ms
email_quote.svg
1065 ms
activityi;src=3573034;type=lp0;cat=axamo0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=5928653276059.776
664 ms
fbevents.js
643 ms
collect
625 ms
hit.xiti
623 ms
person.svg
722 ms
warning.svg
768 ms
remove.svg
728 ms
add_person.svg
736 ms
collect
257 ms
collect
257 ms
collect
259 ms
axa_logo_m.png
769 ms
calender_icon.png
851 ms
collect
13 ms
281637975519856
46 ms
visit-data
210 ms
conversion.js
52 ms
37 ms
36 ms
68 ms
20 ms
ecom.axa.com.sg SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecom.axa.com.sg 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 Ecom.axa.com.sg 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.
ecom.axa.com.sg
Open Graph description is not detected on the main page of Ecom AXA. 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: