Bleeding.org Site Title

National Bleeding Disorders Foundation, formerly NHF | NBDF

Bleeding.org Meta Description

NBDF is committed to curing blood & bleeding disorders, preventing complications, and empowering individuals & families through research, education & advocacy.

Bleeding.org Test Results

Bleeding.org Mobile Performance: 36/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,930 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Minimize main-thread work
8.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce unused CSS
Potential savings of 66 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Defer offscreen images
Potential savings of 180 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Eliminate render-blocking resources
Potential savings of 2,390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce JavaScript execution time
4.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid an excessive DOM size
1,622 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Properly size images
Potential savings of 477 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
7,090 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 573 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 401 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 10 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Serve static assets with an efficient cache policy
3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid enormous network payloads
Total size was 2,852 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Time to Interactive
17.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
390 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
4.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Bleeding.org Mobile SEO: 85/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Links do not have descriptive text
22 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Bleeding.org Mobile Best Practices: 79/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Bleeding.org Mobile Accessibility: 87/100
Quick overview:
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Similar tests
www.bleeding.com
www.bleeding.net
www.bleeding.org
www.bleeding.info
www.bleeding.biz
www.bleeding.us
www.bleeding.mobi
www.leeding.org
www.bleeding.org
www.vleeding.org
www.bvleeding.org
www.vbleeding.org
www.gleeding.org
www.bgleeding.org
www.gbleeding.org
www.hleeding.org
www.bhleeding.org
www.hbleeding.org
www.nleeding.org
www.bnleeding.org
www.nbleeding.org
www.beeding.org
www.bpeeding.org
www.blpeeding.org
www.bpleeding.org
www.boeeding.org
www.bloeeding.org
www.boleeding.org
www.bkeeding.org
www.blkeeding.org
www.bkleeding.org
www.bleding.org
www.blweding.org
www.bleweding.org
www.blweeding.org
www.blseding.org
www.bleseding.org
www.blseeding.org
www.bldeding.org
www.blededing.org
www.bldeeding.org
www.blreding.org
www.blereding.org
www.blreeding.org
www.blewding.org
www.bleewding.org
www.blesding.org
www.bleesding.org
www.bledding.org
www.bleedding.org
www.blerding.org
www.bleerding.org
www.bleeing.org
www.bleexing.org
www.bleedxing.org
www.bleexding.org
www.bleesing.org
www.bleedsing.org
www.bleeeing.org
www.bleedeing.org
www.bleeeding.org
www.bleering.org
www.bleedring.org
www.bleefing.org
www.bleedfing.org
www.bleefding.org
www.bleecing.org
www.bleedcing.org
www.bleecding.org
www.bleedng.org
www.bleedung.org
www.bleediung.org
www.bleeduing.org
www.bleedjng.org
www.bleedijng.org
www.bleedjing.org
www.bleedkng.org
www.bleedikng.org
www.bleedking.org
www.bleedong.org
www.bleediong.org
www.bleedoing.org
www.bleedig.org
www.bleedibg.org
www.bleedinbg.org
www.bleedibng.org
www.bleedihg.org
www.bleedinhg.org
www.bleedihng.org
www.bleedijg.org
www.bleedinjg.org
www.bleedimg.org
www.bleedinmg.org
www.bleedimng.org
www.bleedin.org
www.bleedinf.org
www.bleedingf.org
www.bleedinfg.org
www.bleedinv.org
www.bleedingv.org
www.bleedinvg.org
www.bleedint.org
www.bleedingt.org
www.bleedintg.org
www.bleedinb.org
www.bleedingb.org
www.bleediny.org
www.bleedingy.org
www.bleedinyg.org
www.bleedinh.org
www.bleedingh.org
Last Tested: