11.5 sec in total
123 ms
8 sec
3.4 sec
Welcome to whereseattlesmiles.com homepage info - get ready to check Where Seattle Smiles best content for United States right away, or after learning these important things about whereseattlesmiles.com
Need a great Seattle Dentist? Innovative Dentistry is Belltown's leading dental practice in innovation care. Give us a call for your next dental cleaning
Visit whereseattlesmiles.comWe analyzed Whereseattlesmiles.com page load time and found that the first response time was 123 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
whereseattlesmiles.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value14.9 s
0/100
25%
Value12.9 s
2/100
10%
Value1,920 ms
8/100
30%
Value0.191
64/100
15%
Value16.2 s
6/100
10%
123 ms
5032 ms
80 ms
663 ms
586 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whereseattlesmiles.com, 37% (28 requests) were made to Innovativedentistry.com and 24% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Innovativedentistry.com.
Page size can be reduced by 378.3 kB (36%)
1.1 MB
680.8 kB
In fact, the total size of Whereseattlesmiles.com main page is 1.1 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. 85% 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 391.1 kB which makes up the majority of the site volume.
Potential reduce by 220.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. 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 220.7 kB or 86% of the original size.
Potential reduce by 235 B
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. Where Seattle Smiles images are well optimized though.
Potential reduce by 23.7 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 23.7 kB or 11% of the original size.
Potential reduce by 133.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. Whereseattlesmiles.com needs all CSS files to be minified and compressed as it can save up to 133.7 kB or 72% of the original size.
Number of requests can be reduced by 31 (63%)
49
18
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Where Seattle Smiles. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
whereseattlesmiles.com
123 ms
innovativedentistry.com
5032 ms
autoptimize_2a4e42024ef6c552b564816eaaaf6f54.css
80 ms
css
663 ms
dashicons.min.css
586 ms
autoptimize_single_7f16bf88b19c7015e2bcf5f634782cce.css
608 ms
autoptimize_single_befd28fa57325b6ebc3bc78db5868ff7.css
609 ms
autoptimize_single_96bbc5ceab406ff06b4bb013c2065929.css
610 ms
autoptimize_single_7df395abf126f632808cb4c87b555b0e.css
616 ms
autoptimize_single_9af3c03432d18fed5b8e11ea8a0e3f32.css
612 ms
autoptimize_single_e5d4acf54489b9ad123623854c5b5881.css
613 ms
css
734 ms
jquery.min.js
654 ms
lazysizes.min.js
610 ms
regenerator-runtime.min.js
613 ms
wp-polyfill.min.js
1117 ms
hooks.min.js
612 ms
i18n.min.js
613 ms
autoptimize_388a2ee595782ecfaf3be08d0575f9e3.js
616 ms
wp-emoji-release.min.js
120 ms
gtm.js
805 ms
maps
457 ms
dark-pat.png
437 ms
untitled-2608-scaled.jpg
413 ms
front-desk-inner-hero-1024x533-1.jpg
411 ms
google_avatar.png
410 ms
light-pat-alt.png
407 ms
seattle-dental-front-office.jpg
413 ms
fa-solid-900.woff
130 ms
fa-regular-400.woff
15 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
298 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
462 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
684 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf
587 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
587 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
683 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
586 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
587 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
781 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
780 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
779 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
780 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
780 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
779 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
920 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
861 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
860 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
860 ms
eicons.woff
126 ms
fa-brands-400.woff
128 ms
embed
912 ms
1f642.svg
543 ms
2764.svg
460 ms
1f641.svg
462 ms
analytics.js
610 ms
hotjar-527233.js
699 ms
qevents.js
538 ms
fbevents.js
538 ms
Website-Desktop-Logo.png
135 ms
1727422430897923
136 ms
js
104 ms
collect
38 ms
modules.61e17720cf639c3e96a7.js
67 ms
gen_204
40 ms
collect
74 ms
init_embed.js
76 ms
299312427822272
153 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
114 ms
ga-audiences
73 ms
common.js
62 ms
util.js
85 ms
map.js
112 ms
overlay.js
55 ms
onion.js
52 ms
search_impl.js
84 ms
whereseattlesmiles.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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
whereseattlesmiles.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
Missing source maps for large first-party JavaScript
whereseattlesmiles.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whereseattlesmiles.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 Whereseattlesmiles.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.
whereseattlesmiles.com
Open Graph data is detected on the main page of Where Seattle Smiles. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: