9.8 sec in total
1.8 sec
5.5 sec
2.5 sec
Welcome to hocolife.com homepage info - get ready to check HOCOLIFE best content for Japan right away, or after learning these important things about hocolife.com
注文住宅で失敗しない生活知識・体験談
Visit hocolife.comWe analyzed Hocolife.com page load time and found that the first response time was 1.8 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hocolife.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.7 s
17/100
25%
Value6.3 s
42/100
10%
Value450 ms
63/100
30%
Value0.033
100/100
15%
Value5.8 s
67/100
10%
1823 ms
317 ms
338 ms
340 ms
345 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 71% of them (70 requests) were addressed to the original Hocolife.com, 5% (5 requests) were made to Pagead2.googlesyndication.com and 4% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Hocolife.com.
Page size can be reduced by 560.7 kB (15%)
3.8 MB
3.2 MB
In fact, the total size of Hocolife.com main page is 3.8 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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 67.9 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 67.9 kB or 76% of the original size.
Potential reduce by 149.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. HOCOLIFE images are well optimized though.
Potential reduce by 281.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 281.0 kB or 63% of the original size.
Potential reduce by 62.1 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. Hocolife.com needs all CSS files to be minified and compressed as it can save up to 62.1 kB or 82% of the original size.
Number of requests can be reduced by 39 (40%)
97
58
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HOCOLIFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
hocolife.com
1823 ms
common.css
317 ms
layout.css
338 ms
design.css
340 ms
mobile.css
345 ms
mobile_layout.css
351 ms
advanced.css
369 ms
main.css
478 ms
thickbox.css
504 ms
styles.css
508 ms
twitter-feed.css
515 ms
default.min.css
528 ms
jquery.js
745 ms
jquery-migrate.min.js
634 ms
common.js
677 ms
jquery.validate.min.js
61 ms
external-tracking.min.js
677 ms
nendAdLoader.js
44 ms
adsbygoogle.js
8 ms
thickbox.js
539 ms
jquery.form.min.js
563 ms
scripts.js
743 ms
utility.js
743 ms
socialButton.js
744 ms
wp-embed.min.js
744 ms
wp-emoji-release.min.js
519 ms
analytics.js
33 ms
show
30 ms
house88_31.gif
678 ms
banner_23.gif
766 ms
F293T.76639E.C5791C
570 ms
img-top2.gif
592 ms
bg-menu.png
354 ms
160225-01.jpg
779 ms
160225-02.jpg
634 ms
151225-01.jpg
950 ms
151225-04.jpg
1191 ms
151225-02.jpg
1000 ms
151225-03.jpg
1324 ms
151224-01.jpg
1137 ms
151224-02.jpg
1097 ms
151224-03.jpg
1297 ms
151224-04.jpg
1324 ms
151224-16.jpg
1434 ms
151224-17.jpg
1474 ms
151224-05.jpg
1544 ms
151224-06.jpg
1481 ms
151224-18.jpg
1911 ms
151224-19.jpg
2024 ms
151224-20.jpg
2005 ms
151224-07.jpg
1809 ms
151224-08.jpg
1663 ms
151224-21.jpg
1732 ms
151224-09.jpg
2008 ms
151224-10.jpg
1916 ms
151224-22.jpg
1987 ms
151224-27.jpg
2282 ms
151224-23.jpg
2102 ms
151224-11.jpg
2328 ms
151224-12.jpg
2179 ms
151224-13.jpg
2182 ms
151224-24.jpg
2174 ms
ca-pub-8758184662417538.js
294 ms
zrt_lookup.html
289 ms
show_ads_impl.js
245 ms
collect
232 ms
151224-25.jpg
2167 ms
151224-14.jpg
2397 ms
151224-15.jpg
2405 ms
151224-26.jpg
2245 ms
widgets.js
233 ms
platform.js
273 ms
all.js
355 ms
151224-28.jpg
2306 ms
151224-29.jpg
2124 ms
ads
283 ms
osd.js
16 ms
ads
339 ms
127 ms
xd_arbiter.php
134 ms
xd_arbiter.php
268 ms
profile150x130.png
1922 ms
bg-conts-h.gif
1898 ms
m_js_controller.js
34 ms
abg.js
52 ms
favicon
83 ms
googlelogo_color_112x36dp.png
81 ms
nessie_icon_thin_arrow_big_white.png
41 ms
s
33 ms
x_button_blue2.png
36 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
2 ms
icon-arrow_r_gray.png
1877 ms
icon-menu02.png
1735 ms
icon-arrow02.png
1690 ms
icon-arrow01.png
1592 ms
icon-arrow_r.png
1565 ms
bg-pagetop.png
1646 ms
loadingAnimation.gif
1541 ms
print.css
170 ms
hocolife.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
hocolife.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
hocolife.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hocolife.com 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 Hocolife.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.
hocolife.com
Open Graph description is not detected on the main page of HOCOLIFE. 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: