Tools & Wizards About Us
jdrf.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

jdrf.com

JDRF - Diabetes - Type 1 Diabetes Research, Advocacy, and Support

Page Load Speed

2.6 sec in total

First Response

17 ms

Resources Loaded

552 ms

Page Rendered

2 sec

jdrf.com screenshot

About Website

Click here to check amazing JDRF content for United States. Otherwise, check out these important facts you probably never knew about jdrf.com

JDRF leads the global Type 1 Diabetes support and research effort to keep people healthy and safe until we find a cure for the disease. Help create a world without T1D.

Visit jdrf.com

Key Findings

We analyzed Jdrf.com page load time and found that the first response time was 17 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

jdrf.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,760 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.606

10/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

jdrf.com

17 ms

www.breakthrought1d.org

144 ms

style.min.css

35 ms

shared.css

39 ms

frontend.css

50 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jdrf.com, 89% (64 requests) were made to Breakthrought1d.org and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (208 ms) relates to the external source Breakthrought1d.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.5 kB (3%)

Content Size

4.2 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jdrf.com main page is 4.2 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 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 133.4 kB

  • Original 168.0 kB
  • After minification 166.2 kB
  • After compression 34.6 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 133.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.8 MB
  • After minification 3.8 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. JDRF images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 795 B

  • Original 120.5 kB
  • After minification 120.5 kB
  • After compression 119.7 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

-0%

Potential reduce by 296 B

  • Original 77.9 kB
  • After minification 77.9 kB
  • After compression 77.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. Jdrf.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 45 (64%)

Requests Now

70

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jdrf.com

jdrf.com

17 ms

www.breakthrought1d.org

www.breakthrought1d.org

144 ms

style.min.css

style.min.css

35 ms

shared.css

shared.css

39 ms

frontend.css

frontend.css

50 ms

styles.css

styles.css

46 ms

bne-testimonials.min.css

bne-testimonials.min.css

43 ms

frontend.css

frontend.css

41 ms

styles.min.css

styles.min.css

51 ms

style.min.css

style.min.css

54 ms

frontend.css

frontend.css

75 ms

formreset.min.css

formreset.min.css

63 ms

formsmain.min.css

formsmain.min.css

64 ms

readyclass.min.css

readyclass.min.css

60 ms

browsers.min.css

browsers.min.css

70 ms

select2.min.css

select2.min.css

57 ms

gravityforms-autocomplete-public.css

gravityforms-autocomplete-public.css

72 ms

language-cookie.js

language-cookie.js

83 ms

jquery.min.js

jquery.min.js

84 ms

jquery-migrate.min.js

jquery-migrate.min.js

83 ms

riveted.min.js

riveted.min.js

84 ms

jquery.json.min.js

jquery.json.min.js

102 ms

gravityforms.min.js

gravityforms.min.js

104 ms

select2.min.js

select2.min.js

70 ms

sprintf.js

sprintf.js

103 ms

init.js

init.js

135 ms

utils.min.js

utils.min.js

105 ms

yett.min.js

yett.min.js

67 ms

js-cookie.min.js

js-cookie.min.js

103 ms

jdrf_cookie.min.js

jdrf_cookie.min.js

106 ms

jdrf_ajax_handler.min.js

jdrf_ajax_handler.min.js

103 ms

jquery.scrolldepth.min.js

jquery.scrolldepth.min.js

106 ms

jdrf_google_events.min.js

jdrf_google_events.min.js

118 ms

12272081689.js

12272081689.js

204 ms

frontend.js

frontend.js

118 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

120 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

196 ms

frontend.js

frontend.js

195 ms

date-picker.js

date-picker.js

164 ms

hooks.min.js

hooks.min.js

164 ms

i18n.min.js

i18n.min.js

155 ms

a11y.min.js

a11y.min.js

158 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

154 ms

vendor-theme.min.js

vendor-theme.min.js

158 ms

scripts-theme.min.js

scripts-theme.min.js

156 ms

analytics.min.js

analytics.min.js

184 ms

gtm.js

gtm.js

198 ms

breakthrough-logo.svg

breakthrough-logo.svg

139 ms

chevron-down.svg

chevron-down.svg

138 ms

Learnabout-T1D_NAV-1356431169-1-scaled.jpg

Learnabout-T1D_NAV-1356431169-1-scaled.jpg

141 ms

Life-with-T1D_NAV-scaled.jpg

Life-with-T1D_NAV-scaled.jpg

143 ms

Get-Involved_NAV-scaled.jpg

Get-Involved_NAV-scaled.jpg

147 ms

Accerlerating_NAV542573680-scaled.jpg

Accerlerating_NAV542573680-scaled.jpg

143 ms

LearnAboutBreakthroughs_NAV-1383393717-scaled.jpg

LearnAboutBreakthroughs_NAV-1383393717-scaled.jpg

148 ms

HomeHero-scaled.jpg

HomeHero-scaled.jpg

149 ms

Card-Carousel-1-DiabeticCare-1369899306-1024x683.jpg

Card-Carousel-1-DiabeticCare-1369899306-1024x683.jpg

152 ms

arrow-long-right.svg

arrow-long-right.svg

150 ms

2-Boys-Pool-1024x768.jpeg

2-Boys-Pool-1024x768.jpeg

151 ms

Card-Carousel-3-LivingT1D-1388223922-1024x634.jpg

Card-Carousel-3-LivingT1D-1388223922-1024x634.jpg

154 ms

Card-Carousel-4-LivingT1D-1014817786-1024x684.jpg

Card-Carousel-4-LivingT1D-1014817786-1024x684.jpg

154 ms

ScientistsDr-497411370-1024x683.jpg

ScientistsDr-497411370-1024x683.jpg

155 ms

About-BTT1D969671504-1024x683.jpg

About-BTT1D969671504-1024x683.jpg

201 ms

Primary-Page-Links-Get-Involved-Community-1011936690-1024x683.jpg

Primary-Page-Links-Get-Involved-Community-1011936690-1024x683.jpg

201 ms

group-gradient.svg

group-gradient.svg

198 ms

RES-FY24-ADA-Conference-Blog_1200x800.jpg

RES-FY24-ADA-Conference-Blog_1200x800.jpg

203 ms

ADA-2024-Day-2-1200x800-1.png

ADA-2024-Day-2-1200x800-1.png

202 ms

ScientistsDr-1321467331R80-scaled.jpg

ScientistsDr-1321467331R80-scaled.jpg

203 ms

us.country.svg

us.country.svg

208 ms

es.svg

es.svg

206 ms

a597080980.html

a597080980.html

141 ms

Accessibility Review

jdrf.com 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

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

Links do not have a discernible name

Best Practices

jdrf.com best practices score

75

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

jdrf.com SEO score

93

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

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

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

Social Sharing Optimization

jdrf.com

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