Tools & Wizards About Us
oticon.co.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

oticon.co.jp

個人のお客様｜オーティコン補聴器

Page Load Speed

10.2 sec in total

First Response

1.6 sec

Resources Loaded

8.4 sec

Page Rendered

221 ms

oticon.co.jp screenshot

About Website

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

オーティコン補聴器では、聞こえの改善のための各種製品を取り揃えております。耳の中に収まる耳あな型や耳の後ろにかける耳かけ型、目立たなさ、使いやすさ、機能などお客のニーズに合わせてお選びいただけます。

Visit oticon.co.jp

Key Findings

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

Performance Metrics

oticon.co.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value3,080 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

oticon.co.jp

1591 ms

style.css

2544 ms

colorbox.css

2700 ms

jquery.min.js

2213 ms

jquery-ui.min.js

3375 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 93% of them (56 requests) were addressed to the original Oticon.co.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Oticon.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 544.8 kB (37%)

Content Size

1.5 MB

After Optimization

941.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oticon.co.jp main page is 1.5 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. 35% of websites need less resources to load. Images take 865.4 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 22.0 kB

  • Original 32.4 kB
  • After minification 31.5 kB
  • After compression 10.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 22.0 kB or 68% of the original size.

Image Optimization

-9%

Potential reduce by 78.3 kB

  • Original 865.4 kB
  • After minification 787.1 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. Oticon images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 269.0 kB

  • Original 400.3 kB
  • After minification 391.3 kB
  • After compression 131.3 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 269.0 kB or 67% of the original size.

CSS Optimization

-93%

Potential reduce by 175.5 kB

  • Original 188.2 kB
  • After minification 117.6 kB
  • After compression 12.7 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. Oticon.co.jp needs all CSS files to be minified and compressed as it can save up to 175.5 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (16%)

Requests Now

56

After Optimization

47

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oticon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

oticon.co.jp

oticon.co.jp

1591 ms

style.css

style.css

2544 ms

colorbox.css

colorbox.css

2700 ms

jquery.min.js

jquery.min.js

2213 ms

jquery-ui.min.js

jquery-ui.min.js

3375 ms

jquery.imagesloaded.js

jquery.imagesloaded.js

1178 ms

scrolltopcontrol.js

scrolltopcontrol.js

1276 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1753 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

1563 ms

jquery.masonry.min.js

jquery.masonry.min.js

1826 ms

custom.js

custom.js

2027 ms

ch.js

ch.js

2070 ms

analytics.js

analytics.js

112 ms

globalnavi_bg.png

globalnavi_bg.png

247 ms

logo.ashx

logo.ashx

1805 ms

icon_arrow_s.png

icon_arrow_s.png

267 ms

headerbanner_navitime.ashx

headerbanner_navitime.ashx

2362 ms

headerbanner_contact.ashx

headerbanner_contact.ashx

836 ms

navi_home_on.ashx

navi_home_on.ashx

1294 ms

navi_starter_off.ashx

navi_starter_off.ashx

510 ms

navi_structure_off.ashx

navi_structure_off.ashx

596 ms

navi_product_off.ashx

navi_product_off.ashx

765 ms

navi_about_off.ashx

navi_about_off.ashx

870 ms

navi_contact_off.ashx

navi_contact_off.ashx

1045 ms

mainimage_powerproducts.ashx

mainimage_powerproducts.ashx

2257 ms

mainimage_dynamo.ashx

mainimage_dynamo.ashx

1631 ms

mainimage_senseisp.ashx

mainimage_senseisp.ashx

3186 ms

mainimage_brainhearing.ashx

mainimage_brainhearing.ashx

2433 ms

OyakoDay_2016.ashx

OyakoDay_2016.ashx

2394 ms

mainimageban_01.ashx

mainimageban_01.ashx

1949 ms

mainimageban_02.ashx

mainimageban_02.ashx

2233 ms

title_bg.png

title_bg.png

2470 ms

icon_arrow_l.png

icon_arrow_l.png

2513 ms

scred_arrow_icon.png

scred_arrow_icon.png

2488 ms

img_arrow.png

img_arrow.png

2647 ms

starter_top_01.ashx

starter_top_01.ashx

2932 ms

starter_top_02.ashx

starter_top_02.ashx

3742 ms

starter_top_03.ashx

starter_top_03.ashx

2971 ms

structure_top_07.ashx

structure_top_07.ashx

2782 ms

structure_top_03.ashx

structure_top_03.ashx

2972 ms

BrainHearing_top_01.ashx

BrainHearing_top_01.ashx

3063 ms

contentsbanner_mimitomo.ashx

contentsbanner_mimitomo.ashx

3273 ms

contentsbanner_every.ashx

contentsbanner_every.ashx

3975 ms

contentsbanner_children.ashx

contentsbanner_children.ashx

4252 ms

top_banner_distributers.ashx

top_banner_distributers.ashx

3572 ms

news_icon_news.ashx

news_icon_news.ashx

3451 ms

news_icon_press.ashx

news_icon_press.ashx

3528 ms

top_banner_search.ashx

top_banner_search.ashx

3712 ms

copyright.ashx

copyright.ashx

3789 ms

collect

collect

18 ms

collect

collect

82 ms

ga-audiences

ga-audiences

52 ms

ico-fb.ashx

ico-fb.ashx

3693 ms

ico-youtube.ashx

ico-youtube.ashx

3809 ms

pagetop.png

pagetop.png

3596 ms

navi_starter_on.ashx

navi_starter_on.ashx

3560 ms

navi_structure_on.ashx

navi_structure_on.ashx

3423 ms

navi_product_on.ashx

navi_product_on.ashx

3497 ms

navi_about_on.ashx

navi_about_on.ashx

3461 ms

navi_contact_on.ashx

navi_contact_on.ashx

3303 ms

Accessibility Review

oticon.co.jp accessibility score

83

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

oticon.co.jp best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

oticon.co.jp SEO score

92

Search Engine Optimization Advices

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

    JA

  • Encoding

    UTF-8

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

oticon.co.jp

Open Graph data is detected on the main page of Oticon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: