Axa.co.jp Site Title
アクサ生命保険株式会社
Axa.co.jp Meta Description
アクサ生命保険株式会社公式ホームページです。生命保険、医療保険、がん保険、持病をお持ちの方のための保険などの各種保険商品やアクサ生命の企業情報をご案内します。
Axa.co.jp Test Results
Axa.co.jp Mobile Performance: 4/100
Quick overview:
Avoid large layout shifts
6 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Max Potential First Input Delay
2,560 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
23.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
3.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Axa.co.jp Mobile SEO: 84/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links 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 how to make pages mobile-friendly.
Tap targets are not sized appropriately
79% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
Axa.co.jp Mobile Best Practices: 63/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Trust and Safety
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Axa.co.jp Mobile PWA: 88/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Axa.co.jp Mobile Accessibility: 86/100
Quick overview:
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.axa.com
www.axa.net
www.axa.org
www.axa.info
www.axa.biz
www.axa.us
www.axa.mobi
www.xa.co.jp
www.axa.co.jp
www.qxa.co.jp
www.aqxa.co.jp
www.qaxa.co.jp
www.wxa.co.jp
www.awxa.co.jp
www.waxa.co.jp
www.sxa.co.jp
www.asxa.co.jp
www.saxa.co.jp
www.zxa.co.jp
www.azxa.co.jp
www.zaxa.co.jp
www.aa.co.jp
www.aza.co.jp
www.axza.co.jp
www.asa.co.jp
www.axsa.co.jp
www.ada.co.jp
www.axda.co.jp
www.adxa.co.jp
www.aca.co.jp
www.axca.co.jp
www.acxa.co.jp
www.ax.co.jp
www.axq.co.jp
www.axaq.co.jp
www.axqa.co.jp
www.axw.co.jp
www.axaw.co.jp
www.axwa.co.jp
www.axs.co.jp
www.axas.co.jp
www.axz.co.jp
www.axaz.co.jp
www.axa.net
www.axa.org
www.axa.info
www.axa.biz
www.axa.us
www.axa.mobi
www.xa.co.jp
www.axa.co.jp
www.qxa.co.jp
www.aqxa.co.jp
www.qaxa.co.jp
www.wxa.co.jp
www.awxa.co.jp
www.waxa.co.jp
www.sxa.co.jp
www.asxa.co.jp
www.saxa.co.jp
www.zxa.co.jp
www.azxa.co.jp
www.zaxa.co.jp
www.aa.co.jp
www.aza.co.jp
www.axza.co.jp
www.asa.co.jp
www.axsa.co.jp
www.ada.co.jp
www.axda.co.jp
www.adxa.co.jp
www.aca.co.jp
www.axca.co.jp
www.acxa.co.jp
www.ax.co.jp
www.axq.co.jp
www.axaq.co.jp
www.axqa.co.jp
www.axw.co.jp
www.axaw.co.jp
www.axwa.co.jp
www.axs.co.jp
www.axas.co.jp
www.axz.co.jp
www.axaz.co.jp