12.2 sec in total
841 ms
10.9 sec
436 ms
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.jpWe analyzed Metlife.co.jp page load time and found that the first response time was 841 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
metlife.co.jp performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value18.0 s
0/100
25%
Value9.9 s
10/100
10%
Value6,530 ms
0/100
30%
Value0.041
99/100
15%
Value24.8 s
0/100
10%
841 ms
30 ms
360 ms
543 ms
552 ms
Our browser made a total of 183 requests to load all elements on the main page. We found that 86% of them (157 requests) were addressed to the original Metlife.co.jp, 3% (5 requests) were made to Cdn.clicktale.net and 2% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Metlife.co.jp.
Page size can be reduced by 829.7 kB (26%)
3.2 MB
2.3 MB
In fact, the total size of Metlife.co.jp main page is 3.2 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 43.8 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 43.8 kB or 73% of the original size.
Potential reduce by 224.2 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.
Potential reduce by 460.3 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 460.3 kB or 67% of the original size.
Potential reduce by 101.5 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 101.5 kB or 86% of the original size.
Number of requests can be reduced by 52 (29%)
182
130
The browser has sent 182 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 33 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
metlife.co.jp
841 ms
6d2d4394-3089-4366-bedb-ad39ea2fff40.js
30 ms
reset.css
360 ms
template.css
543 ms
base.css
552 ms
colorbox.css
371 ms
colorbox.css
402 ms
module.css
753 ms
index.css
743 ms
bookmark.css
573 ms
jquery-1.3.2.min.js
1364 ms
jquery.js
1440 ms
template.js
917 ms
common.js
773 ms
jquery.colorbox.js
1150 ms
jquery.colorbox.js
932 ms
reqOpen.js
971 ms
jquery.bxslider.js
1790 ms
index.js
1110 ms
estimateOpen.js
1166 ms
pressList.js
1289 ms
header_bookmark.js
1335 ms
View.js
1196 ms
mbox.js
2322 ms
telinfo.js
1344 ms
getseal
91 ms
widgets.js
104 ms
s_code.js
1573 ms
GoogleAnalytics.js
1188 ms
iSearchSuggest.js
1244 ms
logo.png
235 ms
cmn_nav_01.png
398 ms
cmn_nav_02.png
237 ms
cmn_nav_03.png
204 ms
cmn_nav_04.png
234 ms
cmn_nav_05.png
204 ms
cmn_nav_06.png
397 ms
cmn_nav_07.png
398 ms
cmn_bg_01.png
413 ms
cmn_btn_01.png
399 ms
index_bnr_earthquake_01.png
433 ms
index_bg_13.png
4054 ms
index_bnr_main_rating.jpg
2829 ms
index_bnr_main_cx.png
1990 ms
index_bnr_main_kakuritsu.jpg
1126 ms
index_bnr_main_cx_03.png
1565 ms
index_bnr_main_eservice_campaign.jpg
1873 ms
index_bnr_main_metlifeclub.png
1678 ms
index_bnr_main_online.jpg
3110 ms
index_bnr_main_est.png
2601 ms
index_bnr_main_csr.png
4553 ms
index_btn_01.png
2174 ms
index_btn_02.png
2358 ms
index_img_09.png
2543 ms
index_img_10.png
2726 ms
index_img_08.png
3152 ms
index_ttl_01.png
2908 ms
index_img_osusumeRank01.png
3007 ms
index_ttl_02.png
3090 ms
index_img_osusumeRank02.png
3188 ms
index_ttl_03.png
3272 ms
index_img_osusumeRank03.png
3307 ms
index_txt_07.png
3338 ms
index_txt_08.png
3366 ms
index_txt_09.png
3452 ms
index_txt_10.png
3480 ms
standard
44 ms
tag.js
8 ms
analytics.js
52 ms
ga.js
76 ms
search_tool_n1.js
399 ms
6d2d4394-3089-4366-bedb-ad39ea2fff40.js
47 ms
like.php
218 ms
index_btn_02.png
3330 ms
olb_campaign_d.gif
3523 ms
6d2d4394-3089-4366-bedb-ad39ea2fff40.js
69 ms
WRf4.js
25 ms
collect
180 ms
collect
144 ms
index_bnr_about_01.png
3942 ms
index_bnr_about_02.png
3475 ms
index_bnr_about_03.png
3488 ms
__utm.gif
154 ms
17.gif
410 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
164 ms
rU2ubZ6l1Q5.js
177 ms
LVx-xkvaJ0b.png
194 ms
s51310954049695
82 ms
index_ic_11.png
3518 ms
index_ic_10.png
3516 ms
index_txt_02.png
4028 ms
index_txt_03.png
3707 ms
index_bnr_01.png
3670 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
58 ms
i_search_assist_n1.js
355 ms
ac.css
335 ms
WRf4b.js
3 ms
53 ms
jot
99 ms
index_bnr_02.png
3112 ms
index_bnr_03.png
2929 ms
index_bnr_04.png
2748 ms
index_bnr_15.png
2679 ms
index_btn_17.png
2554 ms
index_btn_09.png
2491 ms
index_btn_07.png
2343 ms
index_btn_08.png
2183 ms
index_btn_23.png
2080 ms
index_btn_12.png
2015 ms
index_btn_13.png
1938 ms
index_img_06.png
1878 ms
index_img_01.png
1815 ms
index_img_07.png
1742 ms
index_btn_14.png
1705 ms
index_btn_21.png
1702 ms
index_btn_15.png
1701 ms
index_btn_16.png
1725 ms
index_btn_22.png
1633 ms
index_bnr_08.jpg
2784 ms
index_bnr_12.png
1638 ms
index_btn_18.png
1632 ms
index_btn_19.png
1588 ms
index_img_05.png
1585 ms
copyright_01.png
1584 ms
copyright_03.png
1453 ms
index_bg_01.png
1470 ms
index_bg_03.png
1509 ms
index_ic_02.png
1362 ms
index_ic_01.png
1397 ms
index_bg_06.png
1289 ms
index_bg_07.png
1276 ms
index_ic_03.png
1306 ms
index_ic_04.png
1286 ms
index_ic_05.png
1274 ms
index_ic_06.png
1230 ms
index_ic_07.png
1253 ms
index_ic_08.png
1251 ms
index_bg_osusume.gif
1216 ms
index_bg_17.png
1277 ms
index_bg_16.png
1222 ms
index_bg_09.png
1233 ms
index_ic_09.png
1254 ms
cmn_ic_05.png
1270 ms
index_bg_02.png
1264 ms
cmn_ic_01.png
1281 ms
index_bg_14.png
1272 ms
cmn_ic_02.png
1266 ms
index_bg_10.png
1281 ms
index_bg_11.png
1310 ms
index_bg_12.png
1306 ms
index_bg_15.png
1313 ms
cmn_bg_03.png
1682 ms
cmn_bg_02.png
1633 ms
index_ic_14.png
1326 ms
cmn_btn_cbox_01.gif
1312 ms
cmn_btn_cbox_02.gif
1299 ms
loading_background.png
1267 ms
loading.gif
1331 ms
cmn_nav_05_o.png
1377 ms
cmn_nav_06_o.png
1341 ms
cmn_nav_07_o.png
1310 ms
index_btn_01_o.png
1372 ms
index_btn_02_o.png
1607 ms
olb_campaign_d_o.gif
2418 ms
index_bnr_about_01_o.png
1940 ms
index_bnr_about_02_o.png
1353 ms
index_bnr_about_03_o.png
1308 ms
index_btn_17_o.png
1331 ms
index_btn_09_o.png
1402 ms
index_btn_07_o.png
1399 ms
index_btn_08_o.png
1404 ms
index_btn_23_o.png
1472 ms
index_btn_12_o.png
1454 ms
index_btn_13_o.png
1408 ms
index_btn_14_o.png
1440 ms
index_btn_21_o.png
1531 ms
index_btn_15_o.png
1485 ms
index_btn_16_o.png
1479 ms
index_btn_22_o.png
1448 ms
btn_bookmark.png
1574 ms
index_ic_12.png
1524 ms
index_ic_13.png
1494 ms
print.css
204 ms
metlife.co.jp 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 are not valid or misspelled
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
Image elements do not have [alt] attributes
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.
metlife.co.jp 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
Browser errors were logged to the console
Page has valid source maps
metlife.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
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 shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
metlife.co.jp
Open Graph data is detected on the main page of Metlife. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: