8.7 sec in total
540 ms
7.9 sec
347 ms
Visit hazuse.com now to see the best up-to-date Hazuse content for Japan and also check out these interesting facts you probably never knew about hazuse.com
Visit hazuse.comWe analyzed Hazuse.com page load time and found that the first response time was 540 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hazuse.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value10.1 s
0/100
25%
Value24.1 s
0/100
10%
Value21,920 ms
0/100
30%
Value0.347
32/100
15%
Value30.5 s
0/100
10%
540 ms
1716 ms
29 ms
913 ms
24 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 66% of them (72 requests) were addressed to the original Hazuse.com, 11% (12 requests) were made to Hazuse777.sakura.ne.jp and 10% (11 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Hazuse.com.
Page size can be reduced by 478.2 kB (27%)
1.8 MB
1.3 MB
In fact, the total size of Hazuse.com main page is 1.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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 74.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. This page needs HTML code to be minified as it can gain 17.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 74.9 kB or 87% of the original size.
Potential reduce by 66.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. Hazuse images are well optimized though.
Potential reduce by 135.5 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 135.5 kB or 60% of the original size.
Potential reduce by 201.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. Hazuse.com needs all CSS files to be minified and compressed as it can save up to 201.8 kB or 83% of the original size.
Number of requests can be reduced by 18 (17%)
107
89
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hazuse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
hazuse.com
540 ms
www.hazuse.com
1716 ms
ga.js
29 ms
parts_01.jpg
913 ms
__utm.gif
24 ms
data.php
640 ms
parts_03.jpg
769 ms
pc_menubar_01.jpg
476 ms
pc_menubar_02.jpg
523 ms
pc_menubar_03.jpg
551 ms
pc_menubar_04.jpg
831 ms
pc_menubar_05.jpg
907 ms
pc_menubar_06.jpg
740 ms
parts_13.jpg
960 ms
parts_25.jpg
735 ms
parts_29.jpg
991 ms
parts_31.jpg
810 ms
kontalk2.jpg
1284 ms
title_niconana1.jpg
1069 ms
niconana_pc_banner.jpg
1509 ms
nama-mente.png
986 ms
title_tureuchi11.jpg
1183 ms
tureuchi.jpg
1396 ms
476.jpg
1220 ms
477.jpg
1321 ms
478.jpg
1491 ms
479.jpg
1546 ms
481.jpg
1515 ms
482.jpg
1620 ms
483.jpg
1697 ms
484.jpg
1807 ms
485.jpg
1842 ms
button_06.jpg
1813 ms
button_09.jpg
1949 ms
button_11.jpg
1972 ms
button_13.jpg
2102 ms
button_15.jpg
2200 ms
button_22.jpg
2146 ms
button_24.jpg
2227 ms
button_26.jpg
2355 ms
button_28.jpg
2224 ms
button_34.jpg
2351 ms
button_35.jpg
2295 ms
089a3cb9d33325e365b054c96bcd3a76.gif
721 ms
data.php
536 ms
button_48.jpg
2241 ms
button_40.jpg
2215 ms
button_42.jpg
2294 ms
button_44.jpg
2401 ms
button_46.jpg
2326 ms
button_55.jpg
2363 ms
button_57.jpg
2461 ms
button_59.jpg
2379 ms
button_61.jpg
2271 ms
button_67.jpg
2504 ms
7f6abba6e4bb411140bed529094bd5fe.gif
729 ms
data.php
460 ms
button_68.jpg
2355 ms
button_03.jpg
2334 ms
button_01.jpg
2252 ms
mjhr.jpg
2387 ms
tils.jpg
2302 ms
2e2a292d0a019c26bea3b0c4c64c10ec.jpg
363 ms
data.php
282 ms
500tureuchi1.png
3091 ms
gachinana2.jpg
2348 ms
ichiran2_01.jpg
2289 ms
7c88_01.gif
2255 ms
7c25_03.gif
2358 ms
map_04.gif
2571 ms
EwxoEU-CPiE
73 ms
bd7ad2ca6bc137f4311666838126d88c.jpg
547 ms
data.php
270 ms
7c10_03.gif
2518 ms
www-embed-player-vflZsBgOl.css
61 ms
www-embed-player.js
81 ms
331.jpg
2390 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
45 ms
ad_status.js
42 ms
777syougou.gif
4196 ms
image003002.gif
2375 ms
image418.gif
2611 ms
0c41162e6dfdcfea25d37aaeebc5d920.png
187 ms
data.php
249 ms
sn.gif
2568 ms
777town_logo3.gif
2530 ms
sozai_29.jpg
2404 ms
1afd741ab1179f17cdfba9f554a799b1.png
182 ms
widgets.js
144 ms
bosotto.php
2968 ms
sozai_35.jpg
2439 ms
gachinana3.jpg
2459 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
147 ms
syndication
94 ms
341394554924199936
235 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
163 ms
22p9gqotsd2ng8ppt0k7_normal.jpeg
136 ms
-VsFROrW_normal.jpg
136 ms
XLSjfwC7_normal.jpeg
132 ms
oly-hazuse_chara4_normal.jpg
131 ms
cWEP13-B_normal.jpg
190 ms
yhp9dA03_normal.jpg
130 ms
RChDQnx__normal.jpeg
128 ms
CcXr9YbUkAALSiN.jpg:small
167 ms
CcXS9BwUkAAT04I.jpg:small
176 ms
CcSHPPSUcAEVUmz.jpg:small
130 ms
CcPUiVSUAAA41FD.jpg:small
186 ms
jot
27 ms
hazuse.com accessibility score
ARIA
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.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
hazuse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hazuse.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Hazuse.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 Hazuse.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.
hazuse.com
Open Graph description is not detected on the main page of Hazuse. 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: