8.9 sec in total
3.9 sec
4.6 sec
350 ms
Visit eargear.com now to see the best up-to-date Eargear content and also check out these interesting facts you probably never knew about eargear.com
Etymotic offers high definition listening, hearing, assessment, enhancement & protection with specially engineered innovative products.
Visit eargear.comWe analyzed Eargear.com page load time and found that the first response time was 3.9 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eargear.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value12.8 s
0/100
25%
Value16.9 s
0/100
10%
Value4,790 ms
0/100
30%
Value0.596
11/100
15%
Value23.5 s
1/100
10%
3909 ms
27 ms
49 ms
49 ms
50 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Eargear.com, 24% (24 requests) were made to Media.etymotic.com and 19% (19 requests) were made to Js.etymotic.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Etymotic.com.
Page size can be reduced by 1.1 MB (68%)
1.7 MB
547.0 kB
In fact, the total size of Eargear.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 969.2 kB which makes up the majority of the site volume.
Potential reduce by 93.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. This page needs HTML code to be minified as it can gain 19.4 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 93.1 kB or 90% of the original size.
Potential reduce by 37.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, Eargear needs image optimization as it can save up to 37.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 723.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 723.6 kB or 75% of the original size.
Potential reduce by 295.0 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. Eargear.com needs all CSS files to be minified and compressed as it can save up to 295.0 kB or 85% of the original size.
Number of requests can be reduced by 65 (68%)
95
30
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eargear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
hearing-protection.html
3909 ms
jquery.min.js
27 ms
calendar-win2k-1.css
49 ms
widgets.css
49 ms
downloads.css
50 ms
mirasvit_searchindex.css
53 ms
custommenu.css
55 ms
bootstrap.min.css
70 ms
bootstrap-theme.min.css
56 ms
magnific-popup.css
59 ms
yamm.css
64 ms
styles.css
87 ms
sdocp.css
80 ms
prototype.js
58 ms
ccard.js
48 ms
validation.js
52 ms
builder.js
48 ms
effects.js
61 ms
dragdrop.js
57 ms
controls.js
63 ms
slider.js
60 ms
js.js
61 ms
form.js
79 ms
menu.js
78 ms
translate.js
81 ms
cookies.js
80 ms
iwd-jquery-2.1.3.min.js
128 ms
modal.js
81 ms
calendar.js
144 ms
captcha.js
126 ms
calendar-setup.js
143 ms
downloads.js
74 ms
custommenu.js
76 ms
jquery.js
123 ms
font-awesome.min.css
35 ms
css
46 ms
full.js
49 ms
bootstrap.min.js
116 ms
holder.min.js
114 ms
jquery.magnific-popup.min.js
130 ms
functions.min.js
129 ms
print.css
64 ms
analytics.js
49 ms
nav_consumer_products_v3_sm_opt.png
111 ms
widget.js
27 ms
styles.css
217 ms
rd-styles.js
136 ms
pr_override.css
25 ms
contents.js
28 ms
header_bg_inner.png
23 ms
logo.png
24 ms
icon-search.png
26 ms
icon-cart.png
24 ms
caret-right.png
84 ms
page-bg.png
83 ms
spacer_10_1.png
85 ms
nav_pro_products_v3_150_opt.png
85 ms
spacer_10.png
84 ms
nav_aboutus_v1_opt.png
85 ms
nav-support_v1.png
86 ms
etymotic-banner-images_new_HP_v5.jpg
87 ms
er20sx_main_450_v2.jpg.png
88 ms
er20xs_uf_450_main_v2.png
94 ms
er20xs_ms_450_main_v2.png
96 ms
products_450_etyplugs_v2_1.jpg
89 ms
products_450_etyplugshd_v2.jpg
92 ms
products_450_me_v3.jpg
94 ms
products_450_mp_v2.jpg
94 ms
products_450_gsp_v2.jpg
96 ms
products_450_hd15_v2_1.jpg
99 ms
products_450_eb15_v2.jpg
97 ms
ek5_450_v3.jpg
98 ms
ek3_450_v3b.jpg
99 ms
hd5_450_v2.jpg
99 ms
80-facebook.png
100 ms
80-linkedin.png
99 ms
90-youtube-2.png
101 ms
80-audiofile.png
100 ms
collect
35 ms
collect
69 ms
stars_small.gif
34 ms
v1.gif
32 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
11 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
16 ms
glyphicons-halflings-regular.woff
12 ms
v1.gif
8 ms
v1.gif
6 ms
contents.js
7 ms
contents.js
7 ms
contents.js
8 ms
contents.js
7 ms
contents.js
7 ms
contents.js
7 ms
contents.js
6 ms
contents.js
7 ms
contents.js
9 ms
spinner.gif
32 ms
close-button.png
29 ms
eargear.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
eargear.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eargear.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eargear.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 Eargear.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.
eargear.com
Open Graph description is not detected on the main page of Eargear. 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: