2.1 sec in total
447 ms
1.2 sec
513 ms
Click here to check amazing Familyforce content for Canada. Otherwise, check out these important facts you probably never knew about familyforce.ca
Canadian Forces Morale and Welfare Services (CFMWS) operates under a social enterprise business model, with the fundamental belief that we exist to create positive value for our members.
Visit familyforce.caWe analyzed Familyforce.ca page load time and found that the first response time was 447 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
familyforce.ca performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value11.4 s
0/100
25%
Value7.6 s
25/100
10%
Value2,070 ms
7/100
30%
Value0.263
47/100
15%
Value10.7 s
22/100
10%
447 ms
63 ms
138 ms
42 ms
279 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Familyforce.ca, 15% (8 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (447 ms) relates to the external source Cfmws.ca.
Page size can be reduced by 406.5 kB (20%)
2.0 MB
1.6 MB
In fact, the total size of Familyforce.ca main page is 2.0 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.2 MB which makes up the majority of the site volume.
Potential reduce by 189.3 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. This page needs HTML code to be minified as it can gain 109.5 kB, which is 53% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 189.3 kB or 91% of the original size.
Potential reduce by 50.7 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. Familyforce images are well optimized though.
Potential reduce by 135.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 135.8 kB or 26% of the original size.
Potential reduce by 30.7 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. Familyforce.ca needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 35% of the original size.
Number of requests can be reduced by 18 (42%)
43
25
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Familyforce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
cfmws.ca
447 ms
js
63 ms
gtm.js
138 ms
cfmws_styles.css
42 ms
systemPageComponents.min.css
279 ms
slideshow-widget.css
141 ms
swiper-bundle.css
37 ms
logo_header_en.svg
116 ms
logo_header_fr.svg
225 ms
1582x844-Boat-Training.jpg
280 ms
icon_tabs_services.svg
67 ms
icon_tabs_discounts.svg
110 ms
icon_tabs_tools.svg
112 ms
icon_tabs_get-help.svg
117 ms
email-decode.min.js
113 ms
runtime.bundle.js
255 ms
vendors.bundle.js
256 ms
main.bundle.js
255 ms
MutationObserver.js
250 ms
Logger.js
278 ms
jquery-3.5.1.js
338 ms
jquery.unobtrusive-ajax.js
350 ms
slideshow-widget.js
374 ms
swiper-bundle.js
349 ms
systemFormComponents.min.js
335 ms
vef91dfe02fce4ee0ad053f6de4f175db1715022073587
112 ms
MFS-youth.jpg
373 ms
css2
97 ms
icon_hamburger_X.svg
248 ms
icon_footer_linkedin.png
253 ms
icon_footer_insta.png
251 ms
icon_map_location.svg
251 ms
icon_search_black.svg
249 ms
icon_location_black.svg
248 ms
icon_location.svg
307 ms
icon_search_open.svg
309 ms
icon_search_x.svg
357 ms
icon_lets-talk.svg
359 ms
icon_lets-talk-open.svg
356 ms
icon_check-circle.svg
360 ms
icon_subnav-button-arrow-white.svg
311 ms
icon_social.svg
309 ms
icon_filter_close.svg
309 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
129 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
226 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
281 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
282 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
280 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
280 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
280 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
280 ms
fbevents.js
180 ms
familyforce.ca 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-*] attributes do not match their roles
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
familyforce.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
familyforce.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Familyforce.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 Familyforce.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.
familyforce.ca
Open Graph description is not detected on the main page of Familyforce. 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: