1.3 sec in total
67 ms
881 ms
373 ms
Click here to check amazing Locations Starkey content for United States. Otherwise, check out these important facts you probably never knew about locations.starkey.com
Find a trusted audiologist or hearing aid center near you. Starkey hearing professionals will help find the right hearing aid for your type of hearing loss, lifestyle, and budget.
Visit locations.starkey.comWe analyzed Locations.starkey.com page load time and found that the first response time was 67 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
locations.starkey.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value5.6 s
17/100
25%
Value3.9 s
82/100
10%
Value2,000 ms
8/100
30%
Value0.7
7/100
15%
Value17.8 s
4/100
10%
67 ms
18 ms
72 ms
80 ms
110 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Locations.starkey.com, 33% (18 requests) were made to Assets.locations.starkey.com and 19% (10 requests) were made to Starkey.com. The less responsive or slowest element that took the longest time to load (440 ms) relates to the external source Starkey.com.
Page size can be reduced by 108.2 kB (12%)
909.2 kB
801.0 kB
In fact, the total size of Locations.starkey.com main page is 909.2 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. 75% 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. Javascripts take 522.9 kB which makes up the majority of the site volume.
Potential reduce by 77.7 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 10.3 kB, which is 11% 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 77.7 kB or 80% of the original size.
Potential reduce by 10.5 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. Locations Starkey images are well optimized though.
Potential reduce by 19.8 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.
Potential reduce by 198 B
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. Locations.starkey.com has all CSS files already compressed.
Number of requests can be reduced by 31 (74%)
42
11
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locations Starkey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
locations.starkey.com
67 ms
locations.starkey.com
18 ms
styles.min.css
72 ms
client.min.css
80 ms
scripts.min.js
110 ms
client.min.js
110 ms
ga.js
116 ms
utag.js
177 ms
logo-starkey.svg
439 ms
jquery.rlsmaps_v2.min.js
50 ms
nearby.svg
14 ms
bg-sched-appt.jpg
28 ms
bg-technology-hdr.jpg
27 ms
hearing-aids.png
440 ms
hearing%20loss.png
364 ms
facebook.svg
293 ms
instagram.svg
334 ms
twitter.svg
332 ms
youtube.svg
382 ms
linkedin.svg
380 ms
blogger.svg
381 ms
icon-global-locations.svg
417 ms
din_next_regular.woff
28 ms
20007504-6ea2-4d68-93e4-f4769b5d9f14.woff
39 ms
din_next_bold.woff
40 ms
mreavesxlsanr-071211001EmigreWebOnly.woff
26 ms
mreavesxlsanbk-071211001EmigreWebOnly.woff
27 ms
glyphicons-halflings-regular.woff
71 ms
mreavesxlsanot-bold-webfont.woff
71 ms
mreavesxlsanot-reg-webfont.woff
72 ms
mreavesxlsanot-book-webfont.woff
73 ms
mreavesxlsanb-071211001EmigreWebOnly.woff
70 ms
js
86 ms
utag.5.js
44 ms
utag.46.js
117 ms
utag.62.js
37 ms
utag.54.js
117 ms
utag.65.js
92 ms
utag.77.js
102 ms
utag.98.js
187 ms
load.js
220 ms
ts.js
144 ms
5254ecc8415044f89bc4e2074cbc12d5.js.ubembed.com
123 ms
analytics.js
29 ms
bat.js
42 ms
js
29 ms
4029974.js
11 ms
4029974
56 ms
invoca-latest.min.js
48 ms
utag.v.js
21 ms
collect
10 ms
bundle.js
48 ms
clarity.js
22 ms
c.gif
7 ms
locations.starkey.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.
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 IDs are not unique
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
locations.starkey.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
Page has valid source maps
locations.starkey.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locations.starkey.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 Locations.starkey.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.
locations.starkey.com
Open Graph description is not detected on the main page of Locations Starkey. 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: