Tools & Wizards About Us
tokyohearing.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tokyohearing.jp

補聴器専門 東京ヒアリングケアセンター - 専門家による丁寧なフィッティングと、生活や心理面まで含めたサポート

Page Load Speed

5.1 sec in total

First Response

1.5 sec

Resources Loaded

3.3 sec

Page Rendered

307 ms

tokyohearing.jp screenshot

About Website

Visit tokyohearing.jp now to see the best up-to-date Tokyohearing content for Japan and also check out these interesting facts you probably never knew about tokyohearing.jp

補聴器を満足して使っていくことは、実はそう簡単ではありません。専門家による丁寧なフィッティングと、生活や心理面まで含めたサポートが有効です。私たちは補聴器にお困りの方に寄り添い、長いおつきあいで支えていきます。これまで補聴器に満足できなかった方、ぜひ一度ご来店ください。

Visit tokyohearing.jp

Key Findings

We analyzed Tokyohearing.jp page load time and found that the first response time was 1.5 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tokyohearing.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value6.3 s

60/100

10%

Network Requests Diagram

tokyohearing.jp

1476 ms

wp-emoji-release.min.js

698 ms

styles.css

372 ms

style.css

370 ms

allinit.css

383 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 70% of them (42 requests) were addressed to the original Tokyohearing.jp, 5% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Tokyohearing.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 494.0 kB (57%)

Content Size

870.3 kB

After Optimization

376.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyohearing.jp main page is 870.3 kB. 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. Javascripts take 404.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 27.8 kB

  • Original 37.8 kB
  • After minification 36.3 kB
  • After compression 10.0 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 27.8 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 7.2 kB

  • Original 150.0 kB
  • After minification 142.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. Tokyohearing images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 228.2 kB

  • Original 404.2 kB
  • After minification 402.6 kB
  • After compression 176.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 228.2 kB or 56% of the original size.

CSS Optimization

-83%

Potential reduce by 230.9 kB

  • Original 278.3 kB
  • After minification 269.9 kB
  • After compression 47.4 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. Tokyohearing.jp needs all CSS files to be minified and compressed as it can save up to 230.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (37%)

Requests Now

57

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyohearing. 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 from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tokyohearing.jp

tokyohearing.jp

1476 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

698 ms

styles.css

styles.css

372 ms

style.css

style.css

370 ms

allinit.css

allinit.css

383 ms

common.css

common.css

385 ms

header.css

header.css

558 ms

primary.css

primary.css

737 ms

secondary.css

secondary.css

569 ms

footer.css

footer.css

401 ms

front-page.css

front-page.css

402 ms

jquery.js

jquery.js

958 ms

jquery-migrate.min.js

jquery-migrate.min.js

593 ms

jsapi

jsapi

25 ms

jquery.form.min.js

jquery.form.min.js

593 ms

scripts.js

scripts.js

517 ms

analytics.js

analytics.js

5 ms

jquery.min.js

jquery.min.js

19 ms

collect

collect

108 ms

collect

collect

144 ms

header-logo.gif

header-logo.gif

227 ms

tokyo_hcc.gif

tokyo_hcc.gif

219 ms

header-toll_free.gif

header-toll_free.gif

219 ms

custum_iem.jpg

custum_iem.jpg

193 ms

head_navi_01.gif

head_navi_01.gif

220 ms

head_navi_02.gif

head_navi_02.gif

220 ms

head_navi_03.gif

head_navi_03.gif

370 ms

head_navi_04.gif

head_navi_04.gif

528 ms

head_navi_05.gif

head_navi_05.gif

527 ms

header-image.jpg

header-image.jpg

636 ms

age_btm_020.jpg

age_btm_020.jpg

531 ms

age_btm_010.jpg

age_btm_010.jpg

535 ms

age_btm_030.jpg

age_btm_030.jpg

550 ms

side_nav_01.gif

side_nav_01.gif

634 ms

side_nav_02.gif

side_nav_02.gif

633 ms

side_nav_03.gif

side_nav_03.gif

634 ms

side_nav_04.gif

side_nav_04.gif

635 ms

side_nav_05.gif

side_nav_05.gif

724 ms

side_nav_06.gif

side_nav_06.gif

789 ms

side_nav_07.gif

side_nav_07.gif

773 ms

side_nav_08.gif

side_nav_08.gif

773 ms

side_nav_09.gif

side_nav_09.gif

787 ms

custum_earmoni.png

custum_earmoni.png

789 ms

manager_blog.png

manager_blog.png

897 ms

facebook.png

facebook.png

958 ms

header-inquiry.gif

header-inquiry.gif

957 ms

pagetop.gif

pagetop.gif

963 ms

all.js

all.js

72 ms

SZ_7gvX1ZcA

SZ_7gvX1ZcA

99 ms

99 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

48 ms

www-embed-player.js

www-embed-player.js

104 ms

base.js

base.js

154 ms

xd_arbiter.php

xd_arbiter.php

97 ms

xd_arbiter.php

xd_arbiter.php

320 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

73 ms

ad_status.js

ad_status.js

125 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

102 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

104 ms

ping

ping

40 ms

Accessibility Review

tokyohearing.jp accessibility score

89

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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.

Best Practices

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

tokyohearing.jp SEO score

92

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyohearing.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 Tokyohearing.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

tokyohearing.jp

Open Graph description is not detected on the main page of Tokyohearing. 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: