6.2 sec in total
526 ms
5.5 sec
261 ms
Click here to check amazing Hokenqing content. Otherwise, check out these important facts you probably never knew about hokenqing.com
ほけんキューイングは、保険に関するFAQ・ランキング・プロへの相談までを網羅した保険の総合サイトです。
Visit hokenqing.comWe analyzed Hokenqing.com page load time and found that the first response time was 526 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hokenqing.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value11.3 s
0/100
25%
Value4.6 s
71/100
10%
Value830 ms
35/100
30%
Value0
100/100
15%
Value6.0 s
64/100
10%
526 ms
646 ms
311 ms
311 ms
323 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 51% of them (58 requests) were addressed to the original Hokenqing.com, 8% (9 requests) were made to Apis.google.com and 4% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Hokenqing.com.
Page size can be reduced by 475.5 kB (15%)
3.1 MB
2.6 MB
In fact, the total size of Hokenqing.com main page is 3.1 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 43.4 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 10.1 kB, which is 20% 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 43.4 kB or 84% of the original size.
Potential reduce by 97.4 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. Hokenqing images are well optimized though.
Potential reduce by 207.8 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 207.8 kB or 65% of the original size.
Potential reduce by 126.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. Hokenqing.com needs all CSS files to be minified and compressed as it can save up to 126.9 kB or 83% of the original size.
Number of requests can be reduced by 59 (55%)
108
49
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hokenqing. 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.
hokenqing.com
526 ms
bedff4ad055da96268ad10499f40b678.css
646 ms
4826bf27795c1863e7bbc7e494de0066.css
311 ms
colorbox.css
311 ms
pagenavi-css.css
323 ms
jetpack.css
650 ms
jquery.js
816 ms
jquery-migrate.min.js
464 ms
jquery.colorbox-min.js
465 ms
jquery-colorbox-wrapper-min.js
483 ms
adsbygoogle.js
5 ms
devicepx-jetpack.js
3 ms
gprofiles.js
55 ms
e-201606.js
3 ms
jquery.min.js
30 ms
0ac53b4690f45c79dfe0f15566ff43b6.js
936 ms
header_logo.png
213 ms
header_catch.png
214 ms
menu_icon01.png
216 ms
menu_icon03.png
217 ms
menu_icon02.png
207 ms
slide201510.png
277 ms
slide20141125.jpg
1087 ms
slide02.jpg
703 ms
slide201510_L.png
542 ms
slide20141125_L.jpg
1024 ms
slide02_L.jpg
704 ms
menu_icon03_sp.png
416 ms
011-300x103.png
724 ms
p28-45%E3%82%B1%E3%83%BC%E3%82%B9%E5%88%A5_%E3%83%9A%E3%83%BC%E3%82%B8_1-300x112.png
1367 ms
01-300x112.png
1024 ms
01-300x113.png
868 ms
top-300x118.png
1032 ms
menu_icon03_sp.png
2562 ms
pro_icon00.png
1186 ms
pro003.jpg
1346 ms
ranking_icon02.png
1187 ms
pro_icon01.png
1239 ms
pro004.jpg
1509 ms
pro010.jpg
1803 ms
pro007.jpg
1701 ms
pro005.jpg
1829 ms
pro015.png
2008 ms
pro014.png
1831 ms
pro_icon02.png
1857 ms
ranking_icon01.png
1958 ms
arrow_gray01.png
1991 ms
ranking_b1.png
1992 ms
pamph_iryou01.jpg
2164 ms
ranking_b2.png
2112 ms
btn.js
92 ms
ranking_b3.png
2098 ms
ca-pub-7476936309553121.js
139 ms
zrt_lookup.html
139 ms
show_ads_impl.js
73 ms
analytics.js
121 ms
sdk.js
116 ms
plusone.js
208 ms
g.gif
104 ms
hovercard.css
100 ms
services.css
156 ms
widgets.js
71 ms
plusone.js
236 ms
button-only.gif
339 ms
bookmark_button.js
357 ms
pamph_gan01.jpg
2178 ms
ads
292 ms
button
57 ms
osd.js
54 ms
flexslider-icon.woff
1962 ms
pamph_shushin01.jpg
2522 ms
pamph_teiki01.jpg
2266 ms
pamph_shunyu-hosho01.jpg
2264 ms
pamph_kojin-nenkin01.jpg
2440 ms
collect
31 ms
button.css
28 ms
shared.js
30 ms
button.js
30 ms
126 ms
like.php
190 ms
linebutton_82x20.png
3747 ms
collect
51 ms
pocket_button.png
8 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
43 ms
fastbutton
94 ms
postmessageRelay
33 ms
3193398744-postmessagerelay.js
45 ms
rpc:shindig_random.js
57 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
15 ms
pagetop_btn.png
2215 ms
cb=gapi.loaded_0
11 ms
fy8tT2klpgR.js
29 ms
LVx-xkvaJ0b.png
16 ms
13250232331523409936
25 ms
abg.js
27 ms
m_js_controller.js
34 ms
googlelogo_color_112x36dp.png
65 ms
255 ms
s
19 ms
x_button_blue2.png
19 ms
icon_home2.png
2100 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
ranking_icon01.png
2024 ms
sns_fb01.png
2083 ms
sns_tw01.png
2079 ms
reset.css
6 ms
entry-button.css
7 ms
button-counter.gif
4 ms
xd_arbiter.php
18 ms
xd_arbiter.php
34 ms
ui
37 ms
hokenqing.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
hokenqing.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
hokenqing.com SEO score
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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hokenqing.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Hokenqing.com 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.
hokenqing.com
Open Graph data is detected on the main page of Hokenqing. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: