7.9 sec in total
889 ms
6.6 sec
412 ms
Click here to check amazing Smith Smile content. Otherwise, check out these important facts you probably never knew about smithsmile.com
Smith Smile Orthodontics is located in Canton and Marietta, Georgia. We offer several areas of orthodontics utilizing the latest technology such as Invisalign, Invisalign Teen, Damon, and Radiance.
Visit smithsmile.comWe analyzed Smithsmile.com page load time and found that the first response time was 889 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
smithsmile.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value9.1 s
1/100
25%
Value13.8 s
1/100
10%
Value3,080 ms
2/100
30%
Value0.023
100/100
15%
Value31.4 s
0/100
10%
889 ms
285 ms
275 ms
280 ms
228 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 17% of them (24 requests) were addressed to the original Smithsmile.com, 14% (21 requests) were made to Static.xx.fbcdn.net and 14% (21 requests) were made to Cdnsm1-clradscript.civiclive.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Smithsmile.com.
Page size can be reduced by 254.5 kB (5%)
5.2 MB
4.9 MB
In fact, the total size of Smithsmile.com main page is 5.2 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 4.2 MB which makes up the majority of the site volume.
Potential reduce by 58.1 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 58.1 kB or 63% of the original size.
Potential reduce by 32.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. Smith Smile images are well optimized though.
Potential reduce by 131.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 131.3 kB or 20% of the original size.
Potential reduce by 32.6 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. Smithsmile.com needs all CSS files to be minified and compressed as it can save up to 32.6 kB or 19% of the original size.
Number of requests can be reduced by 92 (71%)
129
37
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smith Smile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.smithsmile.com
889 ms
vendor.cfcd208495d565ef66e7dff9f98764da.js
285 ms
vendor.cfcd208495d565ef66e7dff9f98764da.css
275 ms
js
280 ms
televox-script-v1.js
228 ms
jumpLink.css
237 ms
centered.css
237 ms
centered.js
236 ms
starterPackage-script-v1.js
245 ms
buttons.js
244 ms
reactPortletLoader.js
358 ms
ReactPortletsInit.js
331 ms
merged.css
281 ms
jquery.mmenu.all.css
357 ms
jquery.mmenu.min.all.js
271 ms
mobilemenu.css
358 ms
mobilemenu2019.v2.js
275 ms
spinnerAlert.js
363 ms
sweetalert2.js
520 ms
ContentLibraryPopup.css
381 ms
common.css
279 ms
sweetalert2.css
273 ms
2073.css
251 ms
CalloutDisplay.css
362 ms
lodash.min.js
239 ms
2592.css
248 ms
Telerik.Web.UI.WebResource.axd
546 ms
WebResource.axd
271 ms
Json2.js
352 ms
jquery-cookie.js
355 ms
PLMoreDropDown.js
355 ms
Common_Control.js
355 ms
attrchange.js
269 ms
ScriptResource.axd
349 ms
ScriptResource.axd
350 ms
Core.js
263 ms
IETouchActionManager.js
244 ms
jQuery.js
245 ms
jQueryPlugins.js
244 ms
Draggable.js
263 ms
Resizable.js
262 ms
MaterialRippleScripts.js
271 ms
AnimationFramework.js
271 ms
AnimationScripts.js
271 ms
PopupScripts.js
346 ms
TouchScrollExtender.js
346 ms
ShortCutManagerScripts.js
346 ms
RadWindowScripts.js
349 ms
RadWindowManager.js
350 ms
ScrollingScripts.js
349 ms
OData.js
347 ms
NavigationScripts.js
349 ms
OverlayScript.js
348 ms
RadMenuScripts.js
350 ms
RadMenuItem.js
350 ms
ClassicView.js
349 ms
AdvancedBanner.js
490 ms
Style.css
528 ms
jquery.cycle2.min.js
192 ms
Callout.js
494 ms
feature.js
530 ms
gtm.js
73 ms
form-styling.css
36 ms
js
89 ms
analytics.js
48 ms
js
109 ms
collect
55 ms
collect
102 ms
css
67 ms
css
88 ms
css
91 ms
UserFile.aspx
4493 ms
UserFile.aspx
4988 ms
UserFile.aspx
1101 ms
UserFile.aspx
801 ms
UserFile.aspx
3959 ms
UserFile.aspx
3070 ms
UserFile.aspx
1357 ms
UserFile.aspx
2377 ms
stretch.jpg
17 ms
bg_header.jpg
16 ms
bg_logo.png
15 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
40 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
41 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
82 ms
fontawesome-webfont.woff
12 ms
bg_banner.jpg
28 ms
information.gif
26 ms
3TZvZpeHPSs
220 ms
UserFile.aspx
1765 ms
UserFile.aspx
2235 ms
UserFile.aspx
2834 ms
UserFile.aspx
3375 ms
phoneicon.png
44 ms
bg_nav.png
64 ms
bg_content.png
46 ms
page.php
643 ms
callout1.png
140 ms
callout2.png
140 ms
callout3.png
141 ms
featureboxbg.png
159 ms
TK3gWksYAxQ7jbsKcg8Ene8.ttf
137 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
137 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
155 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
170 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
171 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
172 ms
bg_footer.png
197 ms
embed
594 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
40 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
40 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
40 ms
www-player.css
29 ms
www-embed-player.js
57 ms
base.js
90 ms
nML6sO0rp_owOkRMsF5s0qJry7DmnW_dXxSd8CRnFU8.js
137 ms
embed.js
82 ms
LWbfNRBVLRg.css
50 ms
Qj9Mnt9CZ00.css
182 ms
pwInwopu80R.css
191 ms
0nCCeJ0Sjjw.js
196 ms
6ydLaeSSU1k.js
189 ms
8ZrPme2EwKH.js
194 ms
C27gDiAQKjy.js
193 ms
p55HfXW__mM.js
188 ms
c_GxyLwezH_.js
193 ms
PY7gxcd2Ltd.js
227 ms
s99okdZzd10.js
245 ms
leuT2ffoZQq.js
240 ms
U_vR6oxqRMZ.js
242 ms
vxmGiegapsN.js
240 ms
vz_2ZHsDSGe.js
241 ms
mEfPb9OcYTS.js
242 ms
HzxD9aAXSyD.js
242 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
140 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
139 ms
Create
145 ms
245758580_269847205150495_4376109532122404344_n.jpg
161 ms
228982264_214599294008620_4412254782723239804_n.jpg
160 ms
UXtr_j2Fwe-.png
33 ms
kCwDvxe1QsQ.js
129 ms
pFKa_4KaPU-.js
126 ms
V0bSjdVNvGA.js
6 ms
GenerateIT
18 ms
log_event
24 ms
smithsmile.com accessibility score
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
Links do not have a discernible name
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.
smithsmile.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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
smithsmile.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smithsmile.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 Smithsmile.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.
smithsmile.com
Open Graph data is detected on the main page of Smith Smile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: