2.2 sec in total
104 ms
1.8 sec
257 ms
Click here to check amazing Bodylife content. Otherwise, check out these important facts you probably never knew about bodylife.ca
Bodylife Massage Therapy by Andrée Guénette Registered Massage Therapist. Easy Online Scheduling! Put Your body in good hands!
Visit bodylife.caWe analyzed Bodylife.ca page load time and found that the first response time was 104 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
bodylife.ca performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value7.0 s
6/100
25%
Value7.8 s
23/100
10%
Value1,420 ms
15/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
104 ms
210 ms
99 ms
60 ms
65 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Bodylife.ca, 43% (51 requests) were made to Bodylifeatlantic.ca and 20% (24 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (779 ms) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 464.0 kB (26%)
1.8 MB
1.3 MB
In fact, the total size of Bodylife.ca main page is 1.8 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 38.8 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 38.8 kB or 82% of the original size.
Potential reduce by 38.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. Bodylife images are well optimized though.
Potential reduce by 384.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 384.8 kB or 65% of the original size.
Potential reduce by 1.9 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. Bodylife.ca needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 83% of the original size.
Number of requests can be reduced by 57 (50%)
114
57
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bodylife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
bodylife.ca
104 ms
www.bodylifeatlantic.ca
210 ms
jquery.js
99 ms
jquery.wpslider.js
60 ms
jspngfix.js
65 ms
wpstyles.css
83 ms
widgets.js
144 ms
js
39 ms
jsWPGoogleMaps.js
52 ms
wpb63ccbac_1a.png
51 ms
wp1fc6bd82_1a.png
50 ms
wp95c05fd3_1a.png
54 ms
wpcf5a71f8_1a.png
55 ms
wpc7a0b5e0_1a.png
51 ms
wp6572d72e_1a.png
118 ms
wp714e0b93_1a.png
57 ms
wp69059183_1a.png
116 ms
wp2fcbcfee_1a.png
206 ms
wp8c3464da_1a.png
121 ms
wp042a1911_1a.png
125 ms
wp048cd459_1a.png
212 ms
wpa40be31f_05_1a.jpg
118 ms
wpfdfbc4bd_05_1a.jpg
207 ms
wp09cb569f_1a.png
122 ms
wp7141b694_1a.png
403 ms
wpacab6a1d_05_1a.jpg
205 ms
wpf96be83f_1a.png
351 ms
wp531737fb_05_1a.jpg
205 ms
wp53f67521_1a.png
205 ms
wp492effc9_1a.png
210 ms
wpb83304dc_1a.png
212 ms
wpde4fb778_1a.png
208 ms
wp583b2d15_1a.png
211 ms
wp0f04fe02_1a.png
250 ms
wpe43257ee_1a.png
249 ms
wpd14249b2_1a.png
246 ms
wpc535cc73_1a.png
246 ms
wp2225085e_1a.png
338 ms
wpc1d05948_1a.png
337 ms
wp7e6a7f64_1a.png
338 ms
wpc1a1ec69_1a.png
337 ms
wp63b49611_1a.png
352 ms
wp38af0e85_1a.png
353 ms
wp5b4d83e3_1a.png
354 ms
wpb7579cc6_05_1a.jpg
381 ms
counter.js
9 ms
wp751bc565_05_1a.jpg
353 ms
wp8e339f57_1a.png
353 ms
wpd70a76ed_1a.png
352 ms
wp0c334c14_1a.png
353 ms
wp826c2efc_1a.png
368 ms
t.php
158 ms
common.js
23 ms
map.js
23 ms
util.js
22 ms
marker.js
24 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
243 ms
t.php
155 ms
wpeca09567_1a.png
310 ms
StaticMapService.GetMapImage
97 ms
wpa64b082a_1a.png
304 ms
like.php
243 ms
wpb7166fe9_1a.png
300 ms
wp5f883f2d_1a.png
303 ms
onion.js
47 ms
openhand_8_8.cur
37 ms
likebox.php
308 ms
ViewportInfoService.GetViewportInfo
47 ms
stats.js
40 ms
controls.js
41 ms
infowindow.js
32 ms
spotlight-poi.png
50 ms
css
78 ms
transparent.png
57 ms
google4.png
57 ms
mapcnt6.png
59 ms
sv5.png
60 ms
vt
74 ms
vt
67 ms
qeKvIRsJabD.js
77 ms
LVx-xkvaJ0b.png
67 ms
vt
47 ms
tmapctrl.png
31 ms
cb_scout5.png
39 ms
tmapctrl4.png
30 ms
imgs8.png
49 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
23 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
23 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
33 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
54 ms
AuthenticationService.Authenticate
63 ms
hDvwL1_H7g-.css
13 ms
56WNbrUYLbL.css
10 ms
yZ--Yu0PDbV.css
30 ms
QD6_ejUFoCN.css
25 ms
xxJgcoj8mOR.css
19 ms
6AlVa5wn0Ie.css
18 ms
q68gy-v_YMF.js
33 ms
FJmpeSpHpjS.js
49 ms
0wM5s1Khldu.js
59 ms
1bNoFZUdlYZ.js
61 ms
njO1TPvGzoR.js
58 ms
1QuX41zDRrx.js
63 ms
Oagsvfb4VWi.js
64 ms
LTv6ZK-5zxz.js
68 ms
1FCa-btixu2.js
68 ms
541135_457532440993413_276454421_n.png
103 ms
safe_image.php
779 ms
558876_558002237613099_329544665_n.jpg
32 ms
10382859_369452266576232_8957843433895018547_n.jpg
31 ms
11149458_369452183242907_2933542868053797837_n.jpg
32 ms
wL6VQj7Ab77.png
29 ms
s7jcwEQH7Sx.png
28 ms
QDwYpIaRyfG.png
28 ms
MiXXTBbOQzg.png
29 ms
K00K-UgnsKu.png
29 ms
jot
98 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
7 ms
bodylife.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
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
bodylife.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
bodylife.ca 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 Bodylife.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 Bodylife.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.
bodylife.ca
Open Graph description is not detected on the main page of Bodylife. 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: