Tools & Wizards About Us
customhearing.net screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

customhearing.net

Hearing Health | House Call Hearing Health, Audiology & Hearing Aid Centers

Page Load Speed

1.8 sec in total

First Response

92 ms

Resources Loaded

1.2 sec

Page Rendered

508 ms

customhearing.net screenshot

About Website

Visit customhearing.net now to see the best up-to-date Custom Hearing content and also check out these interesting facts you probably never knew about customhearing.net

At Custom Hearing Solutions, we tailor the hearing solution for your needs and lifestyle. We offer FREE hearing tests in Lincoln and Omaha.

Visit customhearing.net

Key Findings

We analyzed Customhearing.net page load time and found that the first response time was 92 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

customhearing.net performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.052

98/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

customhearing.net

92 ms

customhearing.net

74 ms

formidableforms.css

59 ms

omnia-base.css

65 ms

integrity-light.css

31 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 56% of them (37 requests) were addressed to the original Customhearing.net, 17% (11 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (323 ms) belongs to the original domain Customhearing.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (49%)

Content Size

3.3 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Customhearing.net main page is 3.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. Only a small number of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 90.1 kB

  • Original 110.2 kB
  • After minification 110.1 kB
  • After compression 20.1 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 90.1 kB or 82% of the original size.

Image Optimization

-70%

Potential reduce by 1.3 MB

  • Original 1.9 MB
  • After minification 566.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. Obviously, Custom Hearing needs image optimization as it can save up to 1.3 MB or 70% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 223.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 916.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 223.9 kB or 20% of the original size.

CSS Optimization

-0%

Potential reduce by 781 B

  • Original 179.0 kB
  • After minification 179.0 kB
  • After compression 178.2 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. Customhearing.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (67%)

Requests Now

51

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

customhearing.net

customhearing.net

92 ms

customhearing.net

customhearing.net

74 ms

formidableforms.css

formidableforms.css

59 ms

omnia-base.css

omnia-base.css

65 ms

integrity-light.css

integrity-light.css

31 ms

style.css

style.css

22 ms

js_composer.min.css

js_composer.min.css

39 ms

pum-site-styles.css

pum-site-styles.css

28 ms

jquery.min.js

jquery.min.js

57 ms

jquery-migrate.min.js

jquery-migrate.min.js

57 ms

rbtools.min.js

rbtools.min.js

98 ms

rs6.min.js

rs6.min.js

110 ms

js

js

114 ms

rs6.css

rs6.css

96 ms

cs-classic.7.5.6.js

cs-classic.7.5.6.js

109 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

95 ms

x.js

x.js

110 ms

comment-reply.min.js

comment-reply.min.js

238 ms

js_composer_front.min.js

js_composer_front.min.js

111 ms

frm.min.js

frm.min.js

114 ms

api.js

api.js

110 ms

core.min.js

core.min.js

237 ms

pum-site-scripts.js

pum-site-scripts.js

239 ms

mobile-detect.min.js

mobile-detect.min.js

113 ms

cs-google-maps.7.5.6.js

cs-google-maps.7.5.6.js

237 ms

js

js

112 ms

css

css

49 ms

fbevents.js

fbevents.js

172 ms

3Od2DYNZ_fs

3Od2DYNZ_fs

306 ms

custom-hearing-solutions-audiology-and-hearing-aid-technology-300063132.png

custom-hearing-solutions-audiology-and-hearing-aid-technology-300063132.png

304 ms

custom-hearing-solutions-audiology-and-hearing-aid-technology-300063132.js

custom-hearing-solutions-audiology-and-hearing-aid-technology-300063132.js

303 ms

hearing_aids_audiology-1.png

hearing_aids_audiology-1.png

197 ms

hearing_aids_omaha_c-1.jpg

hearing_aids_omaha_c-1.jpg

198 ms

hearing-health-minute-1.png

hearing-health-minute-1.png

199 ms

about_custom_hearing_solutions.png

about_custom_hearing_solutions.png

199 ms

hearing_loss_services.png

hearing_loss_services.png

198 ms

hearing_aids_omaha.png

hearing_aids_omaha.png

300 ms

hearing-aids-lincoln-and-omaha.jpg

hearing-aids-lincoln-and-omaha.jpg

198 ms

signia-logo.png

signia-logo.png

297 ms

unitron_hearing_aids.jpg

unitron_hearing_aids.jpg

296 ms

starkey_hearing_aids.jpg

starkey_hearing_aids.jpg

297 ms

oticon_hearing_aids.jpg

oticon_hearing_aids.jpg

296 ms

resound_hearing_aids.jpg

resound_hearing_aids.jpg

296 ms

recaptcha__en.js

recaptcha__en.js

189 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

145 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

236 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

278 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

302 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

302 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

302 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

300 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

301 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

301 ms

fa-solid-900.ttf

fa-solid-900.ttf

323 ms

fa-brands-400.ttf

fa-brands-400.ttf

277 ms

main.js

main.js

135 ms

www-player.css

www-player.css

95 ms

www-embed-player.js

www-embed-player.js

161 ms

base.js

base.js

217 ms

ad_status.js

ad_status.js

137 ms

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

83 ms

embed.js

embed.js

45 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

13 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

12 ms

id

id

31 ms

legacy.min.css

legacy.min.css

96 ms

Accessibility Review

customhearing.net accessibility score

92

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

button, link, and menuitem elements do not have accessible names.

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

customhearing.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

customhearing.net SEO score

98

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

customhearing.net

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