Tools & Wizards About Us
hokencom.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hokencom.net

Page Load Speed

5 sec in total

First Response

561 ms

Resources Loaded

4.2 sec

Page Rendered

257 ms

hokencom.net screenshot

About Website

Click here to check amazing Hokencom content. Otherwise, check out these important facts you probably never knew about hokencom.net

医療保険比較.comは20代、30代、40代、50代の保険選びに悩む方に向けた保険比較サイトです。医療保険は本当に必要か？どんなものを選べばいいのか？そんな疑問に徹底比較しながらお答えします。

Visit hokencom.net

Key Findings

We analyzed Hokencom.net page load time and found that the first response time was 561 ms and then it took 4.5 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

hokencom.net performance score

0

Network Requests Diagram

hokencom.net

561 ms

import.css

583 ms

jquery.min.js

29 ms

widget.js

60 ms

conversion.js

26 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 82% of them (75 requests) were addressed to the original Hokencom.net, 3% (3 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Hokencom.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.8 kB (16%)

Content Size

421.5 kB

After Optimization

355.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hokencom.net main page is 421.5 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. 35% of websites need less resources to load. Images take 304.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.7 kB

  • Original 37.2 kB
  • After minification 30.0 kB
  • After compression 8.6 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 7.2 kB, which is 19% 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 28.7 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 3.5 kB

  • Original 304.8 kB
  • After minification 301.3 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. Hokencom images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 2.2 kB

  • Original 41.3 kB
  • After minification 41.3 kB
  • After compression 39.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-82%

Potential reduce by 31.4 kB

  • Original 38.2 kB
  • After minification 31.0 kB
  • After compression 6.8 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. Hokencom.net needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (35%)

Requests Now

57

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hokencom.net

hokencom.net

561 ms

import.css

import.css

583 ms

jquery.min.js

jquery.min.js

29 ms

widget.js

widget.js

60 ms

conversion.js

conversion.js

26 ms

s_retargeting.js

s_retargeting.js

571 ms

import.css

import.css

313 ms

common.css

common.css

315 ms

layout.css

layout.css

313 ms

top.css

top.css

315 ms

content.css

content.css

322 ms

layout-pink.css

layout-pink.css

331 ms

content-pink.css

content-pink.css

360 ms

dc.js

dc.js

53 ms

header_logo.jpg

header_logo.jpg

345 ms

gnav_title_hikaku.jpg

gnav_title_hikaku.jpg

340 ms

gnav_title_column.jpg

gnav_title_column.jpg

344 ms

gnav_line_01.png

gnav_line_01.png

343 ms

gnav_title_ninshin.png

gnav_title_ninshin.png

343 ms

top_info.jpg

top_info.jpg

381 ms

top_hikaku_title.jpg

top_hikaku_title.jpg

648 ms

top_hikaku_02.jpg

top_hikaku_02.jpg

649 ms

top_hikaku_05.jpg

top_hikaku_05.jpg

662 ms

top_hikaku_06.jpg

top_hikaku_06.jpg

670 ms

top_hikaku_01.jpg

top_hikaku_01.jpg

671 ms

top_hikaku_03.jpg

top_hikaku_03.jpg

712 ms

top_column_title.jpg

top_column_title.jpg

979 ms

top_column_01.jpg

top_column_01.jpg

976 ms

top_column_02.jpg

top_column_02.jpg

977 ms

top_column_03.jpg

top_column_03.jpg

1011 ms

top_news_title.jpg

top_news_title.jpg

999 ms

top_ranking_title.jpg

top_ranking_title.jpg

1064 ms

top_ranking_no1.jpg

top_ranking_no1.jpg

1307 ms

top_ranking_abc.jpg

top_ranking_abc.jpg

1309 ms

top_ranking_no2.jpg

top_ranking_no2.jpg

1328 ms

top_ranking_aflac.jpg

top_ranking_aflac.jpg

1306 ms

top_ranking_no3.jpg

top_ranking_no3.jpg

1359 ms

top_ranking_orix.jpg

top_ranking_orix.jpg

1393 ms

top_qa_title.jpg

top_qa_title.jpg

1636 ms

top_qa_q.jpg

top_qa_q.jpg

1644 ms

top_qa_a.jpg

top_qa_a.jpg

1659 ms

side_nendai_title.jpg

side_nendai_title.jpg

1660 ms

side_nendai.jpg

side_nendai.jpg

1687 ms

footer_btn_pagetop.jpg

footer_btn_pagetop.jpg

1745 ms

footer_logo.png

footer_logo.png

1943 ms

widgets.js

widgets.js

82 ms

gnav_bg.jpg

gnav_bg.jpg

321 ms

gnav_line_02.png

gnav_line_02.png

313 ms

gnav_line_01.png

gnav_line_01.png

339 ms

side_nendai_arrow.jpg

side_nendai_arrow.jpg

366 ms

like.php

like.php

67 ms

57 ms

__utm.gif

__utm.gif

17 ms

41 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

50 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

30 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

123 ms

72 ms

72 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

46 ms

gnav_title_hikaku.jpg

gnav_title_hikaku.jpg

320 ms

header_logo.jpg

header_logo.jpg

356 ms

gnav_title_ninshin.png

gnav_title_ninshin.png

324 ms

gnav_line_01.png

gnav_line_01.png

335 ms

gnav_title_column.jpg

gnav_title_column.jpg

356 ms

top_info.jpg

top_info.jpg

355 ms

jot

jot

86 ms

top_hikaku_title.jpg

top_hikaku_title.jpg

505 ms

top_hikaku_02.jpg

top_hikaku_02.jpg

382 ms

top_hikaku_05.jpg

top_hikaku_05.jpg

363 ms

top_hikaku_06.jpg

top_hikaku_06.jpg

344 ms

top_hikaku_01.jpg

top_hikaku_01.jpg

391 ms

top_hikaku_03.jpg

top_hikaku_03.jpg

388 ms

top_column_01.jpg

top_column_01.jpg

400 ms

top_column_02.jpg

top_column_02.jpg

399 ms

top_column_title.jpg

top_column_title.jpg

561 ms

top_news_title.jpg

top_news_title.jpg

591 ms

top_column_03.jpg

top_column_03.jpg

450 ms

top_ranking_title.jpg

top_ranking_title.jpg

411 ms

top_ranking_aflac.jpg

top_ranking_aflac.jpg

383 ms

top_ranking_no1.jpg

top_ranking_no1.jpg

404 ms

top_ranking_abc.jpg

top_ranking_abc.jpg

468 ms

top_ranking_no2.jpg

top_ranking_no2.jpg

502 ms

top_ranking_no3.jpg

top_ranking_no3.jpg

492 ms

top_ranking_orix.jpg

top_ranking_orix.jpg

538 ms

top_qa_title.jpg

top_qa_title.jpg

518 ms

top_qa_q.jpg

top_qa_q.jpg

408 ms

top_qa_a.jpg

top_qa_a.jpg

454 ms

side_nendai_title.jpg

side_nendai_title.jpg

509 ms

side_nendai.jpg

side_nendai.jpg

629 ms

footer_btn_pagetop.jpg

footer_btn_pagetop.jpg

550 ms

footer_logo.png

footer_logo.png

444 ms

SEO Factors

hokencom.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hokencom.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Hokencom.net 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

hokencom.net

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