1.1 sec in total
49 ms
728 ms
309 ms
Welcome to childhoodobesityfoundation.ca homepage info - get ready to check Childhoodobesityfoundation best content right away, or after learning these important things about childhoodobesityfoundation.ca
Visit childhoodobesityfoundation.caWe analyzed Childhoodobesityfoundation.ca page load time and found that the first response time was 49 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
childhoodobesityfoundation.ca performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value16.4 s
0/100
25%
Value4.2 s
77/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value12.7 s
14/100
10%
49 ms
113 ms
61 ms
23 ms
35 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Childhoodobesityfoundation.ca, 69% (68 requests) were made to Childhoodhealthyliving.ca and 15% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (241 ms) relates to the external source App.cyberimpact.com.
Page size can be reduced by 173.1 kB (8%)
2.2 MB
2.0 MB
In fact, the total size of Childhoodobesityfoundation.ca main page is 2.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. 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.0 MB which makes up the majority of the site volume.
Potential reduce by 76.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 76.5 kB or 81% of the original size.
Potential reduce by 96.3 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. Childhoodobesityfoundation images are well optimized though.
Potential reduce by 286 B
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 42 B
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. Childhoodobesityfoundation.ca has all CSS files already compressed.
Number of requests can be reduced by 61 (79%)
77
16
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Childhoodobesityfoundation. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
childhoodobesityfoundation.ca
49 ms
childhoodhealthyliving.ca
113 ms
js
61 ms
style.min.css
23 ms
css
35 ms
header-footer-elementor.css
43 ms
elementor-icons.min.css
73 ms
frontend-lite.min.css
76 ms
swiper.min.css
54 ms
post-50.css
56 ms
frontend.min.css
83 ms
frontend-lite.min.css
73 ms
post-327.css
74 ms
frontend.css
79 ms
all.min.css
92 ms
v4-shims.min.css
94 ms
text-editor.css
95 ms
style.min.css
96 ms
theme.min.css
97 ms
post-98.css
98 ms
post-201.css
99 ms
ekiticons.css
105 ms
style.css
109 ms
widget-styles.css
130 ms
responsive.css
120 ms
fontawesome.min.css
127 ms
solid.min.css
121 ms
regular.min.css
126 ms
brands.min.css
128 ms
frontend-gtag.min.js
151 ms
v4-shims.min.js
151 ms
jquery.min.js
166 ms
jquery-migrate.min.js
153 ms
widget-icon-list.min.css
152 ms
animations.min.css
153 ms
hello-frontend.min.js
156 ms
frontend-script.js
157 ms
widget-scripts.js
197 ms
frontend.js
206 ms
webpack-pro.runtime.min.js
207 ms
webpack.runtime.min.js
190 ms
frontend-modules.min.js
172 ms
hooks.min.js
161 ms
i18n.min.js
159 ms
frontend.min.js
143 ms
waypoints.min.js
143 ms
core.min.js
143 ms
frontend.min.js
141 ms
elements-handlers.min.js
139 ms
animate-circle.min.js
126 ms
elementor.js
129 ms
jquery.sticky.min.js
128 ms
frontend.min.js
129 ms
tooltipster.min.js
134 ms
5AB04489-FDDB-4855-95AB-768128AA3806
241 ms
CHLF-final-logo-SVG-1.svg
35 ms
group-of-older-kids-running.jpg
135 ms
Picture1.jpg
129 ms
Picture2.jpg
129 ms
Picture3.jpg
127 ms
Picture4.jpg
128 ms
bg-2.png
128 ms
teens-playing-1024x683.jpg
176 ms
cta-overlay.png
133 ms
Picture5.jpg
133 ms
232464_gettyimages1216641336_738082.jpg
133 ms
footer-bg.png
133 ms
DonateButton.png
174 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
21 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
37 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
45 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
73 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
47 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
72 ms
elementskit.woff
76 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf
46 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf
46 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf
71 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rm.ttf
73 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf
72 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf
73 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf
75 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rm.ttf
74 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rm.ttf
73 ms
fa-solid-900.woff
44 ms
fa-regular-400.woff
42 ms
fa-brands-400.woff
43 ms
jquery-ui.min.css
17 ms
css
18 ms
jquery-3.7.1.min.js
35 ms
jquery-ui.min.js
90 ms
0f99039444c45f20def6c96367d333de.js
55 ms
prevent_console.js
46 ms
datepicker-en-CA.js
55 ms
cyberimpact.js
46 ms
common.26e44f97ce1262ce70ebf3916b087234.js
62 ms
public.046cb4de89b8cd6f7af75b844d3f30c9.js
73 ms
dialogs.1410f3bd9f32b6bffe46a4588c1df251.js
122 ms
childhoodobesityfoundation.ca 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.
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
childhoodobesityfoundation.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
childhoodobesityfoundation.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Childhoodobesityfoundation.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 Childhoodobesityfoundation.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.
childhoodobesityfoundation.ca
Open Graph description is not detected on the main page of Childhoodobesityfoundation. 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: