2 sec in total
142 ms
1.5 sec
297 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 142 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.2 s
42/100
10%
Value15.5 s
0/100
25%
Value9.4 s
12/100
10%
Value1,530 ms
13/100
30%
Value0.012
100/100
15%
Value16.4 s
5/100
10%
142 ms
52 ms
62 ms
66 ms
60 ms
Our browser made a total of 193 requests to load all elements on the main page. We found that 90% of them (174 requests) were addressed to the original Afca.ca, 9% (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 (338 ms) belongs to the original domain Afca.ca.
Page size can be reduced by 324.7 kB (15%)
2.1 MB
1.8 MB
In fact, the total size of Afca.ca main page is 2.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. 85% 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 303.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 303.9 kB or 81% of the original size.
Potential reduce by 152 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 14.6 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 5.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. Afca.ca has all CSS files already compressed.
Number of requests can be reduced by 163 (95%)
171
8
The browser has sent 171 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 117 to 1 for JavaScripts and from 48 to 1 for CSS and as a result speed up the page load time.
afca.ca
142 ms
formidableforms1.css
52 ms
dashicons.min.css
62 ms
style.min.css
66 ms
sweetalert2.min.css
60 ms
lightgallery-bundle.css
63 ms
admin.css
79 ms
buttons.min.css
88 ms
editor.min.css
94 ms
variables-skeleton.min.css
89 ms
variables-full.min.css
89 ms
rsvp-v1.min.css
89 ms
common-skeleton.min.css
135 ms
common-full.min.css
125 ms
tickets.min.css
123 ms
unslider.css
121 ms
slider.css
126 ms
bbpress.min.css
126 ms
bbp-image-upload.css
154 ms
frontend.css
155 ms
pmpro-advanced-levels.css
153 ms
pmpro-member-directory.css
156 ms
xoo-el-style.css
164 ms
xoo-el-fonts.css
169 ms
xoo-aff-style.css
183 ms
all.min.css
187 ms
select2.css
190 ms
front.min.css
191 ms
la-index.css
195 ms
login-index.css
201 ms
ti-index.css
250 ms
fi-index.css
222 ms
flist-index.css
221 ms
topic-views-index.css
219 ms
statistics-index.css
229 ms
search-index.css
234 ms
js
61 ms
bspstyle-1.css
240 ms
style.min.css
216 ms
style.min.css
208 ms
style.min.css
215 ms
rsvp.min.css
224 ms
tpp.min.css
212 ms
style.css
220 ms
wc-blocks.css
222 ms
mediaelementplayer-legacy.min.css
231 ms
wp-mediaelement.min.css
233 ms
moxie.min.js
244 ms
plupload.min.js
225 ms
utils.min.js
222 ms
ie-compat.min.js
224 ms
jquery.min.js
338 ms
jquery-migrate.min.js
336 ms
block-widget.js
331 ms
wp-polyfill-inert.min.js
312 ms
regenerator-runtime.min.js
312 ms
wp-polyfill.min.js
311 ms
react.min.js
310 ms
react-dom.min.js
304 ms
dom-ready.min.js
300 ms
hooks.min.js
283 ms
i18n.min.js
280 ms
a11y.min.js
277 ms
deprecated.min.js
278 ms
dom.min.js
276 ms
escape-html.min.js
268 ms
element.min.js
250 ms
is-shallow-equal.min.js
251 ms
keycodes.min.js
251 ms
priority-queue.min.js
242 ms
compose.min.js
292 ms
moment.min.js
279 ms
date.min.js
271 ms
html-entities.min.js
258 ms
primitives.min.js
258 ms
private-apis.min.js
251 ms
redux-routine.min.js
244 ms
data.min.js
260 ms
rich-text.min.js
227 ms
warning.min.js
228 ms
components.min.js
241 ms
underscore-before.js
216 ms
underscore.min.js
239 ms
underscore-after.js
212 ms
wp-util.min.js
214 ms
backbone.min.js
217 ms
wp-backbone.min.js
116 ms
media-models.min.js
125 ms
wp-plupload.min.js
152 ms
lg-zoom.min.js
149 ms
lg-thumbnail.min.js
149 ms
lg-fullscreen.min.js
149 ms
lg-autoplay.min.js
149 ms
lg-video.min.js
150 ms
lg-comment.min.js
155 ms
lightgallery.min.js
168 ms
sweetalert2.min.js
167 ms
react-select.js
176 ms
react-tooltip.js
169 ms
admin.js
186 ms
editor.min.js
184 ms
quicktags.min.js
198 ms
wplink.min.js
204 ms
core.min.js
201 ms
menu.min.js
205 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
48 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
53 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
63 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
54 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
61 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
63 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
65 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
65 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
67 ms
autocomplete.min.js
165 ms
thickbox.js
172 ms
shortcode.min.js
174 ms
media-upload.min.js
179 ms
divi.js
182 ms
ticket-details.min.js
187 ms
rsvp.min.js
192 ms
unslider.min.js
198 ms
jquery.event.move.js
207 ms
jquery.event.swipe.js
208 ms
et-divi-dynamic-22-late.css
204 ms
sourcebuster.min.js
226 ms
order-attribution.min.js
226 ms
lodash.min.js
224 ms
wc-blocks-registry.js
225 ms
url.min.js
337 ms
api-fetch.min.js
302 ms
wc-settings.js
288 ms
data-controls.min.js
277 ms
notices.min.js
253 ms
wc-blocks-middleware.js
253 ms
wc-blocks-data.js
253 ms
blocks-components.js
252 ms
blocks-checkout.js
253 ms
order-attribution-blocks.min.js
252 ms
e2pdf.frontend.js
248 ms
bbp-image-upload.js
236 ms
select2.full.min.js
233 ms
xoo-aff-js.js
234 ms
smooth-scrollbar.js
231 ms
xoo-el-js.js
223 ms
base.min.js
237 ms
layer.js
237 ms
sticky.js
235 ms
front.min.js
268 ms
bsp_enqueue_submit.js
252 ms
advanced.min.js
238 ms
advanced-ads-pro.min.js
226 ms
scripts.min.js
241 ms
jquery.fitvids.js
234 ms
easypiechart.js
261 ms
salvattore.js
256 ms
frontend-bundle.min.js
251 ms
frontend-bundle.min.js
271 ms
slick.js
260 ms
plyr.min.js
263 ms
frontend.js
227 ms
frontend-bundle.min.js
226 ms
frontend-bundle.min.js
226 ms
tracking.min.js
236 ms
ga-tracking.min.js
148 ms
delayed.min.js
159 ms
common.js
164 ms
main.js
165 ms
mediaelement-and-player.min.js
183 ms
mediaelement-migrate.min.js
173 ms
wp-mediaelement.min.js
192 ms
dwe-mini-cart.min.js
194 ms
modules.woff
248 ms
Easy-Login.ttf
248 ms
cropped-AFCA-Logo.png
246 ms
5-Stripes.jpg
247 ms
firefighter-300x200.jpeg
248 ms
gear-300x200.jpeg
248 ms
Railway-Association-150x150.jpg
243 ms
loadingAnimation.gif
37 ms
main.js
21 ms
print.css
36 ms
style.min.css
45 ms
modules.woff
45 ms
afca.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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: