Tools & Wizards About Us
srfcure.org screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

srfcure.org

Scleroderma Research Foundation | SRF | Research for a Cure

Page Load Speed

3.4 sec in total

First Response

105 ms

Resources Loaded

2.1 sec

Page Rendered

1.2 sec

srfcure.org screenshot

About Website

Visit srfcure.org now to see the best up-to-date SRF Cure content for United States and also check out these interesting facts you probably never knew about srfcure.org

Guided by passion for a cure, the Scleroderma Research Foundation has become the largest nonprofit investor in scleroderma research in the U.S.

Visit srfcure.org

Key Findings

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

Performance Metrics

srfcure.org performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value2,030 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.251

49/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

srfcure.org

105 ms

srfcure.org

108 ms

font-awesome.min.css

57 ms

js

126 ms

all.min.css

28 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 86% of them (112 requests) were addressed to the original Srfcure.org, 2% (3 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (606 ms) relates to the external source Listgrowth.ctctcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.2 kB (9%)

Content Size

3.0 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Srfcure.org main page is 3.0 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 204.7 kB

  • Original 241.8 kB
  • After minification 233.7 kB
  • After compression 37.1 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 204.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.9 MB
  • After minification 1.9 MB

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. SRF Cure images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 51.5 kB

  • Original 752.3 kB
  • After minification 752.3 kB
  • After compression 700.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.

CSS Optimization

-12%

Potential reduce by 21.9 kB

  • Original 184.5 kB
  • After minification 182.5 kB
  • After compression 162.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. Srfcure.org needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 87 (73%)

Requests Now

119

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SRF 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 56 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

srfcure.org

srfcure.org

105 ms

srfcure.org

srfcure.org

108 ms

font-awesome.min.css

font-awesome.min.css

57 ms

js

js

126 ms

all.min.css

all.min.css

28 ms

v4-shims.min.css

v4-shims.min.css

29 ms

cnss.css

cnss.css

30 ms

magnific-popup.css

magnific-popup.css

43 ms

jquery.sf-flash.min.css

jquery.sf-flash.min.css

44 ms

classy-style.css

classy-style.css

41 ms

kin0snt.css

kin0snt.css

107 ms

nectar-slider.css

nectar-slider.css

44 ms

give.css

give.css

42 ms

give-authorize.css

give-authorize.css

42 ms

give-ffm-frontend.min.css

give-ffm-frontend.min.css

71 ms

give-ffm-datepicker.min.css

give-ffm-datepicker.min.css

71 ms

give-tributes-public.min.css

give-tributes-public.min.css

73 ms

give-recurring.css

give-recurring.css

72 ms

font-awesome.min.css

font-awesome.min.css

74 ms

grid-system.css

grid-system.css

82 ms

style.css

style.css

90 ms

header-secondary-nav.css

header-secondary-nav.css

80 ms

css

css

73 ms

responsive.css

responsive.css

83 ms

ascend.css

ascend.css

86 ms

menu-dynamic.css

menu-dynamic.css

85 ms

js_composer.min.css

js_composer.min.css

108 ms

pum-site.min.css

pum-site.min.css

105 ms

css

css

88 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

112 ms

style.css

style.css

105 ms

css

css

103 ms

jquery.min.js

jquery.min.js

107 ms

jquery-migrate.min.js

jquery-migrate.min.js

104 ms

core.min.js

core.min.js

122 ms

mouse.min.js

mouse.min.js

118 ms

cnss.js

cnss.js

119 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

118 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

119 ms

wp-polyfill.min.js

wp-polyfill.min.js

121 ms

dom-ready.min.js

dom-ready.min.js

120 ms

hooks.min.js

hooks.min.js

143 ms

i18n.min.js

i18n.min.js

146 ms

signup-form-widget.min.js

signup-form-widget.min.js

84 ms

jquery.fancybox.css

jquery.fancybox.css

142 ms

core.css

core.css

125 ms

a11y.min.js

a11y.min.js

125 ms

datepicker.min.js

datepicker.min.js

125 ms

slider.min.js

slider.min.js

111 ms

clipboard.min.js

clipboard.min.js

137 ms

moxie.min.js

moxie.min.js

139 ms

plupload.min.js

plupload.min.js

137 ms

underscore.min.js

underscore.min.js

138 ms

handlers.min.js

handlers.min.js

147 ms

give-ffm-frontend.min.js

give-ffm-frontend.min.js

108 ms

give-tributes-common.min.js

give-tributes-common.min.js

122 ms

frontend-gtag.min.js

frontend-gtag.min.js

122 ms

babel-polyfill.js

babel-polyfill.js

122 ms

give.js

give.js

142 ms

give-tributes-public.min.js

give-tributes-public.min.js

135 ms

give-recurring.js

give-recurring.js

108 ms

sortable.min.js

sortable.min.js

200 ms

menu.min.js

menu.min.js

197 ms

autocomplete.min.js

autocomplete.min.js

333 ms

wpss-search-suggest.js

wpss-search-suggest.js

318 ms

p.css

p.css

46 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

316 ms

jquery.sf-flash.min.js

jquery.sf-flash.min.js

316 ms

classy-scripts.js

classy-scripts.js

316 ms

anime.js

anime.js

313 ms

nectar-slider.js

nectar-slider.js

308 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

310 ms

jquery.easing.js

jquery.easing.js

305 ms

jquery.mousewheel.js

jquery.mousewheel.js

304 ms

priority.js

priority.js

306 ms

transit.js

transit.js

305 ms

waypoints.js

waypoints.js

305 ms

imagesLoaded.min.js

imagesLoaded.min.js

306 ms

hoverintent.js

hoverintent.js

284 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

285 ms

superfish.js

superfish.js

282 ms

init.js

init.js

285 ms

touchswipe.min.js

touchswipe.min.js

282 ms

site.min.js

site.min.js

282 ms

js_composer_front.min.js

js_composer_front.min.js

282 ms

gtm.js

gtm.js

203 ms

gximage2

gximage2

238 ms

SRF_WebsiteLogo_Positive_2x.png

SRF_WebsiteLogo_Positive_2x.png

152 ms

Blue-Bg-w-Microphones-1.png

Blue-Bg-w-Microphones-1.png

182 ms

2024-CCHC-logo_white.png

2024-CCHC-logo_white.png

178 ms

MYA-Web-Slider-1.png

MYA-Web-Slider-1.png

183 ms

conquer-hero-image.jpg

conquer-hero-image.jpg

153 ms

Website-Slider-BG-1.jpg

Website-Slider-BG-1.jpg

151 ms

preferred-purple-blue-gradient.png

preferred-purple-blue-gradient.png

181 ms

ss-layered-1.svg

ss-layered-1.svg

177 ms

mission-carousel3-1440x796-1.jpg

mission-carousel3-1440x796-1.jpg

180 ms

participate-in-research-carousel-1440x796-copy.jpg

participate-in-research-carousel-1440x796-copy.jpg

185 ms

registry-icon.svg

registry-icon.svg

184 ms

bod-icon.svg

bod-icon.svg

185 ms

Cure-Crew-Icon-1.svg

Cure-Crew-Icon-1.svg

185 ms

halftone-treatment-image.png

halftone-treatment-image.png

237 ms

about-scleroderma.png

about-scleroderma.png

236 ms

participate-in-research-image.png

participate-in-research-image.png

102 ms

join-cure-crew-image.png

join-cure-crew-image.png

101 ms

halftone-treatment-image-1.png

halftone-treatment-image-1.png

101 ms

srf-icon-only-rev-1.png

srf-icon-only-rev-1.png

100 ms

our-reserach-image.png

our-reserach-image.png

143 ms

scientific-workshop.png

scientific-workshop.png

142 ms

current-funded-3.png

current-funded-3.png

142 ms

cchc-image.jpg

cchc-image.jpg

140 ms

Orange-Dot-Gradient.png

Orange-Dot-Gradient.png

139 ms

four-star.svg

four-star.svg

143 ms

rddc-med.png

rddc-med.png

140 ms

Segma-Regular.woff

Segma-Regular.woff

284 ms

Segma-Medium.woff

Segma-Medium.woff

282 ms

Segma-Bold.woff

Segma-Bold.woff

282 ms

Segma-Black.woff

Segma-Black.woff

282 ms

Segma-RegularItalic.woff

Segma-RegularItalic.woff

361 ms

icomoon.woff

icomoon.woff

280 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

281 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

30 ms

analytics.js

analytics.js

86 ms

js

js

86 ms

api.js

api.js

237 ms

collect

collect

224 ms

fa-brands-400.woff

fa-brands-400.woff

103 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

68 ms

recaptcha__en.js

recaptcha__en.js

63 ms

signup-form-widget.css

signup-form-widget.css

533 ms

f69d53747cb14e12e6adac2e9e32f8fd.json

f69d53747cb14e12e6adac2e9e32f8fd.json

606 ms

Accessibility Review

srfcure.org accessibility score

75

Accessibility Issues

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

srfcure.org best practices score

83

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

srfcure.org SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Srfcure.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 Srfcure.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

srfcure.org

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