Tools & Wizards About Us
widex.com.au screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

widex.com.au

Widex Hearing Aids & Hearing Care Solutions | Widex

Page Load Speed

4.1 sec in total

First Response

316 ms

Resources Loaded

3 sec

Page Rendered

793 ms

widex.com.au screenshot

About Website

Visit widex.com.au now to see the best up-to-date Widex content for Australia and also check out these interesting facts you probably never knew about widex.com.au

Explore the possibilities of Widex hearing solutions and hearing aids for your lifestyle. Find your next hearing aids and get a risk-free trial!

Visit widex.com.au

Key Findings

We analyzed Widex.com.au page load time and found that the first response time was 316 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

widex.com.au performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

widex.com.au

316 ms

647 ms

widex-fonts.css

389 ms

shared.693d4e36fe838144999d.css

128 ms

widex.aaf8796ac275573356d9.css

141 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Widex.com.au, 73% (27 requests) were made to Azurecdn.widex.com and 11% (4 requests) were made to Consent.trustarc.com. The less responsive or slowest element that took the longest time to load (905 ms) relates to the external source Azurecdn.widex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.2 kB (4%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Widex.com.au 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 44.4 kB

  • Original 56.0 kB
  • After minification 50.3 kB
  • After compression 11.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. 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 44.4 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 32.4 kB

  • Original 1.5 MB
  • After minification 1.5 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. Widex images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 753 B

  • Original 285.9 kB
  • After minification 285.9 kB
  • After compression 285.2 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

-3%

Potential reduce by 4.7 kB

  • Original 159.9 kB
  • After minification 159.9 kB
  • After compression 155.3 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. Widex.com.au has all CSS files already compressed.

Requests Breakdown

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

Requests Now

35

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

widex.com.au

widex.com.au

316 ms

647 ms

widex-fonts.css

widex-fonts.css

389 ms

shared.693d4e36fe838144999d.css

shared.693d4e36fe838144999d.css

128 ms

widex.aaf8796ac275573356d9.css

widex.aaf8796ac275573356d9.css

141 ms

widex-echo-config.d7de8a18d32daff7bd5d.js

widex-echo-config.d7de8a18d32daff7bd5d.js

172 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

181 ms

form_tracking.4a90df84c28e49c3edd7.js

form_tracking.4a90df84c28e49c3edd7.js

171 ms

notice

notice

91 ms

trustarc_middleware.f4d6d3491b6ed08e3bae.js

trustarc_middleware.f4d6d3491b6ed08e3bae.js

170 ms

menuBar.003ff294147e43b8733f.js

menuBar.003ff294147e43b8733f.js

169 ms

shopFinderFilterRenderer.f82f2a5eb4c4abe0a9f8.js

shopFinderFilterRenderer.f82f2a5eb4c4abe0a9f8.js

174 ms

bundle.32471a41a21cd22e589b.js

bundle.32471a41a21cd22e589b.js

174 ms

widex_js.72c34ada10c5db1b3355.js

widex_js.72c34ada10c5db1b3355.js

173 ms

carousel-arrow.svg

carousel-arrow.svg

8 ms

widex_smartric_man-side_1920x1080_v2.jpg

widex_smartric_man-side_1920x1080_v2.jpg

11 ms

widex-sound_woman-blue-blazer_skyline-close_1920x1080.jpg

widex-sound_woman-blue-blazer_skyline-close_1920x1080.jpg

20 ms

widex-smartric_tech-black_pair_shadow_background_new_1000x1000.jpg

widex-smartric_tech-black_pair_shadow_background_new_1000x1000.jpg

7 ms

widex-moment-app-in-use_1920x1080.jpg

widex-moment-app-in-use_1920x1080.jpg

9 ms

moment-sheer_sric-r-d_sound-assist_led_flat_glasses_1920x1080.jpg

moment-sheer_sric-r-d_sound-assist_led_flat_glasses_1920x1080.jpg

21 ms

widex_soundconnect_dark-table_1920x1080.jpg

widex_soundconnect_dark-table_1920x1080.jpg

20 ms

widex-tinnitus_man-with-glasses-smiling_1000x1000.jpg

widex-tinnitus_man-with-glasses-smiling_1000x1000.jpg

21 ms

dominique-le-gendre-playing-the-guitar-1000x1000.jpg

dominique-le-gendre-playing-the-guitar-1000x1000.jpg

905 ms

facebook-icon_white_32px.svg

facebook-icon_white_32px.svg

489 ms

instagram-icon_white_32px.svg

instagram-icon_white_32px.svg

507 ms

linkedin-icon_white_32px.svg

linkedin-icon_white_32px.svg

36 ms

youtube-icon_white_32px.svg

youtube-icon_white_32px.svg

36 ms

widex---light-sand---rgb.svg

widex---light-sand---rgb.svg

39 ms

log

log

88 ms

get

get

34 ms

v1.7-230

v1.7-230

37 ms

hearing-test_1920x400.jpg

hearing-test_1920x400.jpg

10 ms

widex-store_1920x700.jpg

widex-store_1920x700.jpg

9 ms

widex_smartric_charger-on-table_notebook_cut-out_1920x403.jpg

widex_smartric_charger-on-table_notebook_cut-out_1920x403.jpg

8 ms

arrow-up.svg

arrow-up.svg

7 ms

update.min.js

update.min.js

68 ms

uifbvnhu.js

uifbvnhu.js

725 ms

Accessibility Review

widex.com.au accessibility score

81

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

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

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

widex.com.au 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

widex.com.au SEO score

86

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 Widex.com.au 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 Widex.com.au 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

widex.com.au

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