3.6 sec in total
252 ms
3.1 sec
178 ms
Click here to check amazing AXA content for Mexico. Otherwise, check out these important facts you probably never knew about axa.com.mx
Entra al sitio oficial de AXA México, encuentra y cotiza en línea el seguro que necesitas. ¡No esperes más y obtén aquí un seguro a tu medida!
Visit axa.com.mxWe analyzed Axa.com.mx page load time and found that the first response time was 252 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
axa.com.mx performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value12.0 s
0/100
25%
Value8.5 s
18/100
10%
Value1,120 ms
23/100
30%
Value0.678
8/100
15%
Value18.6 s
3/100
10%
252 ms
363 ms
273 ms
266 ms
144 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Axa.com.mx, 8% (12 requests) were made to Apis.google.com and 4% (6 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Axa.mx.
Page size can be reduced by 1.7 MB (60%)
2.8 MB
1.1 MB
In fact, the total size of Axa.com.mx 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 89.2 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 89.2 kB or 77% of the original size.
Potential reduce by 109.1 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. Obviously, AXA needs image optimization as it can save up to 109.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 974.6 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 974.6 kB or 72% of the original size.
Potential reduce by 500.4 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. Axa.com.mx needs all CSS files to be minified and compressed as it can save up to 500.4 kB or 84% of the original size.
Number of requests can be reduced by 80 (58%)
139
59
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 51 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
axa.mx
252 ms
home
363 ms
aui.css
273 ms
main.css
266 ms
main.css
144 ms
main.css
139 ms
main.css
144 ms
main.css
148 ms
main.css
192 ms
main.css
200 ms
main.css
206 ms
barebone.jsp
495 ms
main.js
243 ms
main.js
254 ms
main.js
283 ms
navigation.js
294 ms
main.css
471 ms
jquery-1.9.1.js
484 ms
jquery-ui-1.9.2.min.js
439 ms
jquery.bxslider.min.js
338 ms
scripts.js
332 ms
jquery.anoslide.js
374 ms
jQuery.succinct.js
378 ms
jquery.bxslider.css
420 ms
main.js
364 ms
main.js
405 ms
platform.js
92 ms
bootstrap-tab.js
410 ms
gtm.js
167 ms
sdk.js
51 ms
widgets.js
208 ms
headerLogo.png
51 ms
caret.png
147 ms
2bcfb6b9-cf1c-40d4-88c1-962b22e34b9e
196 ms
b5959cde-9065-4dee-a10a-116167339c2d
196 ms
18f818c0-5464-4e07-8c45-8772c8fbd81f
197 ms
38ab10dc-395e-439e-8d64-73be8fa51bd7
197 ms
36aa087f-fa8b-4e1f-bcac-35162983e0bd
195 ms
bc38a107-e66f-4cb4-b2cf-d125918b3a43
197 ms
icon_header_menu.png
268 ms
849bc0c2-c24a-4fbd-8cf6-fb2cbc852e45
269 ms
arrow_white.png
268 ms
060031a3-ab11-4f91-9dd4-6b39458f5109.woff
252 ms
b547d31d-69fc-40d6-8013-e9b6f0b38df0.woff
253 ms
a9c64705-3910-46f2-9bab-112f11a58b50
316 ms
bgBlueTransp.png
318 ms
86af120c-a8e0-4b37-97de-4541f8b97cd3
318 ms
6b07dfcd-c2ae-4351-b59c-50bee1f2823f
362 ms
bgAccordionUp.png
317 ms
11643218-d809-48ea-8afb-61b0ba6b9a54
315 ms
ae99c963-7dfe-438b-9e4b-666bb1120c70
396 ms
8af65cce-7225-4350-84b6-a73e88602d3a
372 ms
cb46afeb-183f-46dd-b834-300928279615
372 ms
d6e47260-b1df-4b57-9e52-421badcfc859
420 ms
26d4a99c-ddb6-4c3b-9fb5-eb7996512fad
413 ms
a4835f5f-3ee7-4c92-9261-3155107092e9
473 ms
6936cc44-3db4-4101-a3fc-37fc40e08c0a
534 ms
6da3197c-deb6-44bb-ad69-b861fd143a91
533 ms
bcdc7077-79ba-44e9-8510-89413d3a1bd8
534 ms
e365f385-2bdf-4a7b-8c21-26cf56e72c45
534 ms
6aac0266-defd-41b0-9e5c-904da1f9793b
534 ms
792f201c-30ef-4e02-a7e6-cf9263f9e1ed
1648 ms
00ca0e98-6de3-43ad-a882-684dfdda2cab
571 ms
b936cf0b-922b-4253-b663-5ee0eef0c7f5
570 ms
8a878a5c-1e14-472d-9f4e-2e19230285d2
570 ms
770009d3-74da-42c1-a5de-0ce9c567be46
570 ms
bbc15295-e002-4689-acc1-0e1497ceac43
570 ms
de902d7e-9849-4880-b8fe-966b186b110c.woff
614 ms
plusone.js
74 ms
cb=gapi.loaded_0
96 ms
cb=gapi.loaded_1
140 ms
subscribe_embed
286 ms
follow
261 ms
162 ms
519 ms
xd_arbiter.php
197 ms
cb=gapi.loaded_2
138 ms
analytics.js
203 ms
iMAWebCookie.js
251 ms
fbevents.js
77 ms
tm39325.js
399 ms
e1587520-72eb-4375-bf9c-39fc3cbb4840
474 ms
18cf3edc-5cce-4072-9980-5a6b5831afc9
474 ms
b92c18b5-2d48-4ff8-8a44-51769665f8c9
522 ms
2ae3137a-110c-40be-863f-4635b67ecf9e
560 ms
368f07f4-5abd-4c1d-a73a-d389462ada03
561 ms
like.php
181 ms
activityi;src=3868514;type=seguro02;cat=lpg_l000;ord=6407569833798;~oref=https%3A%2F%2Faxa.mx%2Fhome
239 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
85 ms
b7872892-2429-4424-9f88-c7eac2f06caa
507 ms
postmessageRelay
126 ms
e087cbd9-7395-4f47-a8f7-e0a4ae1144e6
460 ms
6cbcaaed-225b-4b73-ac52-049b30501fd9
548 ms
eb41cafa-0b37-4097-af34-2d531061cb09
551 ms
prev.png
531 ms
next.png
530 ms
69 ms
bgAccordionDown.png
468 ms
follow_button.6a78875565a912489e9aef879c881358.es.html
71 ms
rs=AGLTcCM2TygKB0mUTs1bvsRYQQZWb_gy-g
67 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
95 ms
rs=AGLTcCPilnfXxFZ9JhOdS0EZKHMQN50Ofg
127 ms
qbEHJxuVK5u.js
186 ms
LVx-xkvaJ0b.png
181 ms
api.js
106 ms
core:rpc:shindig.random:shindig.sha1.js
235 ms
2536007149-postmessagerelay.js
223 ms
www-subscribe-embed-vflWJjAep.css
222 ms
www-subscribe-embed.js
253 ms
collect
160 ms
collect
225 ms
collect
184 ms
info.json
242 ms
grlryt2bdKIyfMSOhzd1eA.woff
211 ms
d-QWLnp4didxos_6urzFtg.woff
261 ms
vxNK-E6B13CyehuDCmvQvw.woff
288 ms
pixel
59 ms
usr
194 ms
www-hitchhiker-vfluKv9vH.png
40 ms
ga-audiences
75 ms
ga-audiences
96 ms
cb=gapi.loaded_0
20 ms
sync
208 ms
188 ms
cb=gapi.loaded_3
21 ms
sync
74 ms
border_3.gif
9 ms
subscribe_embed
70 ms
spacer.gif
13 ms
bubbleSprite_3.png
24 ms
bubbleDropR_3.png
28 ms
bubbleDropB_3.png
29 ms
req
159 ms
jot
101 ms
www-subscribe-embed-card-vflqARhQ4.css
12 ms
www-subscribe-embed-card.js
15 ms
50 ms
available_languages.jsp
54 ms
74 ms
58 ms
112 ms
148 ms
82 ms
55 ms
nr-852.min.js
66 ms
ad06dcf1f1
121 ms
axa.com.mx accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role]s are not contained by their required parent element
[role] values are not valid
ARIA IDs are not unique
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
axa.com.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
axa.com.mx SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Axa.com.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Axa.com.mx 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.
axa.com.mx
Open Graph description is not detected on the main page of 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: