4.2 sec in total
69 ms
2.7 sec
1.5 sec
Visit proudsmiles.com now to see the best up-to-date Proud Smiles content and also check out these interesting facts you probably never knew about proudsmiles.com
Visit local dentist Dr. Paulen in Sandy Springs, GA for family and cosmetic dentistry. Offering dental implants, porcelain veneers, Invisalign, and more.
Visit proudsmiles.comWe analyzed Proudsmiles.com page load time and found that the first response time was 69 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
proudsmiles.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value9.4 s
0/100
25%
Value4.5 s
73/100
10%
Value840 ms
34/100
30%
Value0
100/100
15%
Value10.0 s
26/100
10%
69 ms
132 ms
208 ms
20 ms
64 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 33% of them (17 requests) were addressed to the original Proudsmiles.com, 27% (14 requests) were made to B867689.smushcdn.com and 16% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (642 ms) relates to the external source B867689.smushcdn.com.
Page size can be reduced by 341.8 kB (13%)
2.7 MB
2.4 MB
In fact, the total size of Proudsmiles.com main page is 2.7 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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 133.2 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 133.2 kB or 85% of the original size.
Potential reduce by 202.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. Proud Smiles images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 4.3 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. Proudsmiles.com has all CSS files already compressed.
Number of requests can be reduced by 16 (42%)
38
22
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proud 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 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
proudsmiles.com
69 ms
www.proudsmiles.com
132 ms
www.proudsmiles.com
208 ms
style.min.css
20 ms
css
64 ms
style.css
47 ms
style.css
51 ms
ProudSmiles%2FProudSmiles%20-%20Brenda%20Paulen%2Fcode.js
183 ms
zo7GdmJJA8m6yRPM
513 ms
css
62 ms
drscriptpack.min.js
337 ms
scripts-min.js
42 ms
smush-lazy-load.min.js
429 ms
api.js
76 ms
fbevents.js
28 ms
gtm.js
339 ms
ATF-1-2-1300x593.jpg
385 ms
ATF-2-Paulen-1300x509.jpg
395 ms
ATF-3-Paulen-1300x646.jpg
386 ms
key-smile.jpg
397 ms
mod-2-3.jpg
394 ms
mod-2-4.jpg
472 ms
christine-thumb.jpg
474 ms
travis-thumb.jpg
473 ms
ava-thumb.jpg
473 ms
Crystal.png
582 ms
Latricia.png
642 ms
hp-visit-bg.jpg
578 ms
new-smile-banner-min.png
473 ms
hp-mod-7-bg.jpg
381 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf
354 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf
362 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
274 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
286 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
273 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
285 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
287 ms
ionicons.ttf
285 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lIb7Y.ttf
287 ms
fontawesome-webfont.woff
238 ms
recaptcha__en.js
164 ms
logo.png
301 ms
js
130 ms
cp-popup.min.css
63 ms
invisa-scaled.jpg
34 ms
mod-2-1.jpg
167 ms
becky-thumb.jpg
168 ms
daryl-thumb.jpg
179 ms
lum-banner-img.png
380 ms
widget2.94a02b9e.min.js
21 ms
widget2.d3c671b5.min.js
22 ms
proudsmiles.com accessibility score
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 input fields do not have accessible names
ARIA IDs are not unique
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
Links do not have a discernible name
proudsmiles.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
proudsmiles.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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proudsmiles.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Proudsmiles.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.
proudsmiles.com
Open Graph data is detected on the main page of Proud Smiles. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: