5.9 sec in total
434 ms
2.3 sec
3.1 sec
Welcome to sweetsmile.com homepage info - get ready to check Sweetsmile best content right away, or after learning these important things about sweetsmile.com
featuring San Francisco Bay Area photographers Dave Wong and Gregory Bartning photographs of weddings, events and portraits
Visit sweetsmile.comWe analyzed Sweetsmile.com page load time and found that the first response time was 434 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sweetsmile.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.1 s
74/100
25%
Value2.9 s
95/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
434 ms
103 ms
134 ms
137 ms
137 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 91% of them (30 requests) were addressed to the original Sweetsmile.com, 6% (2 requests) were made to W.sharethis.com and 3% (1 request) were made to S.w.org. The less responsive or slowest element that took the longest time to load (434 ms) belongs to the original domain Sweetsmile.com.
Page size can be reduced by 103.8 kB (10%)
1.0 MB
910.8 kB
In fact, the total size of Sweetsmile.com main page is 1.0 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. 35% of websites need less resources to load. Images take 822.2 kB which makes up the majority of the site volume.
Potential reduce by 56.3 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 56.3 kB or 84% of the original size.
Potential reduce by 25.0 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. Sweetsmile images are well optimized though.
Potential reduce by 12.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 12.8 kB or 13% of the original size.
Potential reduce by 9.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. Sweetsmile.com needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 33% of the original size.
Number of requests can be reduced by 14 (48%)
29
15
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweetsmile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.sweetsmile.com
434 ms
wp-emoji-release.min.js
103 ms
style.min.css
134 ms
style.css
137 ms
frontend.min.css
137 ms
jquery.min.js
249 ms
jquery-migrate.min.js
130 ms
buttons.js
8 ms
1431529216_script.js
171 ms
1431529216_style.css
271 ms
buttons.js
23 ms
jquery.cycle.all.min.js
175 ms
wp-embed.min.js
171 ms
logo_1330812964.png
130 ms
masthead_image1_1330812950.jpg
300 ms
colleen-kyle-lake-tahoe-homewood-wedding-0012.jpg
242 ms
colleen-kyle-lake-tahoe-homewood-wedding-0022(pp_w860_h573).jpg
246 ms
colleen-kyle-lake-tahoe-homewood-wedding-0032.jpg
244 ms
blank.gif
73 ms
late_august_blog_bg.jpg
125 ms
late_august_blog_bg_inner.png
182 ms
footer_btm_cap_1330809493.png
191 ms
late_august_primary_nav_menu_bg.png
246 ms
body_bg_1330812850.png
254 ms
bio_inner_bg_1330812824.png
294 ms
bio_separator_1330812786.png
296 ms
late_august_page_and_post_bg.png
297 ms
late_august_call_to_action_separator_img.png
311 ms
late_august_all_inner_content_bg.png
320 ms
1f642.svg
20 ms
DroidSans-webfont.woff
310 ms
LobsterTwo-Regular-webfont.woff
321 ms
ajax-comments.js
319 ms
sweetsmile.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.
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.
sweetsmile.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sweetsmile.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweetsmile.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 Sweetsmile.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.
sweetsmile.com
Open Graph data is detected on the main page of Sweetsmile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: