2.9 sec in total
149 ms
2.2 sec
638 ms
Click here to check amazing Earq content for Belarus. Otherwise, check out these important facts you probably never knew about earq.com
CQ Partners helps to grow hearing healthcare practices. We support every aspect of your business, from operations, to marketing and digital presence.
Visit earq.comWe analyzed Earq.com page load time and found that the first response time was 149 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
earq.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value5.0 s
27/100
25%
Value7.6 s
26/100
10%
Value1,700 ms
11/100
30%
Value0.105
88/100
15%
Value12.5 s
14/100
10%
149 ms
540 ms
109 ms
180 ms
294 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 87% of them (48 requests) were addressed to the original Earq.com, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Cdn.optimizely.com. The less responsive or slowest element that took the longest time to load (603 ms) belongs to the original domain Earq.com.
Page size can be reduced by 534.1 kB (36%)
1.5 MB
940.6 kB
In fact, the total size of Earq.com main page is 1.5 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. 45% of websites need less resources to load. Images take 772.9 kB which makes up the majority of the site volume.
Potential reduce by 18.0 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 18.0 kB or 77% of the original size.
Potential reduce by 28.6 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. Earq images are well optimized though.
Potential reduce by 379.2 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 379.2 kB or 69% of the original size.
Potential reduce by 108.4 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. Earq.com needs all CSS files to be minified and compressed as it can save up to 108.4 kB or 86% of the original size.
Number of requests can be reduced by 5 (9%)
53
48
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Earq. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
earq.com
149 ms
www.earq.com
540 ms
styles_ie.css
109 ms
min.css
180 ms
styles.css
294 ms
compressed_javascript_3.js
454 ms
2421880516.js
246 ms
js
92 ms
geoip2.js
57 ms
earq_animations.js
300 ms
analytics.js
49 ms
little_q.png
83 ms
banner_autumn3.jpg
400 ms
firstVisit_patient.jpg
79 ms
firstVisit_tammy.jpg
78 ms
firstVisit_device.jpg
141 ms
zag_tiny_white.png
114 ms
zag_large_right.png
177 ms
4-year-warranty2.jpg
223 ms
loading_ring_24.gif
193 ms
icon_map_white.png
219 ms
icon_magnifying_white.png
218 ms
icon_phone_white.png
295 ms
earq-logo.png
299 ms
loading_thin.gif
323 ms
leftBlurbTalkieBlue3.png
367 ms
x_gray_small.png
353 ms
foundBox_x3.png
443 ms
home_banner.php
362 ms
home_tiles.php
385 ms
collect
5 ms
collect
58 ms
device_base_mq.jpg
603 ms
featuredDevice_ody.png
413 ms
zag_tiny_brown.png
407 ms
tiles_home.json
81 ms
ears_and_balance.jpg
142 ms
OKU_2016.jpg
93 ms
Widex_logo.jpg
127 ms
NFLPA_Smocks_and_Jocks_2016.jpg
125 ms
starkey_expo_2016.jpg
124 ms
leadership_expansion_2016.jpg
170 ms
blog_noisytoys.jpg
213 ms
nflpa_vegas_2015.jpg
210 ms
blog_ha_parts.jpg
224 ms
MassachusettsHearingSociety_2015.jpg
225 ms
hp_invisible.jpg
223 ms
hp_smartphone.jpg
265 ms
hp_active3.jpg
295 ms
hp_family.jpg
301 ms
hp_tinnitusRelief.jpg
306 ms
hp_discount.jpg
314 ms
ed_anatomy_2.jpg
327 ms
hp_kids.jpg
348 ms
collect
22 ms
earq.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
earq.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
earq.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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Earq.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 Earq.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
earq.com
Open Graph data is detected on the main page of Earq. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: