21.7 sec in total
320 ms
20.8 sec
572 ms
Visit eargo.com now to see the best up-to-date Eargo content for United States and also check out these interesting facts you probably never knew about eargo.com
Hear life to the fullest with Eargo's virtually invisible, comfortable, and rechargeable hearing aids.
Visit eargo.comWe analyzed Eargo.com page load time and found that the first response time was 320 ms and then it took 21.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
eargo.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value33.9 s
0/100
25%
Value14.7 s
1/100
10%
Value1,140 ms
22/100
30%
Value0.37
29/100
15%
Value28.8 s
0/100
10%
320 ms
20 ms
43 ms
46 ms
51 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 6% of them (8 requests) were addressed to the original Eargo.com, 34% (47 requests) were made to D9jpa82qnx9c8.cloudfront.net and 10% (14 requests) were made to Mmtro.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Trc.taboola.com.
Page size can be reduced by 2.1 MB (22%)
9.4 MB
7.4 MB
In fact, the total size of Eargo.com main page is 9.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.2 MB which makes up the majority of the site volume.
Potential reduce by 70.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 70.1 kB or 76% of the original size.
Potential reduce by 384.1 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. Eargo images are well optimized though.
Potential reduce by 931.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 931.6 kB or 70% of the original size.
Potential reduce by 697.7 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. Eargo.com needs all CSS files to be minified and compressed as it can save up to 697.7 kB or 88% of the original size.
Number of requests can be reduced by 76 (61%)
125
49
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eargo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
eargo.com
320 ms
font-awesome.min.css
20 ms
css
43 ms
application-7d66ac88bbe2f1ea3a3680990adbde83.css
46 ms
main+desktop-2b661bab2f976e3f3e8cfc5d931de582.css
51 ms
application-6892404de00fa19d456b232d191a68f2.js
69 ms
ld.js
21 ms
eargo.min.js
46 ms
statistics.asp
187 ms
track.js
188 ms
gtm.js
93 ms
fbevents.js
134 ms
quant.js
138 ms
web
90 ms
loadsamplepack
88 ms
PCMAG-long.png
176 ms
tc-techcrunch_White.png
178 ms
geekwire-logo_White-c.png
175 ms
the-verge-logo1.png
178 ms
Whoopi-Name_FB-White.png
178 ms
popular-science3.png
179 ms
EARGO-Logo-Header-new.png
81 ms
expand_arrow-95ca4f141416f77affea8c140c4fee2a.png
82 ms
Phone-Icon-956f8e1f07ab151d8381541c687abf29.png
81 ms
Cart.jpg
123 ms
Button-Green-NoText-029e32679992420853712f80e891454a.png
123 ms
BacktoTop-7efb7c34335f529c8cfb11071f4724e7.png
122 ms
EargoPlus_NavForm-X-a1eab4288c962b33b7884ff4f7b730bd.png
123 ms
EARGO_SITE_V3-c67644912ac48d77bb4fed8a70917232.jpg
124 ms
Introducing_EargoPlus-54912080c70d5d790c6779b3be8c2be5.jpg
125 ms
Site_Rotator_3WhyEargoNew-da268f52377f9afe28ebdc891fee6935.jpg
132 ms
Invisible_Man_Rotator-9dd513c9883ba27af4cfe67de0d70731.jpg
131 ms
Coming_In_Jan-56d734190c27588db653fc7f565e59e8.png
123 ms
EARGO_SITE_Tablet-3a944dec498b7fa984a1f41e8527d0ea.jpg
125 ms
Introducing_TABLET_Rotator_No-Button-96cc8ca0eb11a44bef35fe1ffb9578fd.jpg
132 ms
Technology_TABLET_Rotator_No_Button-e4c48358a020d7b8e22a9b0570cdca93.jpg
125 ms
Invisible_TABLET_Rotator_No_Button-edb07bde48996293abee52ec5e3802fd.jpg
124 ms
EARGO_SITE_MOB_V3-23ecad91f5a75a94da67fedcdf21db83.jpg
128 ms
Introducing_Mobile_Rotator_No_Button-de7ebacfab5035135afbc65f4eaf9452.jpg
127 ms
Technology_Rotator_Mobile_Type_No%20Button-8a825144cd8ded76ef094f66d43eabf4.jpg
126 ms
Invisible_Mobile_Rotator_Type_No_Button-35d34ba61f6406949f8219b984f17613.jpg
128 ms
1CORP_WhatsNew_Lockup-fbd85e376eee745576255856664a821e.png
127 ms
MoreRange2-0fba20455e05f5144ef6ddb872c7ac50.png
128 ms
Snap3-c8229da8f87c78d198110ed47bd8336a.png
129 ms
Eargo-Difference-Invisible-3f68e5ec050e6325feb956763ff18a53.png
129 ms
Eargo-Difference-Comfortable-7264042e4ec91a16d3f3107f131bff95.png
130 ms
Eargo-Difference-NaturalSounding-3dc821d294c2c2e6cf1f68133044e4f4.png
131 ms
Eargo-Difference-EasytoUse-3e8e39caf379278a273c6d3398c0e7fc.png
130 ms
Play-icon-e7671b1fb13d6a497e7de1de1b38d0e6.png
130 ms
DannyR-Eargo-Testimonial-9088af815c1c5090c997e6e109c2a027.jpg
131 ms
SylvaC-Eargo-Testimonial-bfc281e6a8745aae0af79165c7ff24a0.jpg
133 ms
DanielA-Eargo-Testimonial-6a2808bdd3e5bed2caf2fee643473dc2.jpg
132 ms
MikeT-Eargo-Testimonial-418e672849a4ffb794318ed08b5145c1.jpg
132 ms
V4_Background.jpg
131 ms
V4_Background-487420595a0a9f200c09897e8f5ac2de.jpg
132 ms
V4_Florent-aa701f7b256fc0da065a0c752008e54a.png
133 ms
V4_FlyFishvsDevice-d8e0eac9e1991abfb768333d0621f251.png
75 ms
event
60 ms
fontawesome-webfont.woff
54 ms
EargoPlus_Corp_HowitWorksBG_V2.jpg
58 ms
EargoPlus_Corp_HowitWorksBG_V2-f40efbffd568acf25294b70944daa486.jpg
58 ms
tfa.js
34 ms
Icon-PlaceOrder_v2-d5eb7f0e517f0f3324df94c0c4e85deb.png
73 ms
push
253 ms
push
244 ms
Icon-PopThemIn_v2-7c0bc99519e563423502cb46d53ef5b4.png
49 ms
Icon-HHP_v2-7893c5ca1dbcf30a19f365c9cbcb87ae.png
49 ms
Icon-Guarantee_v2-4233fd39037a56b099ee6ccb1e0444aa.png
48 ms
EargoPlus_NavForm_Sample-2c8f848a976c807ce7c62b3939573594.png
48 ms
xmark_close-8ee8f6484299c30cc4db1e8bb1e71fc6.png
48 ms
i.js
72 ms
cd07795c8334ba52f38d767f6762eb0ec3701e2d.2.js
34 ms
analytics.js
30 ms
conversion_async.js
32 ms
2559.js
67 ms
bat.js
64 ms
aquant.js
65 ms
1368091972.js
110 ms
qevents.js
84 ms
gtm.js
28 ms
tfa.js
27 ms
tro.js
215 ms
obtp.js
86 ms
438011993042257
15 ms
rules-p-nYECaWq9G0PUk.js
44 ms
mark
20138 ms
oct.js
52 ms
ec.js
22 ms
167 ms
track-visibility.aspx
234 ms
push
233 ms
36 ms
create.gif
211 ms
collect
6 ms
collect
148 ms
pixel
139 ms
pixel
20071 ms
pixel
247 ms
a1368091972.html
135 ms
event
408 ms
adsct
151 ms
uwt.js
15 ms
pixel;r=48248319;labels=_fp.event.Homepage;rf=0;a=p-nYECaWq9G0PUk;url=http%3A%2F%2Feargo.com%2F;fpan=1;fpa=P0-1900531288-1504689368932;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504689368932;tzo=-180;ogl=title.Eargo%20Hearing%20Device%2Cdescription.%2Curl.http%3A%2F%2Fwww%252Eeargo%252Ecom%2Cimage.%2Fassets%2FGeneral%2FSocial-linkedin%252Ejpg%2Ctitle.Eargo%20Hearing%20Device%2Cdescription.%2Curl.http%3A%2F%2Fwww%252Eeargo%252Ecom%2Cimage.%2Fassets%2FGeneral%2FSocial-linkedin%252Ejpg
15 ms
tro.js
80 ms
41 ms
adsct
148 ms
ga-audiences
29 ms
exec.js
73 ms
p
75 ms
sync.js
125 ms
pixel
14 ms
cs
136 ms
liveramp
75 ms
sync
96 ms
s
65 ms
s
129 ms
s
64 ms
s
89 ms
s
81 ms
3 ms
447836.gif
5 ms
s
69 ms
event
4 ms
event
5 ms
ping
66 ms
s
76 ms
s
66 ms
pixel.gif
22 ms
s
76 ms
nr-1044.min.js
48 ms
dis.aspx
45 ms
s
116 ms
adsct
93 ms
adsct
91 ms
pixel
33 ms
u
81 ms
pixel
34 ms
8a8a98b7cc
105 ms
match.aspx
13 ms
eargo.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
eargo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
eargo.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eargo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eargo.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.
eargo.com
Open Graph description is not detected on the main page of Eargo. 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: