Tools & Wizards About Us
fansforthecure.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fansforthecure.org

Prostate Cancer Awareness and Education | Fans for the Cure

Page Load Speed

4 sec in total

First Response

81 ms

Resources Loaded

3.6 sec

Page Rendered

329 ms

fansforthecure.org screenshot

About Website

Visit fansforthecure.org now to see the best up-to-date Fans For The Cure content and also check out these interesting facts you probably never knew about fansforthecure.org

Fans for the Cure works to increase the number of men who get tested for prostate cancer and to reduce the number of men diagnosed with later-stage cancer. 

Visit fansforthecure.org

Key Findings

We analyzed Fansforthecure.org page load time and found that the first response time was 81 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

fansforthecure.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.446

20/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

fansforthecure.org

81 ms

fansforthecure.org

2676 ms

leaflet.min.css

95 ms

style.css

35 ms

style.min.css

38 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 93% of them (75 requests) were addressed to the original Fansforthecure.org, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Fansforthecure.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.7 kB (13%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fansforthecure.org 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. 70% of websites need less resources to load. Images take 788.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 73.0 kB

  • Original 94.4 kB
  • After minification 94.4 kB
  • After compression 21.4 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 73.0 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 79.6 kB

  • Original 788.7 kB
  • After minification 709.1 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. Fans For The Cure images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 352 B

  • Original 229.9 kB
  • After minification 229.9 kB
  • After compression 229.5 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.

CSS Optimization

-11%

Potential reduce by 25.8 kB

  • Original 227.8 kB
  • After minification 212.6 kB
  • After compression 202.1 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. Fansforthecure.org needs all CSS files to be minified and compressed as it can save up to 25.8 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (75%)

Requests Now

77

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fans For The Cure. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fansforthecure.org

fansforthecure.org

81 ms

fansforthecure.org

fansforthecure.org

2676 ms

leaflet.min.css

leaflet.min.css

95 ms

style.css

style.css

35 ms

style.min.css

style.min.css

38 ms

all.min.css

all.min.css

147 ms

bootstrap.min.css

bootstrap.min.css

141 ms

front.css

front.css

136 ms

lbdesign_button_shortcode.css

lbdesign_button_shortcode.css

43 ms

widget-options.css

widget-options.css

43 ms

frontend.min.css

frontend.min.css

59 ms

flatpickr.min.css

flatpickr.min.css

54 ms

select2.min.css

select2.min.css

88 ms

dashicons.min.css

dashicons.min.css

71 ms

css

css

40 ms

elementor-icons.min.css

elementor-icons.min.css

85 ms

frontend.min.css

frontend.min.css

97 ms

swiper.min.css

swiper.min.css

106 ms

post-1859.css

post-1859.css

108 ms

frontend.min.css

frontend.min.css

109 ms

global.css

global.css

127 ms

post-1879.css

post-1879.css

192 ms

post-1876.css

post-1876.css

129 ms

post-1858.css

post-1858.css

197 ms

style.css

style.css

140 ms

style.css

style.css

214 ms

civicrm.css

civicrm.css

148 ms

tad-civicrm.css

tad-civicrm.css

155 ms

css

css

47 ms

jquery.min.js

jquery.min.js

256 ms

jquery-migrate.min.js

jquery-migrate.min.js

229 ms

popper.min.js

popper.min.js

154 ms

bootstrap.min.js

bootstrap.min.js

165 ms

front.js

front.js

173 ms

flatpickr.min.js

flatpickr.min.js

182 ms

select2.min.js

select2.min.js

192 ms

responsive-menu.js

responsive-menu.js

297 ms

js

js

64 ms

email-decode.min.js

email-decode.min.js

194 ms

soliloquy.css

soliloquy.css

208 ms

animations.min.css

animations.min.css

202 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

202 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

197 ms

wp-polyfill.min.js

wp-polyfill.min.js

394 ms

hooks.min.js

hooks.min.js

282 ms

i18n.min.js

i18n.min.js

188 ms

jquery.form.min.js

jquery.form.min.js

182 ms

frontend.min.js

frontend.min.js

363 ms

soliloquy-min.js

soliloquy-min.js

346 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

347 ms

webpack.runtime.min.js

webpack.runtime.min.js

343 ms

frontend-modules.min.js

frontend-modules.min.js

285 ms

frontend.min.js

frontend.min.js

282 ms

waypoints.min.js

waypoints.min.js

329 ms

core.min.js

core.min.js

306 ms

frontend.min.js

frontend.min.js

306 ms

elements-handlers.min.js

elements-handlers.min.js

380 ms

6884168

6884168

141 ms

fans-for-the-cure-logo_392x98.gif

fans-for-the-cure-logo_392x98.gif

165 ms

fftc-grandfather-father-son.jpg

fftc-grandfather-father-son.jpg

290 ms

holder.gif

holder.gif

194 ms

online-mens-support-group-testimonial-03.png

online-mens-support-group-testimonial-03.png

221 ms

stay-in-the-game-howard-wolinsky.webp

stay-in-the-game-howard-wolinsky.webp

248 ms

fans-for-the-cure-womens-support-group-800x500-1.jpg

fans-for-the-cure-womens-support-group-800x500-1.jpg

298 ms

bayer-logo-512x512-1.png

bayer-logo-512x512-1.png

288 ms

fans-for-the-cure-logo_392x41.gif

fans-for-the-cure-logo_392x41.gif

271 ms

stay-in-the-game-podcast-logo-square.png

stay-in-the-game-podcast-logo-square.png

368 ms

symbol-defs.svg

symbol-defs.svg

258 ms

fans-for-the-cure-giving-tuesday.jpg

fans-for-the-cure-giving-tuesday.jpg

395 ms

va9B4kDNxMZdWfMOD5VnZKveRhf8.woff

va9B4kDNxMZdWfMOD5VnZKveRhf8.woff

59 ms

va9B4kDNxMZdWfMOD5VnLK3eRhf8.woff

va9B4kDNxMZdWfMOD5VnLK3eRhf8.woff

67 ms

preloader.gif

preloader.gif

223 ms

fftc-grandfather-grandson-fishing.jpg

fftc-grandfather-grandson-fishing.jpg

202 ms

fftc-family-playing-baseball.jpg

fftc-family-playing-baseball.jpg

184 ms

fftc-family-01.jpg

fftc-family-01.jpg

195 ms

fftc-thanksgiving-01.jpg

fftc-thanksgiving-01.jpg

272 ms

left.png

left.png

175 ms

right.png

right.png

247 ms

pause.png

pause.png

190 ms

circle.png

circle.png

274 ms

circle-hover.png

circle-hover.png

149 ms

Accessibility Review

fansforthecure.org accessibility score

90

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

fansforthecure.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fansforthecure.org SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fansforthecure.org 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 Fansforthecure.org 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.

Social Sharing Optimization

fansforthecure.org

Open Graph data is detected on the main page of Fans For The Cure. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: