5.1 sec in total
221 ms
4.8 sec
140 ms
Click here to check amazing Fire Museum Canada content. Otherwise, check out these important facts you probably never knew about firemuseumcanada.com
SEE THE TRUCKS The introduction of motorized apparatus had a profound impact on the fire service. Read More... SUPPORT THE MUSEUM The CFFM is a volunteer-run organization and could use your help. Don...
Visit firemuseumcanada.comWe analyzed Firemuseumcanada.com page load time and found that the first response time was 221 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
firemuseumcanada.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value13.6 s
0/100
25%
Value14.2 s
1/100
10%
Value770 ms
38/100
30%
Value0.184
66/100
15%
Value14.4 s
9/100
10%
221 ms
1483 ms
174 ms
261 ms
270 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 65% of them (58 requests) were addressed to the original Firemuseumcanada.com, 27% (24 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Firemuseumcanada.com.
Page size can be reduced by 87.3 kB (7%)
1.3 MB
1.2 MB
In fact, the total size of Firemuseumcanada.com main page is 1.3 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. 65% of websites need less resources to load. Images take 516.8 kB which makes up the majority of the site volume.
Potential reduce by 58.0 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 58.0 kB or 77% of the original size.
Potential reduce by 11.6 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. Fire Museum Canada images are well optimized though.
Potential reduce by 7.3 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 10.4 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. Firemuseumcanada.com has all CSS files already compressed.
Number of requests can be reduced by 51 (85%)
60
9
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fire Museum Canada. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
firemuseumcanada.com
221 ms
www.firemuseumcanada.com
1483 ms
style.min.css
174 ms
jquery.selectBox.css
261 ms
font-awesome.css
270 ms
prettyPhoto.css
269 ms
style.css
276 ms
extendify-utilities.css
271 ms
styles.css
267 ms
plugin.css
347 ms
woocommerce-layout.css
354 ms
woocommerce.css
359 ms
style.css
356 ms
dashicons.min.css
444 ms
lib.css
539 ms
css
34 ms
style.css
532 ms
fusion-shortcodes.min.css
442 ms
js_composer.min.css
643 ms
jquery.min.js
538 ms
jquery-migrate.min.js
530 ms
js
51 ms
plugin.js
538 ms
rbtools.min.js
803 ms
rs6.min.js
849 ms
jquery.blockUI.min.js
619 ms
add-to-cart.min.js
620 ms
js.cookie.min.js
625 ms
woocommerce.min.js
706 ms
woocommerce-add-to-cart.js
707 ms
lib.js
820 ms
functions.js
730 ms
counter.js
35 ms
css
13 ms
animate.min.css
722 ms
rs6.css
771 ms
jquery.selectBox.min.js
813 ms
jquery.prettyPhoto.min.js
814 ms
jquery.yith-wcwl.min.js
849 ms
index.js
850 ms
api.js
66 ms
index.js
849 ms
sourcebuster.min.js
759 ms
order-attribution.min.js
715 ms
wp-polyfill-inert.min.js
716 ms
regenerator-runtime.min.js
717 ms
wp-polyfill.min.js
736 ms
index.js
727 ms
smush-lazy-load.min.js
745 ms
hoverIntent.min.js
720 ms
maxmegamenu.js
730 ms
js_composer_front.min.js
728 ms
skrollr.min.js
736 ms
vc-waypoints.min.js
660 ms
lazyload.min.js
657 ms
dummy.png
304 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVQ.woff
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
153 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
152 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
151 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
152 ms
ionicons.ttf
470 ms
font
153 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
153 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
171 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
168 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
169 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
169 ms
wARDj0u
16 ms
font
152 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
165 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
173 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
172 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
173 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
185 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
185 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
203 ms
fontawesome-webfont.woff
358 ms
fontawesome-webfont.woff
375 ms
t.php
114 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
163 ms
KFOmCnqEu92Fr1Mu4mxM.woff
163 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
163 ms
SqLogoLrg.gif
152 ms
museum_logo_image2.jpg
615 ms
Oma_logo_hires_white-color-e1494452901182.png
89 ms
woocommerce-smallscreen.css
88 ms
firemuseumcanada.com 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
firemuseumcanada.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
firemuseumcanada.com 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 Firemuseumcanada.com 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 Firemuseumcanada.com 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.
firemuseumcanada.com
Open Graph data is detected on the main page of Fire Museum Canada. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: