10.4 sec in total
540 ms
9.5 sec
333 ms
Visit hikarie.jp now to see the best up-to-date Hikarie content for Japan and also check out these interesting facts you probably never knew about hikarie.jp
渋谷駅直結「渋谷ヒカリエ」公式サイト。ショップ、カフェ&レストラン、イベントホール、カンファレンス、東急シアターオーブ、オフィス等からなる高層複合施設です。
Visit hikarie.jpWe analyzed Hikarie.jp page load time and found that the first response time was 540 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hikarie.jp performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value29.3 s
0/100
25%
Value13.9 s
1/100
10%
Value2,780 ms
3/100
30%
Value0.252
49/100
15%
Value36.8 s
0/100
10%
540 ms
1283 ms
318 ms
641 ms
343 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 80% of them (139 requests) were addressed to the original Hikarie.jp, 6% (11 requests) were made to Hms.hikarie.jp and 2% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Hikarie.jp.
Page size can be reduced by 625.8 kB (32%)
2.0 MB
1.3 MB
In fact, the total size of Hikarie.jp main page is 2.0 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 34.3 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 34.3 kB or 81% of the original size.
Potential reduce by 49.6 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. Hikarie images are well optimized though.
Potential reduce by 326.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 326.8 kB or 62% of the original size.
Potential reduce by 215.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. Hikarie.jp needs all CSS files to be minified and compressed as it can save up to 215.1 kB or 87% of the original size.
Number of requests can be reduced by 84 (49%)
170
86
The browser has sent 170 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hikarie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
hikarie.jp
540 ms
www.hikarie.jp
1283 ms
import.css
318 ms
index.css
641 ms
import.js
343 ms
slideshow.js
364 ms
readJsonTop.js
727 ms
sortMenuScroll.js
472 ms
linq.min.js
856 ms
sortInfomation_top.js
532 ms
reset.css
230 ms
default.css
313 ms
common.css
580 ms
style.css
1361 ms
jquery.jscrollpane.css
473 ms
gbl_header.css
1256 ms
jquery.min.js
30 ms
jquery.jscrollpane.min.js
539 ms
jquery.mousewheel.js
185 ms
jquery.scrollTo-min.js
171 ms
jquery.easing.1.3.js
320 ms
jquery.bxSlider.min.js
543 ms
jquery.cookie.js
159 ms
swfobject.js
513 ms
domain.js
339 ms
mwheelIntent.js
363 ms
commonParts.js
643 ms
functions.js
509 ms
glb_header.js
545 ms
season.js
679 ms
crosslanguage-translate.php
1313 ms
bg_wraper.gif
201 ms
ttl_myhikarie.gif
195 ms
profileicon.jpg
190 ms
btn_lang.gif
330 ms
btn_facebook.gif
198 ms
ttl_h1_hikarie.gif
160 ms
glbnav.gif
470 ms
ttl_h2_hikarie_topics.gif
338 ms
btn_more_news.gif
351 ms
ttl_h2_shopping.gif
362 ms
bg_arrow_btn.gif
375 ms
ttl_h2_cafe_restaurant.gif
486 ms
ttl_h2_design_art_theater.gif
504 ms
ttl_h2_event.gif
528 ms
ttl_h2_report.gif
547 ms
btn_pagetop.gif
556 ms
ttl_h3_opentime.gif
683 ms
ttl_th_shinqs.gif
669 ms
ttl_th_cafe.gif
694 ms
ttl_th_cafe7.gif
709 ms
ttl_th_8.gif
751 ms
ttl_h3_searchinfo.gif
736 ms
side_nav_search.gif
827 ms
bnr_myhikarie.gif
870 ms
btn_evtcal.gif
871 ms
btn_building_brief.gif
888 ms
btn_service.gif
947 ms
btn_hikarie_for_business.jpg
1341 ms
ttl_h3_weeklyrank.gif
1026 ms
btn_popular_article.gif
1027 ms
ttl_h3_informationcenter.gif
1081 ms
ttl_th_info_hikarie.gif
1080 ms
dotline_x.gif
1128 ms
txt_td_hikarie_number.gif
1185 ms
ttl_th_info_shinqs.gif
1168 ms
txt_td_shinqs_number.gif
1263 ms
widgets.js
37 ms
ga.js
37 ms
hikarieWebEmergency.php
702 ms
hikarieWebTopRightBanner.php
718 ms
hikarieWebAccessRanking.php
805 ms
hikarieWeb8Movie.php
782 ms
hikarieWebTopImage.php
765 ms
hikarieWebNewsEvent_v2.php
857 ms
hikarieWebNewsEvent_v2.php
1516 ms
hikarieWebNewsEvent_v2.php
1298 ms
hikarieWebNewsEvent_v2.php
1586 ms
hikarieWebNewsEvent_v2.php
1186 ms
hikarieWebReport.php
1211 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
53 ms
__utm.gif
22 ms
like.php
132 ms
collect
74 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
34 ms
ttl_h3_8tv.gif
1100 ms
bg_footernav.gif
1130 ms
nav_footer.gif
1149 ms
copyright.gif
1162 ms
btn_before_login.gif
1401 ms
vpc6VNjRPXV.js
62 ms
LVx-xkvaJ0b.png
66 ms
jot
101 ms
00001216_00002533_00000013.png
1092 ms
00001216_00002533_00000007.gif
929 ms
00001216_00002533_00000003.gif
743 ms
00001216_00002533_00000004.jpg
778 ms
00001216_00002533_00000001.gif
762 ms
00001216_00002533_00000005.jpg
1092 ms
00001216_00002533_00000002.gif
925 ms
00001216_00002533_00000006.gif
962 ms
00001211_00002434_00000125.jpg
1975 ms
00001211_00002434_00000126.jpg
2786 ms
00001211_00002434_00000098.jpg
1594 ms
pager_slideshow.png
1085 ms
149538201
84 ms
00000060_00002150_00002643.jpg
1510 ms
icon_rank1_s.gif
1128 ms
00000060_00002150_00002635.jpg
1208 ms
icon_rank2_s.gif
1284 ms
00000010_00000108_00000737.jpg
1573 ms
icon_rank3_s.gif
1439 ms
00000010_00000108_00000738.jpg
1751 ms
icon_rank4_s.gif
1683 ms
00000060_00002150_00002641.jpg
1875 ms
player.js
121 ms
player.css
83 ms
ga.js
102 ms
vuid.min.js
79 ms
icon_rank5_s.gif
1677 ms
__utm.gif
59 ms
00000010_00000108_00000739.jpg
1711 ms
icon_rank6_s.gif
1753 ms
proxy.html
35 ms
551245969.jpg
98 ms
3397992_60x60.jpg
67 ms
00000060_00002150_00002634.jpg
1725 ms
icon_rank7_s.gif
1837 ms
00000060_00002150_00002633.jpg
1817 ms
nr-852.min.js
49 ms
icon_rank8_s.gif
1779 ms
00000010_00000108_00000742.jpg
1907 ms
689d5b4562
117 ms
icon_rank9_s.gif
1737 ms
00000010_00000108_00000740.jpg
1834 ms
icon_rank10_s.gif
1818 ms
brdr_bottom.gif
1787 ms
bdr.gif
1833 ms
00000103_00002071_00000037.jpg
2376 ms
icon_hikarie.png
1791 ms
icon_event.png
1782 ms
00000060_00002150_00002435.jpg
1787 ms
icon_end.gif
1766 ms
icon_info.png
1787 ms
00000010_00000108_00000742.jpg
1956 ms
icon_shinqs.png
1784 ms
icon_fashionl.png
1700 ms
00000010_00000108_00000741.jpg
1981 ms
icon_lifestyle.png
1783 ms
00000010_00000108_00000740.jpg
1907 ms
icon_goods.png
1676 ms
00000010_00000108_00000739.jpg
1653 ms
icon_beauty.png
1549 ms
00000010_00000108_00000705.jpg
1666 ms
icon_cafe.png
1512 ms
icon_restaurant.png
1534 ms
00000010_00000108_00000704.jpg
1445 ms
00000010_00000108_00000701.jpg
1418 ms
00000060_00002150_00002643.jpg
1650 ms
00000060_00002150_00002641.jpg
1654 ms
00000060_00002150_00002640.jpg
1386 ms
00000060_00002150_00002647.jpg
1587 ms
icon_8.png
1440 ms
icon_culture.png
1392 ms
00000060_00002150_00002645.jpg
1744 ms
icon_hobby.png
1410 ms
00000060_00002150_00002644.jpg
1815 ms
icon_art.png
1467 ms
00000010_00000108_00000738.jpg
1887 ms
icon_food.png
1448 ms
00000060_00002150_00002638.jpg
1435 ms
icon_news.png
1511 ms
00000060_00002150_00002628.jpg
1555 ms
hikarie.jp accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hikarie.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hikarie.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
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hikarie.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 Hikarie.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.
hikarie.jp
Open Graph data is detected on the main page of Hikarie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: