1.8 sec in total
27 ms
1.3 sec
428 ms
Click here to check amazing AFCA content. Otherwise, check out these important facts you probably never knew about afca.ca
Alberta Fire Chiefs Association (AFCA) provides essential fire fighting training materials for professionals. Visit our online book store or join our membership today.
Visit afca.caWe analyzed Afca.ca page load time and found that the first response time was 27 ms and then it took 1.8 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.
afca.ca performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value9.2 s
1/100
25%
Value14.9 s
1/100
10%
Value1,420 ms
15/100
30%
Value1.219
1/100
15%
Value17.2 s
4/100
10%
27 ms
180 ms
63 ms
53 ms
37 ms
Our browser made a total of 181 requests to load all elements on the main page. We found that 90% of them (162 requests) were addressed to the original Afca.ca, 10% (18 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (313 ms) belongs to the original domain Afca.ca.
Page size can be reduced by 396.2 kB (11%)
3.5 MB
3.1 MB
In fact, the total size of Afca.ca main page is 3.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. Only a small number of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 374.9 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 374.9 kB or 83% of the original size.
Potential reduce by 811 B
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. AFCA images are well optimized though.
Potential reduce by 13.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. This website has mostly compressed JavaScripts.
Potential reduce by 6.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. Afca.ca has all CSS files already compressed.
Number of requests can be reduced by 143 (92%)
156
13
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AFCA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 99 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
afca.ca
27 ms
afca.ca
180 ms
formidableforms1.css
63 ms
upe_blocks.css
53 ms
dashicons.min.css
37 ms
style.min.css
32 ms
sweetalert2.min.css
48 ms
lightgallery-bundle.min.css
59 ms
admin.css
78 ms
buttons.min.css
50 ms
editor.min.css
75 ms
xoo-aff-style.css
87 ms
all.min.css
92 ms
variables-skeleton.min.css
103 ms
variables-full.min.css
107 ms
common-skeleton.min.css
104 ms
common-full.min.css
125 ms
tickets.min.css
136 ms
rsvp-v1.min.css
142 ms
unslider.css
167 ms
slider.css
140 ms
bbpress.min.css
142 ms
bbp-image-upload.css
161 ms
base.css
187 ms
variation_1.css
181 ms
pmpro-advanced-levels.css
212 ms
pmpro-member-directory.css
177 ms
xoo-el-style.css
202 ms
xoo-el-fonts.css
198 ms
front.min.css
215 ms
la-index.css
216 ms
login-index.css
221 ms
ti-index.css
233 ms
fi-index.css
238 ms
flist-index.css
251 ms
topic-views-index.css
248 ms
statistics-index.css
250 ms
js
72 ms
search-index.css
276 ms
bspstyle-1.css
279 ms
style.min.css
248 ms
style.min.css
248 ms
style.min.css
249 ms
rsvp.min.css
285 ms
style.css
257 ms
wc-blocks.css
261 ms
mediaelementplayer-legacy.min.css
226 ms
wp-mediaelement.min.css
228 ms
jquery.min.js
233 ms
jquery-migrate.min.js
218 ms
block-widget.js
263 ms
moxie.min.js
231 ms
plupload.min.js
213 ms
utils.min.js
204 ms
xoo-aff-js.js
238 ms
unslider.min.js
237 ms
jquery.event.move.js
236 ms
jquery.event.swipe.js
231 ms
e2pdf.frontend.js
217 ms
bbp-image-upload.js
206 ms
ie-compat.min.js
232 ms
bsp_enqueue_submit.js
220 ms
advanced.min.js
223 ms
react.min.js
192 ms
react-dom.min.js
190 ms
react-jsx-runtime.min.js
186 ms
dom-ready.min.js
189 ms
hooks.min.js
194 ms
i18n.min.js
181 ms
a11y.min.js
179 ms
deprecated.min.js
167 ms
dom.min.js
220 ms
escape-html.min.js
221 ms
element.min.js
193 ms
is-shallow-equal.min.js
188 ms
keycodes.min.js
179 ms
priority-queue.min.js
176 ms
compose.min.js
177 ms
moment.min.js
169 ms
date.min.js
171 ms
html-entities.min.js
171 ms
primitives.min.js
161 ms
private-apis.min.js
155 ms
redux-routine.min.js
147 ms
data.min.js
148 ms
rich-text.min.js
147 ms
warning.min.js
146 ms
components.min.js
192 ms
underscore-before.js
183 ms
underscore.min.js
108 ms
underscore-after.js
170 ms
wp-util.min.js
106 ms
backbone.min.js
167 ms
wp-backbone.min.js
144 ms
media-models.min.js
161 ms
wp-plupload.min.js
154 ms
lightgallery.js
150 ms
sweetalert2.min.js
172 ms
react-select.js
188 ms
drag-select.js
199 ms
admin.js
185 ms
editor.min.js
177 ms
quicktags.min.js
145 ms
hoverIntent.min.js
156 ms
common.min.js
186 ms
wplink.min.js
172 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
88 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
96 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
101 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
110 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
109 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
110 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
109 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
102 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
109 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
110 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
111 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
112 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
112 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
113 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
112 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
128 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
128 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
128 ms
core.min.js
138 ms
menu.min.js
120 ms
autocomplete.min.js
120 ms
thickbox.js
127 ms
shortcode.min.js
127 ms
media-upload.min.js
150 ms
divi.js
207 ms
xoo-el-js.js
161 ms
rsvp.min.js
173 ms
ticket-details.min.js
178 ms
layer.js
174 ms
sticky.js
182 ms
front.min.js
194 ms
advanced-ads-pro.min.js
209 ms
scripts.min.js
193 ms
jquery.fitvids.js
185 ms
easypiechart.js
191 ms
salvattore.js
195 ms
frontend-bundle.min.js
286 ms
frontend-bundle.min.js
202 ms
slick.js
203 ms
et-divi-dynamic-tb-113494-22-late.css
154 ms
plyr.min.js
187 ms
frontend.js
264 ms
frontend-bundle.min.js
264 ms
frontend-bundle.min.js
265 ms
sourcebuster.min.js
263 ms
order-attribution.min.js
251 ms
tracking.min.js
240 ms
ga-tracking.min.js
225 ms
delayed.min.js
222 ms
common.js
221 ms
main.js
224 ms
dwe-mini-cart.min.js
224 ms
mediaelement-and-player.min.js
222 ms
mediaelement-migrate.min.js
214 ms
wp-mediaelement.min.js
214 ms
sticky-elements.js
214 ms
tinymce.min.js
215 ms
plugin.min.js
213 ms
modules.woff
313 ms
Easy-Login.ttf
292 ms
cropped-AFCA-Logo.png
280 ms
FFProfileIcon.png
189 ms
HotShopCart.png
267 ms
firefighter-300x200.jpeg
266 ms
gear-300x200.jpeg
258 ms
AFCA-Ad-Sample-3.jpg
300 ms
tsi-01.jpg
296 ms
5-Stripes.jpg
244 ms
roadside-safety.jpg
132 ms
woocommerce-placeholder.png
132 ms
fa-solid-900.woff
104 ms
fa-brands-400.woff
154 ms
fa-regular-400.woff
78 ms
main.js
28 ms
loadingAnimation.gif
44 ms
afca.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
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.
afca.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
Missing source maps for large first-party JavaScript
afca.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 Afca.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 Afca.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.
afca.ca
Open Graph description is not detected on the main page of AFCA. 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: