Tools & Wizards About Us
207207.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

207207.jp

海外旅行保険 | 人気のおすすめ11社を徹底比較【ｉ保険】

Page Load Speed

7 sec in total

First Response

1.2 sec

Resources Loaded

5.6 sec

Page Rendered

276 ms

207207.jp screenshot

About Website

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

海外旅行保険の最新人気ランキングやおすすめプランを徹底比較！保険金額・補償内容・各社の特長などから保険をお選びいただけます。人気複数社の保険料や補償内容を一括比較できる業界No.1のシステム！海外旅行保険の相談・見積り・資料請求は無料。海外旅行保険の比較は【ｉ保険】

Visit 207207.jp

Key Findings

We analyzed 207207.jp page load time and found that the first response time was 1.2 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

207207.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

207207.jp

1162 ms

import.css

388 ms

rollover.js

393 ms

common.js

394 ms

jquery.js

1158 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 91% of them (105 requests) were addressed to the original 207207.jp, 2% (2 requests) were made to Seal.globalsign.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain 207207.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 248.3 kB (34%)

Content Size

735.1 kB

After Optimization

486.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 207207.jp main page is 735.1 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. 30% of websites need less resources to load. Images take 429.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 28.6 kB

  • Original 36.4 kB
  • After minification 33.7 kB
  • After compression 7.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 28.6 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 33.4 kB

  • Original 429.4 kB
  • After minification 396.0 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. 207207 images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 90.8 kB

  • Original 161.1 kB
  • After minification 156.3 kB
  • After compression 70.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 90.8 kB or 56% of the original size.

CSS Optimization

-88%

Potential reduce by 95.5 kB

  • Original 108.3 kB
  • After minification 83.6 kB
  • After compression 12.7 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. 207207.jp needs all CSS files to be minified and compressed as it can save up to 95.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (17%)

Requests Now

112

After Optimization

93

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

207207.jp

207207.jp

1162 ms

import.css

import.css

388 ms

rollover.js

rollover.js

393 ms

common.js

common.js

394 ms

jquery.js

jquery.js

1158 ms

script.js

script.js

594 ms

sp.js

sp.js

575 ms

smoothscroll.js

smoothscroll.js

765 ms

ga.js

ga.js

577 ms

sp_btn.js

sp_btn.js

750 ms

gs_image_130-66_ja.js

gs_image_130-66_ja.js

6 ms

reset.css

reset.css

381 ms

style.css

style.css

801 ms

serect.css

serect.css

994 ms

pulldown.css

pulldown.css

554 ms

insurance.css

insurance.css

1135 ms

features.css

features.css

570 ms

info.css

info.css

743 ms

faq.css

faq.css

759 ms

ihoken.css

ihoken.css

933 ms

conversion.js

conversion.js

16 ms

analytics.js

analytics.js

32 ms

gs_noscript_130-66_ja.gif

gs_noscript_130-66_ja.gif

30 ms

logo.gif

logo.gif

192 ms

head_img01.gif

head_img01.gif

192 ms

gnavi_btn01_off.jpg

gnavi_btn01_off.jpg

194 ms

gnavi_btn02_off.jpg

gnavi_btn02_off.jpg

382 ms

gnavi_btn03_off.jpg

gnavi_btn03_off.jpg

193 ms

gnavi_btn04_off.jpg

gnavi_btn04_off.jpg

200 ms

gnavi_btn05_off.jpg

gnavi_btn05_off.jpg

380 ms

gnavi_btn06_off.jpg

gnavi_btn06_off.jpg

384 ms

top_view_btn01_off.jpg

top_view_btn01_off.jpg

576 ms

com_bnr_tel01.jpg

com_bnr_tel01.jpg

769 ms

top_title02.gif

top_title02.gif

395 ms

top_toko_btn01_off.gif

top_toko_btn01_off.gif

570 ms

top_toko_btn02_off.gif

top_toko_btn02_off.gif

571 ms

top_toko_btn03_off.gif

top_toko_btn03_off.gif

573 ms

top_toko_btn04_off.gif

top_toko_btn04_off.gif

591 ms

top_toko_btn05_off.gif

top_toko_btn05_off.gif

758 ms

top_toko_btn06_off.gif

top_toko_btn06_off.gif

760 ms

top_toko_btn07_off.gif

top_toko_btn07_off.gif

762 ms

top_title03.gif

top_title03.gif

764 ms

com_ins_logo_aiu_off.gif

com_ins_logo_aiu_off.gif

786 ms

com_ins_logo_ji_off.gif

com_ins_logo_ji_off.gif

947 ms

com_ins_logo_ms_off.gif

com_ins_logo_ms_off.gif

948 ms

com_ins_logo_tk_off.gif

com_ins_logo_tk_off.gif

949 ms

com_ins_logo_ace_off.gif

com_ins_logo_ace_off.gif

950 ms

com_ins_logo_sjnk_off.gif

com_ins_logo_sjnk_off.gif

960 ms

com_ins_logo_aioi_off.gif

com_ins_logo_aioi_off.gif

983 ms

com_ins_logo_hs_off.gif

com_ins_logo_hs_off.gif

1136 ms

com_ins_logo_fk_off.gif

com_ins_logo_fk_off.gif

1138 ms

top_title04.gif

top_title04.gif

1140 ms

top_title05.gif

top_title05.gif

1140 ms

top_img01.jpg

top_img01.jpg

1151 ms

top_title07.gif

top_title07.gif

1178 ms

top_rank_title01.jpg

top_rank_title01.jpg

1326 ms

top_rank_title02.gif

top_rank_title02.gif

1326 ms

ins_logo_sjnk_off.gif

ins_logo_sjnk_off.gif

1328 ms

ins_logo_ms_off.gif

ins_logo_ms_off.gif

1311 ms

collect

collect

33 ms

collect

collect

67 ms

49 ms

siteSeal.do

siteSeal.do

618 ms

37 ms

ins_logo_ji_off.gif

ins_logo_ji_off.gif

1162 ms

top_rank_title03.gif

top_rank_title03.gif

1192 ms

ins_logo_aiu_off.gif

ins_logo_aiu_off.gif

1333 ms

ins_logo_tm_off.gif

ins_logo_tm_off.gif

1332 ms

ins_logo_ace_off.gif

ins_logo_ace_off.gif

1329 ms

top_rank_title04.gif

top_rank_title04.gif

1148 ms

top_rank_title05.gif

top_rank_title05.gif

1163 ms

top_rank_title06.gif

top_rank_title06.gif

1195 ms

top_rank_title07.gif

top_rank_title07.gif

1319 ms

isms.gif

isms.gif

1143 ms

17001945_01_85_jp.gif

17001945_01_85_jp.gif

1143 ms

snavi_btn_request_off.jpg

snavi_btn_request_off.jpg

1333 ms

snavi_bnr_ihoken_off.jpg

snavi_bnr_ihoken_off.jpg

1162 ms

snavi_title01_off.gif

snavi_title01_off.gif

1187 ms

siteSealImage.do

siteSealImage.do

188 ms

snavi_title02_off.gif

snavi_title02_off.gif

1141 ms

snavi_title03_off.gif

snavi_title03_off.gif

1142 ms

snavi_title04_off.gif

snavi_title04_off.gif

1143 ms

snavi_bnr_tel.jpg

snavi_bnr_tel.jpg

1355 ms

snavi_bnr_kasai_off.jpg

snavi_bnr_kasai_off.jpg

1207 ms

snavi_bnr_medi_off.jpg

snavi_bnr_medi_off.jpg

1307 ms

snavi_bnr_car_off.jpg

snavi_bnr_car_off.jpg

1337 ms

snavi_bnr_bike_off.jpg

snavi_bnr_bike_off.jpg

1147 ms

snavi_bnr_pet_off.jpg

snavi_bnr_pet_off.jpg

1147 ms

bnr_cycle_off.png

bnr_cycle_off.png

1220 ms

bnr_golf_off.png

bnr_golf_off.png

1322 ms

footer_pagetop_off.gif

footer_pagetop_off.gif

1303 ms

head_icon01.gif

head_icon01.gif

1149 ms

head_icon02.gif

head_icon02.gif

1173 ms

gnavi_bg01.jpg

gnavi_bg01.jpg

1226 ms

pan_bg01.jpg

pan_bg01.jpg

1331 ms

pan_icon01.gif

pan_icon01.gif

1322 ms

top_view_bg01.jpg

top_view_bg01.jpg

1868 ms

top_tokucho_btn_off.jpg

top_tokucho_btn_off.jpg

1151 ms

top_info_btn01_off.jpg

top_info_btn01_off.jpg

1178 ms

top_info_btn02_off.jpg

top_info_btn02_off.jpg

1234 ms

top_info_btn03_off.jpg

top_info_btn03_off.jpg

1333 ms

top_info_btn04_off.jpg

top_info_btn04_off.jpg

1320 ms

top_info_btn05_off.jpg

top_info_btn05_off.jpg

1293 ms

top_info_btn06_off.jpg

top_info_btn06_off.jpg

1368 ms

top_info_btn07_off.jpg

top_info_btn07_off.jpg

1240 ms

top_info_btn08_off.jpg

top_info_btn08_off.jpg

1332 ms

top_rank_bg02.gif

top_rank_bg02.gif

1334 ms

top_rank_bg01.gif

top_rank_bg01.gif

1320 ms

snavi_icon01.gif

snavi_icon01.gif

1385 ms

snavi_icon02.gif

snavi_icon02.gif

1338 ms

snavi_icon03.gif

snavi_icon03.gif

1337 ms

snavi_icon04.gif

snavi_icon04.gif

1339 ms

snavi_btn_faq_off.jpg

snavi_btn_faq_off.jpg

1542 ms

snavi_btn_glossary_off.jpg

snavi_btn_glossary_off.jpg

1383 ms

bnr_aflac_cp_off.jpg

bnr_aflac_cp_off.jpg

1526 ms

Accessibility Review

207207.jp accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

207207.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

207207.jp SEO score

99

Search Engine Optimization Advices

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 207207.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 207207.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

207207.jp

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