1.3 sec in total
61 ms
1.1 sec
177 ms
Visit fighting-back.ca now to see the best up-to-date Fighting Back content and also check out these interesting facts you probably never knew about fighting-back.ca
Organize your own challenge to raise funds for cancer research.
Visit fighting-back.caWe analyzed Fighting-back.ca page load time and found that the first response time was 61 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
fighting-back.ca performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value17.0 s
0/100
25%
Value11.6 s
4/100
10%
Value2,250 ms
6/100
30%
Value0.165
71/100
15%
Value20.6 s
2/100
10%
61 ms
213 ms
113 ms
90 ms
176 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fighting-back.ca, 65% (26 requests) were made to Donordrivecontent.com and 15% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (521 ms) relates to the external source Donordrivecontent.com.
Page size can be reduced by 110.3 kB (27%)
411.2 kB
301.0 kB
In fact, the total size of Fighting-back.ca main page is 411.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 182.5 kB which makes up the majority of the site volume.
Potential reduce by 93.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 93.0 kB or 77% of the original size.
Potential reduce by 0 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. Fighting Back images are well optimized though.
Potential reduce by 1.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 15.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. Fighting-back.ca needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 16% of the original size.
Number of requests can be reduced by 25 (81%)
31
6
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fighting Back. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fighting-back.ca
61 ms
index.cfm
213 ms
gtm.js
113 ms
gtm.js
90 ms
dd-public.css
176 ms
master.css
199 ms
design-system.css
230 ms
jquery.min.js
29 ms
jquery-migrate-3.4.0.min.js
211 ms
dd.min.js
205 ms
donordrive.widget.js
212 ms
donordrive.api.js
210 ms
js
77 ms
donordrive.tabs.js
297 ms
dd-forms.css
221 ms
jquery.validate.min.js
521 ms
moment-with-locales.js
300 ms
numeral.min.js
316 ms
donordrive.form.js
479 ms
dd-streaming.css
294 ms
dd-scroll-to-class-update.js
444 ms
sticky-items.js
296 ms
theme.js
374 ms
livechatinc.js
304 ms
slick.1.9.min.js
381 ms
modal.js
402 ms
embed-donate.js
25 ms
css2
52 ms
logoImage.png
103 ms
bannerImage.png
101 ms
constituent_9D66E02F-BAAC-1B65-C42B63552D032448.jpg
199 ms
logo-white.svg
96 ms
S6uyw4BMUTPHvxo.woff
68 ms
S6u9w4BMUTPHh6UVeww.woff
80 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
98 ms
pxiEyp8kv8JHgFVrFJM.woff
106 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
107 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
105 ms
fontawesome-webfont.woff
65 ms
print.css
35 ms
fighting-back.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.
fighting-back.ca 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
fighting-back.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Fighting-back.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 Fighting-back.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.
fighting-back.ca
Open Graph data is detected on the main page of Fighting Back. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: