11.8 sec in total
3.2 sec
7.2 sec
1.5 sec
Welcome to heathaze.tokyo.jp homepage info - get ready to check HEATHAZE best content for Japan right away, or after learning these important things about heathaze.tokyo.jp
エッジが効いた人や場をポップに魅せるカルチャードキュメントサイトです。
Visit heathaze.tokyo.jpWe analyzed Heathaze.tokyo.jp page load time and found that the first response time was 3.2 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
heathaze.tokyo.jp performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value6.5 s
9/100
25%
Value6.8 s
35/100
10%
Value260 ms
83/100
30%
Value0.031
100/100
15%
Value8.2 s
41/100
10%
3167 ms
194 ms
364 ms
545 ms
350 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 48% of them (59 requests) were addressed to the original Heathaze.tokyo.jp, 15% (18 requests) were made to Pbs.twimg.com and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Heathaze.tokyo.jp.
Page size can be reduced by 306.7 kB (10%)
3.1 MB
2.8 MB
In fact, the total size of Heathaze.tokyo.jp 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. 65% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 35.8 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 35.8 kB or 75% of the original size.
Potential reduce by 176.2 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. HEATHAZE images are well optimized though.
Potential reduce by 79.4 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 79.4 kB or 52% of the original size.
Potential reduce by 15.2 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. Heathaze.tokyo.jp needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 79% of the original size.
Number of requests can be reduced by 31 (26%)
121
90
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEATHAZE. 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 7 to 1 for CSS and as a result speed up the page load time.
heathaze.tokyo.jp
3167 ms
style.css
194 ms
smartRollover.js
364 ms
jquery-1.9.0.min.js
545 ms
jquery.nivo.slider.pack.js
350 ms
nivo-slider.css
361 ms
pagenavi-css.css
370 ms
show_ads.js
7 ms
dot.jpg
232 ms
head_bg.png
287 ms
logo.jpg
289 ms
bar.jpg
289 ms
nav_01_on.jpg
435 ms
nav_02_off.jpg
408 ms
nav_03_off.jpg
434 ms
nav_04_off.jpg
433 ms
nav_05_off.jpg
465 ms
nav_06_off.jpg
465 ms
icon_sns01.png
585 ms
icon_sns02.png
598 ms
main_banner_nextphase.jpg
1872 ms
box_head_01.png
874 ms
box_body.png
655 ms
bads1-500x375.jpg
1537 ms
icon_08.gif
825 ms
PIP_Falus_mini-500x333.jpg
1037 ms
icon_01.gif
870 ms
EBMT1bright-500x375.jpg
1911 ms
icon_09.gif
1060 ms
dual1new-333x500.jpg
1739 ms
gorgejukemura-500x500.png
1380 ms
icon_07.gif
1315 ms
598f18f0ef879f683605e95a7013c2721.jpg
1858 ms
miwaka_ogawa_main-500x500.jpg
1761 ms
djbou_bokunou_main-339x500.jpg
2411 ms
koichi_kohhei1-500x333.jpg
2105 ms
koedawg1-500x375.jpg
2111 ms
box_foot.png
2029 ms
box_head_02.png
2044 ms
01-333x500.jpg
2266 ms
icon_14.gif
2202 ms
mh3_0512-500x333.jpg
2237 ms
tokyo_main-362x500.jpg
2475 ms
Tabor-Robak-500x281.jpg
2092 ms
widgets.js
4 ms
arca_soichiro-500x335.png
2807 ms
ca-pub-8248820307975346.js
166 ms
zrt_lookup.html
67 ms
show_ads_impl.js
105 ms
noiz_slug-500x500.jpeg
2156 ms
oursummer1-500x333.jpeg
2359 ms
ga.js
30 ms
marie_jukebox_main-500x500.jpg
2380 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
57 ms
__utm.gif
53 ms
ads
373 ms
likebox.php
230 ms
osd.js
28 ms
saka_main-366x500.jpg
2219 ms
syndication
117 ms
548764741129076737
206 ms
yamato-california_top-500x280.jpg
2215 ms
box_head_03.png
2235 ms
kinokonosei_top-500x333.jpg
2599 ms
icon_06.gif
2362 ms
shirokumagohan-4koma-top-6-500x500.jpg
2415 ms
abc_logo-500x300.jpg
2263 ms
kinokonosei10-2015-500x500.jpg
2431 ms
lL2b34Z7dj7.css
52 ms
guHxiHaOfJH.css
77 ms
_rx8naC75Dy.js
97 ms
b94UUzHjapV.js
97 ms
0wM5s1Khldu.js
81 ms
TTCre3391I0.js
96 ms
1f48e.png
192 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
12 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
38 ms
shirokumagohan-5-top-500x500.jpg
2510 ms
5FNkkmmX_normal.jpg
373 ms
wIZwRyGw_normal.jpg
400 ms
a8a3c65170f7cfd22eaa92ce1c0981e6_normal.jpeg
452 ms
LskJxZOA_normal.jpg
475 ms
t4dMcUwK_normal.jpg
579 ms
9Uz0QjIH_normal.jpg
504 ms
CcYtOZSUAAAif2u.jpg:small
498 ms
CcYsjRTUsAEaBKh.jpg:small
574 ms
CcYplaCUcAAPA3l.jpg:small
533 ms
Cb5wSltUAAEiHQp.jpg:small
598 ms
Cb5o181VIAAsfEl.jpg:small
636 ms
Ca8J2BwUEAANQ9U.jpg:small
568 ms
Ca8Jb3EUkAAS75_.jpg:small
664 ms
CY1h8yeUAAAX7eu.jpg:small
823 ms
CacQrPMWIAAI4NJ.jpg:small
646 ms
CaXxOM6UkAYWxIw.jpg:small
766 ms
Cam3G3EUMAEMRh6.jpg:small
626 ms
CaTlpwTUMAAy9aI.jpg:small
755 ms
12088430_491073224392530_507698751880528138_n.jpg
281 ms
11048715_491191024380750_1704319616007324799_n.jpg
277 ms
1780733_10152219289854076_1784648042_n.jpg
282 ms
165556_10150090444092817_8225274_n.jpg
282 ms
10474801_735289489889602_3823584303912124009_n.jpg
306 ms
12507418_581314925356586_2005810787423804879_n.jpg
303 ms
12507234_964306016976955_2703757866385940517_n.jpg
282 ms
12654318_445844652272507_4542003530484904009_n.jpg
285 ms
12360084_174160262936055_6443026542648572625_n.jpg
284 ms
wL6VQj7Ab77.png
66 ms
s7jcwEQH7Sx.png
65 ms
5171746271700867932
112 ms
abg.js
112 ms
m_js_controller.js
129 ms
googlelogo_color_112x36dp.png
158 ms
shirokumagohan_4koma_4_top-500x500.jpg
2390 ms
shirokumagohan-4koma-top-3-500x500.jpg
2194 ms
s
35 ms
redir.html
159 ms
x_button_blue2.png
36 ms
iframe.html
62 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
11 ms
I6-MnjEovm5.js
49 ms
f6T91Deal_q.js
52 ms
jot
29 ms
btn_02.jpg
190 ms
ui
37 ms
heathaze.tokyo.jp 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-*] attributes do not match their roles
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
Links do not have a discernible name
heathaze.tokyo.jp 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
Page has valid source maps
heathaze.tokyo.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heathaze.tokyo.jp 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 Heathaze.tokyo.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.
heathaze.tokyo.jp
Open Graph description is not detected on the main page of HEATHAZE. 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: