Tools & Wizards About Us
precisehearing.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

precisehearing.com

Welcome to Precise Hearing - Your Source for Discount Hearing Aids

Page Load Speed

3.2 sec in total

First Response

170 ms

Resources Loaded

2.9 sec

Page Rendered

126 ms

precisehearing.com screenshot

About Website

Click here to check amazing Precise Hearing content for United States. Otherwise, check out these important facts you probably never knew about precisehearing.com

Precise Hearing is your one-stop source for saving thousands of dollars on discount hearing aids from brand names such as Signia and Sonic! We offer the best in hearing aid technology as well as acces...

Visit precisehearing.com

Key Findings

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

Performance Metrics

precisehearing.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value5,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

precisehearing.com

170 ms

www.precisehearing.com

389 ms

4782a518-4f1a-4dcf-a6d0-b9345f812757.css

84 ms

48346c5d-af63-4949-9987-8ed8d361372d.css

91 ms

583138a3-c699-4e31-852e-77939d6b6d98.css

90 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 19% of them (8 requests) were addressed to the original Precisehearing.com, 40% (17 requests) were made to Hb.wpmucdn.com and 14% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (681 ms) relates to the external source Hb.wpmucdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.8 kB (29%)

Content Size

430.9 kB

After Optimization

307.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Precisehearing.com main page is 430.9 kB. 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. Javascripts take 191.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 81.0 kB

  • Original 100.2 kB
  • After minification 94.7 kB
  • After compression 19.2 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 81.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 34 B
  • After minification 34 B

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. Precise Hearing images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 19.3 kB

  • Original 191.9 kB
  • After minification 191.9 kB
  • After compression 172.6 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

-17%

Potential reduce by 23.5 kB

  • Original 138.7 kB
  • After minification 138.7 kB
  • After compression 115.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. Precisehearing.com needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (91%)

Requests Now

32

After Optimization

3

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Precise 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 20 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

precisehearing.com

precisehearing.com

170 ms

www.precisehearing.com

www.precisehearing.com

389 ms

4782a518-4f1a-4dcf-a6d0-b9345f812757.css

4782a518-4f1a-4dcf-a6d0-b9345f812757.css

84 ms

48346c5d-af63-4949-9987-8ed8d361372d.css

48346c5d-af63-4949-9987-8ed8d361372d.css

91 ms

583138a3-c699-4e31-852e-77939d6b6d98.css

583138a3-c699-4e31-852e-77939d6b6d98.css

90 ms

385f6984-eac7-4bc9-b971-48ed4e024ef3.css

385f6984-eac7-4bc9-b971-48ed4e024ef3.css

111 ms

2673b160-614a-4fd7-adf3-837542b6e902.css

2673b160-614a-4fd7-adf3-837542b6e902.css

183 ms

fbf77cd7-a93a-4e80-ba29-ea55d6c6e53f.css

fbf77cd7-a93a-4e80-ba29-ea55d6c6e53f.css

91 ms

43e82298-239e-41e4-82aa-e775bd841223.css

43e82298-239e-41e4-82aa-e775bd841223.css

681 ms

b1cac78b-cd45-4d7e-b300-3b8aaf56c96b.js

b1cac78b-cd45-4d7e-b300-3b8aaf56c96b.js

232 ms

76b928a9-9cd1-457c-b40f-b5e8967e1bc9.js

76b928a9-9cd1-457c-b40f-b5e8967e1bc9.js

156 ms

swap.js

swap.js

78 ms

rbtools.min.js

rbtools.min.js

233 ms

rs6.min.js

rs6.min.js

434 ms

css

css

49 ms

8bbd24ae-ea3d-4e00-81b4-0f1d105f7791.css

8bbd24ae-ea3d-4e00-81b4-0f1d105f7791.css

167 ms

fbd127d3-9df7-4950-b36c-6b965fa3012c.css

fbd127d3-9df7-4950-b36c-6b965fa3012c.css

194 ms

js

js

68 ms

16935d2f-56a3-4de0-bc44-206023b22006.js

16935d2f-56a3-4de0-bc44-206023b22006.js

186 ms

wp-polyfill.min.js

wp-polyfill.min.js

174 ms

b3bc83f0-6093-4d87-9bc5-b73f880a5c0e.js

b3bc83f0-6093-4d87-9bc5-b73f880a5c0e.js

303 ms

fe13cd5f-db64-41ee-8049-b6b81a6d38d2.js

fe13cd5f-db64-41ee-8049-b6b81a6d38d2.js

521 ms

rs6.min.js

rs6.min.js

436 ms

a2173bed-8acc-4e80-a055-3b0241a003de.js

a2173bed-8acc-4e80-a055-3b0241a003de.js

266 ms

ce1c6299-14ae-43e5-81bf-47c6a51b1241.js

ce1c6299-14ae-43e5-81bf-47c6a51b1241.js

214 ms

gtm.js

gtm.js

72 ms

bat.js

bat.js

279 ms

fqzvtgn585

fqzvtgn585

284 ms

gtm.js

gtm.js

130 ms

5ldgw7rwjx

5ldgw7rwjx

339 ms

dummy.png

dummy.png

272 ms

32664572-c032-40f6-824d-dbda12d900da.css

32664572-c032-40f6-824d-dbda12d900da.css

220 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

285 ms

WooCommerce.woff

WooCommerce.woff

183 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

116 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

165 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

191 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

192 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

194 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

193 ms

js

js

173 ms

clarity.js

clarity.js

71 ms

Accessibility Review

precisehearing.com accessibility score

91

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

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>).

Best Practices

precisehearing.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

precisehearing.com 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 Precisehearing.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 Precisehearing.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

precisehearing.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: