Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

hikarie.jp

渋谷ヒカリエ

Page Load Speed

10.4 sec in total

First Response

540 ms

Resources Loaded

9.5 sec

Page Rendered

333 ms

hikarie.jp screenshot

About Website

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.jp

Key Findings

We 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.

Performance Metrics

hikarie.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value29.3 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.252

49/100

15%

TTI (Time to Interactive)

Value36.8 s

0/100

10%

Network Requests Diagram

hikarie.jp

540 ms

www.hikarie.jp

1283 ms

import.css

318 ms

index.css

641 ms

import.js

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 Optimization Overview & Recommendations

Page size can be reduced by 625.8 kB (32%)

Content Size

2.0 MB

After Optimization

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.

HTML Optimization

-81%

Potential reduce by 34.3 kB

  • Original 42.5 kB
  • After minification 39.9 kB
  • After compression 8.2 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.

Image Optimization

-4%

Potential reduce by 49.6 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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.

JavaScript Optimization

-62%

Potential reduce by 326.8 kB

  • Original 524.4 kB
  • After minification 502.3 kB
  • After compression 197.6 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.

CSS Optimization

-87%

Potential reduce by 215.1 kB

  • Original 246.1 kB
  • After minification 222.8 kB
  • After compression 31.0 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.

Requests Breakdown

Number of requests can be reduced by 84 (49%)

Requests Now

170

After Optimization

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.

Accessibility Review

hikarie.jp accessibility score

61

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hikarie.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hikarie.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: