Tools & Wizards About Us
kenja-hoken.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kenja-hoken.co.jp

生命保険の比較・見直し・相談なら「賢者の生命保険」

Page Load Speed

4.5 sec in total

First Response

539 ms

Resources Loaded

3.8 sec

Page Rendered

186 ms

kenja-hoken.co.jp screenshot

About Website

Welcome to kenja-hoken.co.jp homepage info - get ready to check Kenja Hoken best content right away, or after learning these important things about kenja-hoken.co.jp

Visit kenja-hoken.co.jp

Key Findings

We analyzed Kenja-hoken.co.jp page load time and found that the first response time was 539 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

kenja-hoken.co.jp performance score

0

Network Requests Diagram

kenja-hoken.co.jp

539 ms

www.kenja-hoken.co.jp

1206 ms

import_index.css

343 ms

common.js

552 ms

gs_image_130-66_ja.js

6 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 92% of them (57 requests) were addressed to the original Kenja-hoken.co.jp, 3% (2 requests) were made to Seal.globalsign.com and 3% (2 requests) were made to Ssif1.globalsign.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Kenja-hoken.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.3 kB (22%)

Content Size

105.9 kB

After Optimization

82.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kenja-hoken.co.jp main page is 105.9 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. 20% of websites need less resources to load. Images take 76.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 10.7 kB

  • Original 14.3 kB
  • After minification 12.5 kB
  • After compression 3.7 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 1.9 kB, which is 13% 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 10.7 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 1.9 kB

  • Original 76.7 kB
  • After minification 74.8 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. Kenja Hoken images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 4.4 kB

  • Original 6.6 kB
  • After minification 5.4 kB
  • After compression 2.2 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 4.4 kB or 66% of the original size.

CSS Optimization

-77%

Potential reduce by 6.4 kB

  • Original 8.3 kB
  • After minification 6.1 kB
  • After compression 1.9 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. Kenja-hoken.co.jp needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (37%)

Requests Now

59

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kenja-hoken.co.jp

kenja-hoken.co.jp

539 ms

www.kenja-hoken.co.jp

www.kenja-hoken.co.jp

1206 ms

import_index.css

import_index.css

343 ms

common.js

common.js

552 ms

gs_image_130-66_ja.js

gs_image_130-66_ja.js

6 ms

start_bd.php

start_bd.php

887 ms

basic.css

basic.css

167 ms

main.css

main.css

173 ms

gs_noscript_130-66_ja.gif

gs_noscript_130-66_ja.gif

62 ms

bg.gif

bg.gif

167 ms

bg_content.gif

bg_content.gif

172 ms

bg_content_top.gif

bg_content_top.gif

181 ms

header_bg.gif

header_bg.gif

331 ms

logo_m.gif

logo_m.gif

342 ms

top_img.jpg

top_img.jpg

870 ms

btn_top_rules.gif

btn_top_rules.gif

717 ms

btn_top_profile.gif

btn_top_profile.gif

373 ms

sub_fq.gif

sub_fq.gif

370 ms

dashed.gif

dashed.gif

496 ms

q_s.gif

q_s.gif

511 ms

sub_interview.gif

sub_interview.gif

551 ms

thumb_interview_1.jpg

thumb_interview_1.jpg

554 ms

img_2.gif

img_2.gif

671 ms

sub_lifestage.gif

sub_lifestage.gif

682 ms

thumb_lifestage_1.jpg

thumb_lifestage_1.jpg

732 ms

h3_lifestage_1.gif

h3_lifestage_1.gif

733 ms

thumb_lifestage_2.jpg

thumb_lifestage_2.jpg

836 ms

h3_lifestage_2.gif

h3_lifestage_2.gif

866 ms

thumb_lifestage_3.jpg

thumb_lifestage_3.jpg

889 ms

h3_lifestage_3.gif

h3_lifestage_3.gif

911 ms

thumb_lifestage_4.jpg

thumb_lifestage_4.jpg

909 ms

h3_lifestage_4.gif

h3_lifestage_4.gif

997 ms

thumb_lifestage_5.jpg

thumb_lifestage_5.jpg

1033 ms

h3_lifestage_5.gif

h3_lifestage_5.gif

1034 ms

thumb_lifestage_6.jpg

thumb_lifestage_6.jpg

1063 ms

h3_lifestage_6.gif

h3_lifestage_6.gif

1089 ms

sub_fear.gif

sub_fear.gif

1090 ms

thumb_fear_1.jpg

thumb_fear_1.jpg

1160 ms

h3_fear_1.gif

h3_fear_1.gif

1216 ms

thumb_fear_2.jpg

thumb_fear_2.jpg

1201 ms

h3_fear_2.gif

h3_fear_2.gif

1237 ms

thumb_fear_3.jpg

thumb_fear_3.jpg

1267 ms

h3_fear_3.gif

h3_fear_3.gif

1270 ms

thumb_fear_4.jpg

thumb_fear_4.jpg

1324 ms

h3_fear_4.gif

h3_fear_4.gif

1323 ms

thumb_fear_5.jpg

thumb_fear_5.jpg

1233 ms

h3_fear_5.gif

h3_fear_5.gif

1264 ms

btn_rules.gif

btn_rules.gif

1278 ms

btn_sys.gif

btn_sys.gif

1133 ms

side_bg.gif

side_bg.gif

1159 ms

side_sub_lifestage.gif

side_sub_lifestage.gif

1183 ms

bullet_blue.gif

bullet_blue.gif

1195 ms

side_sub_fear.gif

side_sub_fear.gif

1107 ms

bullet_pink.gif

bullet_pink.gif

1127 ms

btn_interview.gif

btn_interview.gif

1094 ms

btn_faq.gif

btn_faq.gif

1112 ms

siteSeal.do

siteSeal.do

611 ms

btn_belief.gif

btn_belief.gif

1050 ms

btn_manga.gif

btn_manga.gif

1056 ms

footer_bg.gif

footer_bg.gif

1061 ms

acclog.cgi

acclog.cgi

1087 ms

siteSealImage.do

siteSealImage.do

250 ms

SEO Factors

kenja-hoken.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kenja-hoken.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kenja-hoken.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.

Social Sharing Optimization

kenja-hoken.co.jp

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