Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

metlife.co.jp

保険・生命保険のメットライフ生命

Page Load Speed

4.4 sec in total

First Response

409 ms

Resources Loaded

3.8 sec

Page Rendered

215 ms

About Website

Welcome to metlife.co.jp homepage info - get ready to check Metlife best content for Japan right away, or after learning these important things about metlife.co.jp

メットライフ生命の公式サイトです。医療保険、死亡保険（生命保険）、外貨建保険、ガン保険、個人年金保険など各種保険商品のご紹介やご契約後のお手続き・サービス、企業情報をご案内します。

Visit metlife.co.jp

Key Findings

We analyzed Metlife.co.jp page load time and found that the first response time was 409 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

metlife.co.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value26.6 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

metlife.co.jp

409 ms

www.metlife.co.jp

1019 ms

css

53 ms

ja.min.css

20 ms

global.min.css

37 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 92% of them (61 requests) were addressed to the original Metlife.co.jp, 5% (3 requests) were made to Cache.dga.jp and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cache.dga.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.1 kB (53%)

Content Size

710.4 kB

After Optimization

337.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metlife.co.jp main page is 710.4 kB. 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. Javascripts take 473.1 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 146.6 kB

  • Original 162.8 kB
  • After minification 113.6 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 49.2 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 146.6 kB or 90% of the original size.

Image Optimization

-10%

Potential reduce by 7.4 kB

  • Original 72.1 kB
  • After minification 64.7 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. Metlife images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 218.3 kB

  • Original 473.1 kB
  • After minification 466.2 kB
  • After compression 254.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 218.3 kB or 46% of the original size.

CSS Optimization

-33%

Potential reduce by 795 B

  • Original 2.4 kB
  • After minification 2.3 kB
  • After compression 1.6 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. Metlife.co.jp needs all CSS files to be minified and compressed as it can save up to 795 B or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (71%)

Requests Now

63

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

metlife.co.jp accessibility score

70

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

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

High

Image elements do not have [alt] attributes

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

metlife.co.jp best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

metlife.co.jp SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

Open Graph description is not detected on the main page of Metlife. 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: