Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 69

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

oticon.global

Hearing aids, information on hearing loss and tinnitus | Oticon

Page Load Speed

5.2 sec in total

First Response

161 ms

Resources Loaded

4.6 sec

Page Rendered

423 ms

oticon.global screenshot

About Website

Click here to check amazing Oticon content for Belarus. Otherwise, check out these important facts you probably never knew about oticon.global

Rediscover the sounds of your life with Oticon hearing aids. Explore all our hearing aids & accessories, learn about hearing loss, and more.

Visit oticon.global

Key Findings

We analyzed Oticon.global page load time and found that the first response time was 161 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

oticon.global performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

8/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value11.3 s

6/100

10%

TBT (Total Blocking Time)

Value1,290 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.807

5/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

hearing-aid-users

161 ms

www.oticon.com

651 ms

uc.js

237 ms

main.dc4e98b88a24ebe96cae974b67dd839d.css

245 ms

pep-image-hotfix-7-14-22.css

804 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Oticon.global, 53% (23 requests) were made to Wdh02.azureedge.net and 12% (5 requests) were made to Wdh-fonts.azureedge.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Wdh02.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.5 kB (7%)

Content Size

1.3 MB

After Optimization

1.2 MB

In fact, the total size of Oticon.global main page is 1.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 949.4 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 52.6 kB

  • Original 79.2 kB
  • After minification 69.0 kB
  • After compression 26.6 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. This page needs HTML code to be minified as it can gain 10.2 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 52.6 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 29.5 kB

  • Original 949.4 kB
  • After minification 919.9 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

-6%

Potential reduce by 2.0 kB

  • Original 35.4 kB
  • After minification 35.4 kB
  • After compression 33.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 382 B

  • Original 230.5 kB
  • After minification 230.5 kB
  • After compression 230.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. Oticon.global has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (39%)

Requests Now

36

After Optimization

22

The browser has sent 36 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 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

oticon.global accessibility score

94

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

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

Links do not have a discernible name

Best Practices

oticon.global best practices score

69

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

High

Registers an unload listener

Low

Detected JavaScript libraries

SEO Factors

oticon.global SEO score

85

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

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oticon.global can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Oticon.global 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 Oticon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: