2.3 sec in total
142 ms
1.8 sec
325 ms
Click here to check amazing Reallysmile content. Otherwise, check out these important facts you probably never knew about reallysmile.com
David A Smith
Visit reallysmile.comWe analyzed Reallysmile.com page load time and found that the first response time was 142 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
reallysmile.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value2.4 s
91/100
25%
Value2.8 s
96/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
142 ms
8 ms
14 ms
29 ms
32 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 65% of them (42 requests) were addressed to the original Reallysmile.com, 11% (7 requests) were made to Youtube.com and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (723 ms) relates to the external source Youtube.com.
Page size can be reduced by 83.1 kB (6%)
1.5 MB
1.4 MB
In fact, the total size of Reallysmile.com main page is 1.5 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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 49.5 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 49.5 kB or 79% of the original size.
Potential reduce by 13.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. Reallysmile images are well optimized though.
Potential reduce by 12.5 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 7.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. Reallysmile.com has all CSS files already compressed.
Number of requests can be reduced by 37 (64%)
58
21
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reallysmile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.reallysmile.com
142 ms
colorbox.css
8 ms
style.css
14 ms
style.min.css
29 ms
styles.css
32 ms
wp-accessibility-helper.min.css
32 ms
pagenavi-css.css
32 ms
css
49 ms
dashicons.min.css
32 ms
style.css
27 ms
app.css
38 ms
front-page.css
38 ms
jquery.min.js
42 ms
jquery-migrate.min.js
37 ms
jquery.colorbox-min.js
37 ms
jquery-colorbox-wrapper-min.js
38 ms
sharethis.js
44 ms
js
95 ms
flexslider.css
43 ms
public.css
39 ms
index.js
43 ms
index.js
42 ms
wp-accessibility-helper.min.js
42 ms
comment-reply.min.js
44 ms
hoverIntent.min.js
46 ms
superfish.min.js
46 ms
superfish.args.min.js
43 ms
skip-links.min.js
44 ms
responsive-menu.js
82 ms
jquery.flexslider.min.js
89 ms
script.min.js
88 ms
swap.js
91 ms
analytics.js
187 ms
header-logo.png
29 ms
C612RD0KnWA
297 ms
cp_OOuhcfTk
723 ms
UiuEwlE06Fw
666 ms
embed
604 ms
bg2-image.jpg
168 ms
final_with_member.png
169 ms
large-print-2.png
183 ms
1c.jpg
159 ms
2.jpg
158 ms
3.jpg
160 ms
4.jpg
160 ms
5b.jpg
159 ms
6.jpg
159 ms
8.jpg
182 ms
image3.jpg
181 ms
symbol-defs.svg
181 ms
overlay.png
68 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
40 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
45 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
57 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
59 ms
collect
43 ms
www-player.css
16 ms
www-embed-player.js
34 ms
base.js
59 ms
ad_status.js
373 ms
wAFWjcG1j0S59k6y9gmRkscrkcYt8sjUn-04af-yL2Q.js
360 ms
embed.js
273 ms
id
42 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
37 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
37 ms
reallysmile.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.
reallysmile.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
reallysmile.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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reallysmile.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Reallysmile.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.
reallysmile.com
Open Graph data is detected on the main page of Reallysmile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: