Tools & Wizards About Us
hearingoncall.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

hearingoncall.com

Hearing Aids Cary, IL | Hearing Aids Arlington Heights, IL

Page Load Speed

8.2 sec in total

First Response

1.1 sec

Resources Loaded

6.5 sec

Page Rendered

626 ms

hearingoncall.com screenshot

About Website

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

Hearing on Call provides hearing aids to Cary, IL , Arlington Heights , IL and the surrounding areas. If you need hearing aids in the Chicago, IL area please give us a call today.

Visit hearingoncall.com

Key Findings

We analyzed Hearingoncall.com page load time and found that the first response time was 1.1 sec and then it took 7.1 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

hearingoncall.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.3 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

www.hearingoncall.com

1122 ms

wc-blocks-vendors-style.css

178 ms

wc-blocks-style.css

309 ms

public-main.css

200 ms

style.min.css

321 ms

Our browser made a total of 163 requests to load all elements on the main page. We found that 90% of them (146 requests) were addressed to the original Hearingoncall.com, 4% (6 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Hearingoncall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (25%)

Content Size

4.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hearingoncall.com main page is 4.7 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. 55% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 140.6 kB

  • Original 166.4 kB
  • After minification 162.7 kB
  • After compression 25.8 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 140.6 kB or 85% of the original size.

Image Optimization

-19%

Potential reduce by 690.2 kB

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

JavaScript Optimization

-42%

Potential reduce by 238.1 kB

  • Original 569.8 kB
  • After minification 569.8 kB
  • After compression 331.7 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 238.1 kB or 42% of the original size.

CSS Optimization

-38%

Potential reduce by 107.6 kB

  • Original 280.7 kB
  • After minification 280.5 kB
  • After compression 173.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. Hearingoncall.com needs all CSS files to be minified and compressed as it can save up to 107.6 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 124 (81%)

Requests Now

154

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hearingoncall.com

www.hearingoncall.com

1122 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

178 ms

wc-blocks-style.css

wc-blocks-style.css

309 ms

public-main.css

public-main.css

200 ms

style.min.css

style.min.css

321 ms

style.css

style.css

201 ms

0696d4f159387c4a3906ce9ea58b81b7.min.css

0696d4f159387c4a3906ce9ea58b81b7.min.css

452 ms

frontend.min.css

frontend.min.css

244 ms

wvs-theme-override.min.css

wvs-theme-override.min.css

267 ms

frontend-tooltip.min.css

frontend-tooltip.min.css

266 ms

jquery.min.js

jquery.min.js

325 ms

jquery-migrate.min.js

jquery-migrate.min.js

337 ms

public-main.js

public-main.js

342 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

266 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

278 ms

wp-polyfill.min.js

wp-polyfill.min.js

279 ms

index.js

index.js

505 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

304 ms

add-to-cart.min.js

add-to-cart.min.js

337 ms

js.cookie.min.js

js.cookie.min.js

503 ms

woocommerce.min.js

woocommerce.min.js

503 ms

cart-fragments.min.js

cart-fragments.min.js

503 ms

isotope.js

isotope.js

510 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

510 ms

avada-faqs.js

avada-faqs.js

511 ms

modernizr.js

modernizr.js

511 ms

jquery.fitvids.js

jquery.fitvids.js

510 ms

fusion-video-general.js

fusion-video-general.js

510 ms

jquery.ilightbox.js

jquery.ilightbox.js

635 ms

jquery.mousewheel.js

jquery.mousewheel.js

634 ms

fusion-lightbox.js

fusion-lightbox.js

633 ms

imagesLoaded.js

imagesLoaded.js

633 ms

packery.js

packery.js

639 ms

avada-portfolio.js

avada-portfolio.js

633 ms

Chart.js

Chart.js

773 ms

fusion-chart.js

fusion-chart.js

718 ms

fusion-column-bg-image.js

fusion-column-bg-image.js

714 ms

cssua.js

cssua.js

654 ms

jquery.waypoints.js

jquery.waypoints.js

632 ms

fusion-waypoints.js

fusion-waypoints.js

629 ms

fusion-animations.js

fusion-animations.js

642 ms

fusion-equal-heights.js

fusion-equal-heights.js

654 ms

fusion-column.js

fusion-column.js

654 ms

jquery.fade.js

jquery.fade.js

607 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

595 ms

fusion-parallax.js

fusion-parallax.js

630 ms

fusion-video-bg.js

fusion-video-bg.js

618 ms

fusion-container.js

fusion-container.js

616 ms

fusion-content-boxes.js

fusion-content-boxes.js

581 ms

jquery.countdown.js

jquery.countdown.js

572 ms

fusion-countdown.js

fusion-countdown.js

573 ms

jquery.countTo.js

jquery.countTo.js

605 ms

jquery.appear.js

jquery.appear.js

579 ms

gtm.js

gtm.js

250 ms

gtm.js

gtm.js

304 ms

shopping-71.png

shopping-71.png

243 ms

photo.jpg

photo.jpg

278 ms

photo.jpg

photo.jpg

276 ms

photo.jpg

photo.jpg

276 ms

logo-2.png

logo-2.png

406 ms

telephone.png

telephone.png

231 ms

photo.jpg

photo.jpg

303 ms

photo.jpg

photo.jpg

457 ms

maps-and-flags.png

maps-and-flags.png

232 ms

fusion-counters-box.js

fusion-counters-box.js

408 ms

jquery.easyPieChart.js

jquery.easyPieChart.js

411 ms

fusion-counters-circle.js

fusion-counters-circle.js

409 ms

fusion-flip-boxes.js

fusion-flip-boxes.js

416 ms

fusion-gallery.js

fusion-gallery.js

479 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

143 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

150 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

171 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

179 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

180 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

179 ms

jquery.fusion_maps.js

jquery.fusion_maps.js

470 ms

fusion-google-map.js

fusion-google-map.js

468 ms

jquery.event.move.js

jquery.event.move.js

471 ms

fusion-image-before-after.js

fusion-image-before-after.js

470 ms

bootstrap.modal.js

bootstrap.modal.js

477 ms

fusion-modal.js

fusion-modal.js

435 ms

fusion-progress.js

fusion-progress.js

416 ms

fusion-recent-posts.js

fusion-recent-posts.js

417 ms

fusion-syntax-highlighter.js

fusion-syntax-highlighter.js

416 ms

bootstrap.transition.js

bootstrap.transition.js

414 ms

bootstrap.tab.js

bootstrap.tab.js

417 ms

fusion-tabs.js

fusion-tabs.js

486 ms

jquery.cycle.js

jquery.cycle.js

409 ms

fusion-testimonials.js

fusion-testimonials.js

397 ms

jquery.textillate.js

jquery.textillate.js

405 ms

fusion-title.js

fusion-title.js

398 ms

bootstrap.collapse.js

bootstrap.collapse.js

406 ms

fusion-toggles.js

fusion-toggles.js

411 ms

vimeoPlayer.js

vimeoPlayer.js

404 ms

fusion-video.js

fusion-video.js

393 ms

jquery.hoverintent.js

jquery.hoverintent.js

389 ms

fusion-vertical-menu-widget.js

fusion-vertical-menu-widget.js

407 ms

lazysizes.js

lazysizes.js

386 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

408 ms

bootstrap.popover.js

bootstrap.popover.js

420 ms

jquery.carouFredSel.js

jquery.carouFredSel.js

423 ms

jquery.easing.js

jquery.easing.js

422 ms

jquery.flexslider.js

jquery.flexslider.js

439 ms

jquery.hoverflow.js

jquery.hoverflow.js

433 ms

jquery.placeholder.js

jquery.placeholder.js

417 ms

jquery.touchSwipe.js

jquery.touchSwipe.js

424 ms

fusion-alert.js

fusion-alert.js

423 ms

fusion-carousel.js

fusion-carousel.js

427 ms

fusion-flexslider.js

fusion-flexslider.js

435 ms

fusion-popover.js

fusion-popover.js

433 ms

fusion-tooltip.js

fusion-tooltip.js

416 ms

fusion-sharing-box.js

fusion-sharing-box.js

433 ms

fusion-blog.js

fusion-blog.js

436 ms

fusion-button.js

fusion-button.js

428 ms

fusion-general-global.js

fusion-general-global.js

432 ms

fusion.js

fusion.js

431 ms

avada-header.js

avada-header.js

415 ms

avada-menu.js

avada-menu.js

427 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

426 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

433 ms

avada-skip-link-focus-fix.js

avada-skip-link-focus-fix.js

431 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

427 ms

avada-comments.js

avada-comments.js

415 ms

avada-general-footer.js

avada-general-footer.js

425 ms

avada-quantity.js

avada-quantity.js

432 ms

avada-scrollspy.js

avada-scrollspy.js

423 ms

avada-select.js

avada-select.js

430 ms

avada-sidebars.js

avada-sidebars.js

420 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

414 ms

avada-tabs-widget.js

avada-tabs-widget.js

413 ms

jquery.toTop.js

jquery.toTop.js

417 ms

avada-to-top.js

avada-to-top.js

415 ms

avada-drop-down.js

avada-drop-down.js

409 ms

avada-contact-form-7.js

avada-contact-form-7.js

406 ms

jquery.elasticslider.js

jquery.elasticslider.js

415 ms

avada-elastic-slider.js

avada-elastic-slider.js

416 ms

avada-woocommerce.js

avada-woocommerce.js

418 ms

avada-fusion-slider.js

avada-fusion-slider.js

414 ms

underscore.min.js

underscore.min.js

410 ms

wp-util.min.js

wp-util.min.js

408 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

415 ms

frontend.min.js

frontend.min.js

429 ms

forms.js

forms.js

429 ms

icomoon.woff

icomoon.woff

413 ms

logo.png

logo.png

414 ms

powered_by_google_on_white.png

powered_by_google_on_white.png

411 ms

top-box-bg-1.jpg

top-box-bg-1.jpg

431 ms

fair-pricing.jpg

fair-pricing.jpg

417 ms

generous.jpg

generous.jpg

413 ms

quality.jpg

quality.jpg

411 ms

pricing-approach.jpg

pricing-approach.jpg

445 ms

list-icon.jpg

list-icon.jpg

444 ms

bg.png

bg.png

751 ms

logo-bg.png

logo-bg.png

412 ms

call-bg.png

call-bg.png

524 ms

arrow.png

arrow.png

413 ms

discliamer.png

discliamer.png

525 ms

www.hearingoncall.com

www.hearingoncall.com

520 ms

slide-5.png

slide-5.png

246 ms

slide-4.png

slide-4.png

429 ms

slide-3.png

slide-3.png

246 ms

home-banner-1-bg_de1a9185-6aa1-4cac-827f-bc8ebbd5c15a.jpg

home-banner-1-bg_de1a9185-6aa1-4cac-827f-bc8ebbd5c15a.jpg

307 ms

home-banner-3-1.jpg

home-banner-3-1.jpg

318 ms

Accessibility Review

hearingoncall.com accessibility score

88

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

Image elements do not have [alt] attributes

Best Practices

hearingoncall.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

hearingoncall.com SEO score

79

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

High

Image elements do not have [alt] attributes

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 Hearingoncall.com 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 Hearingoncall.com 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

hearingoncall.com

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