3.5 sec in total
40 ms
3 sec
459 ms
Welcome to onesmilebright.ca homepage info - get ready to check One Smile Bright best content right away, or after learning these important things about onesmilebright.ca
Visit onesmilebright.caWe analyzed Onesmilebright.ca page load time and found that the first response time was 40 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
onesmilebright.ca performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value23.3 s
0/100
25%
Value9.2 s
13/100
10%
Value1,730 ms
10/100
30%
Value0.056
98/100
15%
Value18.2 s
3/100
10%
40 ms
117 ms
16 ms
23 ms
26 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 57% of them (50 requests) were addressed to the original Onesmilebright.ca, 28% (24 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Onesmilebright.ca.
Page size can be reduced by 368.9 kB (12%)
3.1 MB
2.7 MB
In fact, the total size of Onesmilebright.ca main page is 3.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. 75% 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 134.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 134.7 kB or 88% of the original size.
Potential reduce by 98.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. One Smile Bright images are well optimized though.
Potential reduce by 131.4 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.4 kB or 31% of the original size.
Potential reduce by 4.8 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. Onesmilebright.ca has all CSS files already compressed.
Number of requests can be reduced by 42 (71%)
59
17
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of One Smile Bright. 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 21 to 1 for CSS and as a result speed up the page load time.
onesmilebright.ca
40 ms
webfont.js
117 ms
styles.css
16 ms
settings.css
23 ms
wpcf7-redirect-frontend.min.css
26 ms
bootstrap.min.css
51 ms
font-awesome.min.css
45 ms
stm-icomoon.css
47 ms
jquery-ui.min.css
47 ms
jquery-ui.datepicker.min.css
49 ms
jquery-ui.slider.min.css
56 ms
jquery-ui-timepicker-addon.min.css
58 ms
jquery.fancybox.css
56 ms
select2.css
59 ms
style.css
63 ms
skin_4.css
57 ms
js_composer.min.css
76 ms
jquery.min.js
277 ms
jquery-migrate.min.js
299 ms
jquery.themepunch.tools.min.js
327 ms
jquery.themepunch.revolution.min.js
324 ms
sharethis.js
115 ms
css
115 ms
css
207 ms
css
216 ms
css
217 ms
css
218 ms
index.js
337 ms
index.js
338 ms
wpcf7r-fe.js
368 ms
bootstrap.min.js
368 ms
core.min.js
320 ms
datepicker.min.js
371 ms
mouse.min.js
368 ms
slider.min.js
369 ms
jquery-ui-timepicker-addon.min.js
337 ms
jquery.fancybox.pack.js
370 ms
select2.min.js
435 ms
custom.js
367 ms
js_composer_front.min.js
435 ms
js
200 ms
css
108 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
51 ms
font
52 ms
KFOmCnqEu92Fr1Mu4mxM.woff
51 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
52 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
52 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
53 ms
KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff
53 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
53 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
54 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff
55 ms
KFOjCnqEu92Fr1Mu51TzBic6CsI.woff
54 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff
56 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff
55 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff
55 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff
56 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXtHA_w.woff
57 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXtHA_w.woff
60 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXtHA_w.woff
83 ms
fbevents.js
49 ms
analytics.js
90 ms
OSB-bigger-font.png
74 ms
front-reception-upright.jpg
407 ms
OSM-Logo-1.png
73 ms
IMG_1441.jpg
1381 ms
blue-seal-81-171-onesmilebright-97110.png
139 ms
Sourireblanc-1.png
249 ms
Massage-Chairs.jpg
1980 ms
front-of-building11-1.jpg
396 ms
dentist-1-1024x577.jpg
247 ms
icomoon.ttf
177 ms
fontawesome-webfont.woff
176 ms
collect
114 ms
Screen-Shot-2016-11-16-at-10.06.18-PM.png
410 ms
js
157 ms
font
148 ms
SlGVmQWMvZQIdix7AFxXkHNSaw.woff
65 ms
SlGWmQWMvZQIdix7AFxXmMh3eDs1YQ.woff
65 ms
revolution.extension.slideanims.min.js
120 ms
revolution.extension.actions.min.js
124 ms
revolution.extension.layeranimation.min.js
125 ms
revolution.extension.navigation.min.js
126 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uz.woff
23 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
24 ms
revicons.woff
137 ms
onesmilebright.ca 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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
onesmilebright.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
onesmilebright.ca 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 Onesmilebright.ca 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 Onesmilebright.ca 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.
onesmilebright.ca
Open Graph description is not detected on the main page of One Smile Bright. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: