5.2 sec in total
135 ms
2 sec
3.1 sec
Welcome to kingsandia.com homepage info - get ready to check King Sandia best content right away, or after learning these important things about kingsandia.com
When you need hearing aids, you need a practice you can trust. Call us at Sandia Hearing Aids & King Hearing Aids in Colorado Springs, CO & Pueblo, CO.
Visit kingsandia.comWe analyzed Kingsandia.com page load time and found that the first response time was 135 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kingsandia.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value6.7 s
8/100
25%
Value6.4 s
40/100
10%
Value810 ms
36/100
30%
Value0.013
100/100
15%
Value12.3 s
15/100
10%
135 ms
209 ms
130 ms
132 ms
205 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 21% of them (13 requests) were addressed to the original Kingsandia.com, 43% (26 requests) were made to Fonts.gstatic.com and 10% (6 requests) were made to Siteminds.net. The less responsive or slowest element that took the longest time to load (648 ms) relates to the external source Reviewtube.com.
Page size can be reduced by 276.4 kB (33%)
850.0 kB
573.7 kB
In fact, the total size of Kingsandia.com main page is 850.0 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. Images take 451.2 kB which makes up the majority of the site volume.
Potential reduce by 158.9 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 158.9 kB or 83% of the original size.
Potential reduce by 14.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. King Sandia images are well optimized though.
Potential reduce by 93.3 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 93.3 kB or 55% of the original size.
Potential reduce by 9.5 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. Kingsandia.com needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 25% of the original size.
Number of requests can be reduced by 15 (54%)
28
13
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of King Sandia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
kingsandia.com
135 ms
kingsandia.com
209 ms
ca14bc18-9369-4053-9b94-098bb95061b3.css
130 ms
f5295440-d848-4f6f-add2-06745ab4cdde.css
132 ms
all.min.js
205 ms
mind_loader.php
344 ms
565249d9-a494-46e7-912c-d3516fb25e97.js
345 ms
scripts.min.js
163 ms
4399fbb7-da33-489b-84a1-6474795b88e2.js
166 ms
gtm.js
252 ms
e_insights.php
648 ms
widget.js
468 ms
logos-combined.jpg
350 ms
header-banners-home-updated.jpg
417 ms
pattern-bg.jpg
416 ms
cta-bg-home.jpg
351 ms
Sandia-Hearing-Aids-logo276-white.png
350 ms
king-hearing-aids-logo-pueblo-co.png
461 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
463 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
484 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
486 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
486 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
485 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
484 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
480 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
486 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
487 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
487 ms
wEO_EBrAnc9BLjLQAUk1WPoM.woff
387 ms
wEO_EBrAnc9BLjLQAUk1WPoP.ttf
389 ms
fa-solid-900.woff
450 ms
fa-brands-400.woff
451 ms
fa-regular-400.woff
447 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuvMQQ.woff
384 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuvMQg.ttf
387 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuvMQQ.woff
387 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhDuvMQg.ttf
389 ms
modules.ttf
448 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
389 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
442 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
443 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
443 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
442 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
441 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
443 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
449 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
449 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
448 ms
956a2cd4-8ae8-4f36-947e-45fffeef23a8.css
133 ms
mind_rs_prd.php
343 ms
tingle.min.css
163 ms
css
53 ms
directional.png
233 ms
mind_local.css
105 ms
mind_jsn_chk_av.php
110 ms
br.php
298 ms
jquery.min.js
31 ms
css
18 ms
gocast_combined_g16.css
173 ms
x-64.png
243 ms
info-64t.png
124 ms
kingsandia.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
kingsandia.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
Browser errors were logged to the console
kingsandia.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Kingsandia.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 Kingsandia.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.
kingsandia.com
Open Graph data is detected on the main page of King Sandia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: