3.5 sec in total
161 ms
3.1 sec
232 ms
Click here to check amazing Blood 4 Life content for United States. Otherwise, check out these important facts you probably never knew about blood4life.org
Medical Web Portal
Visit blood4life.orgWe analyzed Blood4life.org page load time and found that the first response time was 161 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.
blood4life.org performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value16.2 s
0/100
25%
Value13.6 s
2/100
10%
Value2,560 ms
4/100
30%
Value0.006
100/100
15%
Value24.6 s
0/100
10%
161 ms
263 ms
187 ms
199 ms
200 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blood4life.org, 88% (64 requests) were made to Donors.vitalant.org and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Donors.vitalant.org.
Page size can be reduced by 384.1 kB (12%)
3.2 MB
2.8 MB
In fact, the total size of Blood4life.org main page is 3.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. 65% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 116.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 116.6 kB or 84% of the original size.
Potential reduce by 59.2 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. Blood 4 Life images are well optimized though.
Potential reduce by 208.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 208.3 kB or 38% of the original size.
Number of requests can be reduced by 54 (79%)
68
14
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blood 4 Life. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
blood4life.org
161 ms
dwa
263 ms
mobiscroll.custom-3.2.6.min-cb53663f783369293252e49ec433a8e5.css
187 ms
jquery-ui-93bd0deaf07b2253873b726e124a8364.css
199 ms
jquery-ui-timepicker-addon-2965edf466d523a160509e7e37c4146e.css
200 ms
foundationD-a3708130b4dfdc96cf99ac39e5dfd01b.css
248 ms
foundation-icons-68844d2c98e2e1b3004cedf00f2e51a1.css
201 ms
normalize-757d1bf1b20c47678a6d4fb4b028df47.css
200 ms
bootstrap-e672fdd8f02642d79155a1d6b849a78d.css
254 ms
responsiveTable-5ae229d7c42f7415b88b8468bcea3d8f.css
257 ms
font-awesome-0676c4527c173c8e6694d19dcda4141c.css
254 ms
default-0717b1c75df18e86a1cc6d26f21f1a73.css
257 ms
default.date-7afbbd0191f9c928e82da8671a86463a.css
258 ms
default.time-14dda2db6434390aba332bb1f09f88c7.css
314 ms
fixed-tab-bar-c5126042e454733e64a5156baeedd7ab.css
312 ms
jquery.mCustomScrollbar-295351a5027c5ad6256f3389ab471cfb.css
318 ms
application-c92691156c03571f658896d24668e6db.css
381 ms
head-foot-a30ab29469a95810f2873bc148097ec4.css
321 ms
style-b595b5affb108d9d99867c1c99cf2da9.css
324 ms
stacktable-3296fd2dc2175a23abcc9ede33514e3b.css
375 ms
chosen-b2b0a42732ac51e4bcf7160b2ab6c385.css
385 ms
custom.modernizr-3ebb4643783188b17078b8615f089db7.js
390 ms
jquery-35e7c13439a82ff00912649dae42b1bb.js
512 ms
jquery-ui-c960283b0802675eed8fea69a9d938af.js
522 ms
jquery-ui-sliderAccess-59e6ffd2c80db262ebf3d4c8114ea498.js
440 ms
jquery-ui-timepicker-addon-f85ced23fe6b7a9b9caa97bc08ec495d.js
447 ms
jquery.validate-a97da859a817b8ad70ce73215181990e.js
442 ms
foundation-18e9d395fb1db2cd0e9d7454cf55f904.js
444 ms
foundation.magellan-ba772459112e787bbd1047efcf2d02e4.js
508 ms
foundation.offcanvas-6a9c9239a00799a943bac2984f3c12b7.js
505 ms
foundation.orbit-323f7a543bba700d34aebd1135bf8aa0.js
507 ms
foundation.reveal-564b27334fda340431256f152daac296.js
536 ms
foundation.topbar-16c3e20d216a7b87283ac8f675541f13.js
571 ms
foundation.tab-3ff64360b9bf6c95ef795a6d50eff47d.js
576 ms
foundation.accordion-405f109a51c7498ddddc5caf38b0d3af.js
578 ms
portal-206583eeb8367a423ae1b123782ddbe5.js
581 ms
dwa-b15f06c78fb76dbbd6ab2ad9ed9d03b6.js
580 ms
d64b4ad0-49ee-0138-f594-06a9ed4ca31b
29 ms
font-awesome-eb824e1044b8bc906186fb340eb0b231.css
531 ms
bootstrap.min-ddf62d2a6b8d502890dca20f3eb20b81.js
446 ms
TreeMenu-92395f214590be7a3c854d30247ed69a.js
455 ms
jquery.stayInWebApp-3e959c77e1f76a15dff92c202136034d.js
456 ms
jquery.mask-f6a723ddf1c1ecb33f0b7ae1f0812bce.js
457 ms
gstatic.charts.loader.min-73c94d431a125bf190b60a0ff9c00625.js
460 ms
picker-3c51f3f8204b51f2cc95d6da9f89825b.js
413 ms
picker.date-b27885a780819ff7bc833b498cf30efd.js
454 ms
picker.time-bd1a2bda8d60565b3e7b9f6bf99c2d5c.js
464 ms
legacy-f73fc362c3bdc306a65392c11221159d.js
463 ms
bowser-5effea215fcd265ef1e8f191d150f971.js
464 ms
jquery.mCustomScrollbar-50c803e1483b1bbb1531fea61f849d98.js
475 ms
mobiscroll.custom-3.2.6.min-ac54ead44922a7d308bbd831de231078.js
426 ms
moment.min-36e68df9e516c74c2083f3d1d31e0aa4.js
464 ms
stacktable-29196e0f00ea8be8969ec0a60570f590.js
464 ms
chosen.jquery-65b5e638afe3a98f2cc514ca3bb311ea.js
462 ms
jquery.mousewheel.min.js
47 ms
fbevents.js
394 ms
gtm.js
458 ms
vitalant-r-logo-1471568cd80f8490b3e4ed60afdca362.png
392 ms
ajax-loader-dot-8749ea7f724a393ac08f2e488038ca64.gif
392 ms
ajax-loader-dot-84598410f69b5017be14fc5b6cc88f5a.gif
392 ms
vitalant-r-footer-top-044da85bb6ac7d9eaaa366af6db6addb.png
392 ms
vitalant-contact-us-e24f4dbdff983e9f215396dc55cc285c.png
392 ms
warning-effcaf389eb1ede013d642fc9e9623a8.png
391 ms
analytics.js
420 ms
transform-a-life-image-block-3353d9e93293647d18321d18a572f428.jpg
1237 ms
ui-bg_flat_75_ffffff_40x100-2c2d8b9867ff13e18190b5947c27b704.png
506 ms
ui-bg_highlight-soft_75_cccccc_1x100-4a73870fc0e5e44a481fc44e2ff8d544.png
487 ms
36C852_1_0-f336bf485180db946f59635b907ee489.woff
496 ms
36C852_6_0-6bf110028ee00d3d28a2cbac47d8949a.woff
506 ms
foundation-icons-a188c2f768ce5033d3f5d47be7280e25.woff
492 ms
collect
30 ms
collect
26 ms
ga-audiences
126 ms
blood4life.org accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
blood4life.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
blood4life.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blood4life.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 Blood4life.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.
blood4life.org
Open Graph description is not detected on the main page of Blood 4 Life. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: