Tools & Wizards About Us
floridaear.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

floridaear.com

Hearing Care | Hearing Products | TruEAR

Page Load Speed

1.4 sec in total

First Response

16 ms

Resources Loaded

1.2 sec

Page Rendered

250 ms

floridaear.com screenshot

About Website

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

TruEAR provides the best hearing care services, hearing loss treatment and hearing aids to improve your overall hearing health.

Visit floridaear.com

Key Findings

We analyzed Floridaear.com page load time and found that the first response time was 16 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

floridaear.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

floridaear.com

16 ms

truearhearing.com

737 ms

gtm.js

118 ms

matomo.js

112 ms

wpnw-public.css

77 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Floridaear.com, 39% (16 requests) were made to Truearhearing.com and 27% (11 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (737 ms) relates to the external source Truearhearing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.6 kB (5%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Floridaear.com main page is 1.1 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. 40% of websites need less resources to load. Images take 714.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.4 kB

  • Original 71.7 kB
  • After minification 69.6 kB
  • After compression 15.3 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 56.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 714.4 kB
  • After minification 714.4 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. Floridaear images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 298.1 kB
  • After minification 298.1 kB
  • After compression 296.9 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.

Requests Breakdown

Number of requests can be reduced by 25 (64%)

Requests Now

39

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

floridaear.com

floridaear.com

16 ms

truearhearing.com

truearhearing.com

737 ms

gtm.js

gtm.js

118 ms

matomo.js

matomo.js

112 ms

wpnw-public.css

wpnw-public.css

77 ms

swiper-bundle.min.css

swiper-bundle.min.css

64 ms

style.css

style.css

39 ms

jquery.min.js

jquery.min.js

70 ms

566b3f5ad8.js

566b3f5ad8.js

106 ms

css2

css2

108 ms

stream.js

stream.js

63 ms

core.min.js

core.min.js

107 ms

mouse.min.js

mouse.min.js

68 ms

sortable.min.js

sortable.min.js

104 ms

media-check.js

media-check.js

140 ms

modernizr-custom.js

modernizr-custom.js

106 ms

lazyload.js

lazyload.js

63 ms

navigation.js

navigation.js

110 ms

main.js

main.js

110 ms

text-resizer.js

text-resizer.js

112 ms

search.js

search.js

112 ms

api.js

api.js

105 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

111 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

111 ms

wp-polyfill.min.js

wp-polyfill.min.js

138 ms

index.js

index.js

137 ms

parallax.min.js

parallax.min.js

137 ms

Client-Logo.svg

Client-Logo.svg

160 ms

staff-banner2.png

staff-banner2.png

269 ms

cta-sound-levels-color.svg

cta-sound-levels-color.svg

234 ms

cta-sound-levels-white.svg

cta-sound-levels-white.svg

222 ms

cta-book-color.svg

cta-book-color.svg

232 ms

cta-book-white.svg

cta-book-white.svg

226 ms

cta-calendar-color.svg

cta-calendar-color.svg

223 ms

cta-calendar-white.svg

cta-calendar-white.svg

225 ms

staff-split-image.jpg

staff-split-image.jpg

227 ms

hearing-expereince.svg

hearing-expereince.svg

229 ms

matomo.php

matomo.php

202 ms

recaptcha__en.js

recaptcha__en.js

130 ms

central-florida-downtown-orlando_image4%402x-scaled.jpg

central-florida-downtown-orlando_image4%402x-scaled.jpg

151 ms

configs.php

configs.php

81 ms

Accessibility Review

floridaear.com accessibility score

81

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

floridaear.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

floridaear.com SEO score

100

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

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

floridaear.com

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