Access hokensc.jp. 保険を真剣に選ぶ人のための総合情報サイト

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.122

84/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

hokensc.jp

2738 ms

style.css.pagespeed.ce.jDDcgttgsk.css

346 ms

jquery-1.9.1.min.js.pagespeed.jm.roLDJ9nOeu.js

914 ms

jquery.cookie.js,Mjm.Qq8gohmZoz.js+jquery.fontsizechange.js,Mjm.mRYRHR7QpD.js+library.js,Mjm.8QswH8X0Eu.js+heightLine.js,Mjm.43S6dChYr2.js+jquery.ah-placeholder.js,Mjm.sr6D8-Wv8G.js.pagespeed.jc.qaI-qh3XXb.js

550 ms

styles.css,qver=4.3.pagespeed.ce._rvaR2jS-i.css

369 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 57% of them (41 requests) were addressed to the original Hokensc.jp, 11% (8 requests) were made to Omt.shinobi.jp and 7% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Hokensc.jp.

Content Size

934.3 kB

After Optimization

600.9 kB

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

HTML Optimization

-45%

Potential reduce by 37.2 kB

Original 83.2 kB
After minification 82.4 kB
After compression 46.0 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 37.2 kB or 45% of the original size.

Image Optimization

-11%

Potential reduce by 46.2 kB

Original 427.1 kB
After minification 381.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. Obviously, Hokensc needs image optimization as it can save up to 46.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 176.8 kB

Original 334.8 kB
After minification 334.4 kB
After compression 158.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 176.8 kB or 53% of the original size.

CSS Optimization

-82%

Potential reduce by 73.2 kB

Original 89.2 kB
After minification 62.8 kB
After compression 16.0 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. Hokensc.jp needs all CSS files to be minified and compressed as it can save up to 73.2 kB or 82% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

These are opportunities to improve the legibility of your content.

High

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

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hokensc.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 Hokensc.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

hokensc.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

保険を真剣に選ぶ人のための総合情報サイト - 保険ソクラテス

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

hokensc.jp

style.css.pagespeed.ce.jDDcgttgsk.css

jquery-1.9.1.min.js.pagespeed.jm.roLDJ9nOeu.js

jquery.cookie.js,Mjm.Qq8gohmZoz.js+jquery.fontsizechange.js,Mjm.mRYRHR7QpD.js+library.js,Mjm.8QswH8X0Eu.js+heightLine.js,Mjm.43S6dChYr2.js+jquery.ah-placeholder.js,Mjm.sr6D8-Wv8G.js.pagespeed.jc.qaI-qh3XXb.js

styles.css,qver=4.3.pagespeed.ce._rvaR2jS-i.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

hokensc.jp

style.css.pagespeed.ce.jDDcgttgsk.css

jquery-1.9.1.min.js.pagespeed.jm.roLDJ9nOeu.js

jquery.cookie.js,Mjm.Qq8gohmZoz.js+jquery.fontsizechange.js,Mjm.mRYRHR7QpD.js+library.js,Mjm.8QswH8X0Eu.js+heightLine.js,Mjm.43S6dChYr2.js+jquery.ah-placeholder.js,Mjm.sr6D8-Wv8G.js.pagespeed.jc.qaI-qh3XXb.js

styles.css,qver=4.3.pagespeed.ce._rvaR2jS-i.css

style.css,qver=4.3.1.pagespeed.ce.jDDcgttgsk.css

wpp.css,qver=3.3.1.pagespeed.ce.qH-xCxR6hY.css

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

loader.js

vertical-m.css,qversion=3.5.4.pagespeed.ce.Kos-ZWTbEH.css

base.css

top.css

responsive.gs.24col.css

font.css

reset.css

sns.css

adsbygoogle.js

jquery.form.min.js,qver=3.51.0-2014.06.20.pagespeed.jm.RVBOol6lkO.js

scripts.js,qver=4.3.pagespeed.jm.AQ2a9_TgU5.js

wp-emoji-release.min.js

bg.png

bg_head_pc.png

img_logo_pc.png

25xNxico_navi03.png.pagespeed.ic.e6EhzqRmEH.png

220xNxtop_yougo.png.pagespeed.ic.KKpgRsWHMx.png

220x80xbnr_manga.png.pagespeed.ic.WaCpMAOa9T.png

167xNxttl_fpans.png.pagespeed.ic.uudyjJv3mh.png

82xNxlogo_hoken.png.pagespeed.ic.nFh8Ytu5HD.png

75x75xb37c8fff3ffea67f6345568009da5d01-75x75.png.pagespeed.ic.eSkAWvgU91.jpg

75x75x8639104623_50d3abea3f-75x75.jpg.pagespeed.ic.-pvoOkF2_9.jpg

75x75x6008028111_99fbc41745-75x75.jpg.pagespeed.ic.clIls_T1Tc.jpg

111xNxlogo_mobuta.png.pagespeed.ic.DYK9j_GkFk.png

75x75xpresident1116-2-75x75.jpg.pagespeed.ic.e-n9l8VnZQ.jpg

75x75xae46b1f460ee46f789c27b264a6cb421-75x75.jpg.pagespeed.ic.n_x3npXmex.jpg

75x75xpresident-75x75.jpg.pagespeed.ic.OE7a1KzPSN.jpg

280xNxbnr_fpans.png.pagespeed.ic.zZAYQTDfJx.png

220xNxbnr_kikakushitsu.png.pagespeed.ic.tiS6djuNZo.png

220xNxbnr_soudan-repo.png.pagespeed.ic.H-9ynQ-7Vl.jpg

220xNxbnr_hokenjounal.png.pagespeed.ic.wXmWrv-iE-.png

220xNxbnr_mobutablog.png.pagespeed.ic.fYQuv8r80B.png

ico_search.png

ico_fpans.png