10.3 sec in total
658 ms
9.4 sec
277 ms
Click here to check amazing Bloodinfo content for South Korea. Otherwise, check out these important facts you probably never knew about bloodinfo.net
Visit bloodinfo.netWe analyzed Bloodinfo.net page load time and found that the first response time was 658 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
bloodinfo.net performance score
name
value
score
weighting
Value12.0 s
0/100
10%
Value17.2 s
0/100
25%
Value21.2 s
0/100
10%
Value1,180 ms
21/100
30%
Value0.324
36/100
15%
Value15.9 s
6/100
10%
658 ms
1427 ms
22 ms
1624 ms
1062 ms
Our browser made a total of 170 requests to load all elements on the main page. We found that 66% of them (112 requests) were addressed to the original Bloodinfo.net, 16% (28 requests) were made to Static.xx.fbcdn.net and 9% (15 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Bloodinfo.net.
Page size can be reduced by 656.2 kB (18%)
3.7 MB
3.1 MB
In fact, the total size of Bloodinfo.net main page is 3.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 73.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. This page needs HTML code to be minified as it can gain 22.1 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 73.4 kB or 85% of the original size.
Potential reduce by 106.8 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. Bloodinfo images are well optimized though.
Potential reduce by 355.9 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 355.9 kB or 74% of the original size.
Potential reduce by 120.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. Bloodinfo.net needs all CSS files to be minified and compressed as it can save up to 120.1 kB or 90% of the original size.
Number of requests can be reduced by 50 (30%)
165
115
The browser has sent 165 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bloodinfo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
bloodinfo.net
658 ms
main.do
1427 ms
nanumgothic.css
22 ms
new_common_for_fnb.css
1624 ms
new_main.css
1062 ms
jquery.bxslider.css
785 ms
jquery-1.7.min.js
1747 ms
jquery-ui-1.10.3.min.js
2139 ms
jquery.jscrollpane.min.js
1377 ms
jcarousellite_1.0.1.js
1249 ms
jquery.touchSwipe.min.js
1269 ms
jquery.bxslider.js
1670 ms
new_common_for_fnb.js
1900 ms
new_main.js
1777 ms
footer.js
787 ms
NanumGothic-Regular.woff
105 ms
NanumGothic-Bold.woff
129 ms
NanumGothic-ExtraBold.woff
210 ms
all.js
39 ms
webfont.js
39 ms
fnb_background.png
219 ms
fnb_donation.png
212 ms
fnb_voluntary.png
210 ms
fnb_education.png
210 ms
fnb_rcy.png
209 ms
fnb_hospital.png
209 ms
top_right_gnb_00.png
398 ms
top_right_gnb_01.png
414 ms
top_right_gnb_02.png
410 ms
top_right_gnb_03.png
416 ms
top_right_gnb_04.png
408 ms
top_right_gnb_05.png
411 ms
top_right_gnb_06.png
602 ms
btn_zoom_in.png
610 ms
btn_zoom_out.png
606 ms
btn_zoom_default.png
607 ms
ci.png
611 ms
div_board.png
612 ms
gnb_login.png
809 ms
gnb_join.png
803 ms
gnb_favorite.png
804 ms
gnb_sitemap.png
805 ms
gnb_english.png
806 ms
new_mainmenu_about_blood_donation.png
810 ms
new_mainmenu_donating_blood.png
1000 ms
new_mainmenu_get_involved.png
1003 ms
new_mainmenu_community.png
1005 ms
new_mainmenu_news_event.png
1001 ms
new_mainmenu_pr_contents.png
1007 ms
new_mainmenu_introduce.png
1009 ms
bg_main_visual.png
1200 ms
main_image9.png
1598 ms
main_image7.png
3062 ms
main_image1.png
3608 ms
main_image2.png
3647 ms
main_image3.png
2615 ms
bstrk.js
2231 ms
86 ms
xd_arbiter.php
44 ms
xd_arbiter.php
52 ms
main_image4.png
3379 ms
today_bloodinfo.png
1596 ms
bg_today_bloodinfo.png
1795 ms
bg_today_bloodinfo_more.png
1994 ms
bg_notification.png
2233 ms
file_util.do
3219 ms
file_util.do
2582 ms
file_util.do
2713 ms
file_util.do
2870 ms
file_util.do
2913 ms
file_util.do
3088 ms
file_util.do
3517 ms
file_util.do
3226 ms
bg_favorite_link.png
3080 ms
icon_find_bloodhouse.png
3160 ms
icon_blood_reserve.png
3208 ms
icon_blood_history.png
3247 ms
icon_blood_inspection.png
3274 ms
icon_emi_bldqualify.png
3165 ms
icon_blood_donation.png
3213 ms
icon_blood_certificate.png
3220 ms
icon_abo_friends.png
3258 ms
icon_self_exclusion.png
3279 ms
icon_counsel.png
3323 ms
bg_prev_visual.png
3166 ms
btn_prev_visual.png
3214 ms
next_visual_close.png
3219 ms
popup_20160211.png
4076 ms
bg_next_visual.png
3280 ms
btn_next_visual.png
3327 ms
next_visual_open.png
3162 ms
title_next_visual.png
2819 ms
title_sns_facebook.png
2621 ms
title_sns_blog.png
2489 ms
blog_red_story2.png
2342 ms
logger.v4.js
597 ms
btn_blog_addn_on.png
2126 ms
page.php
261 ms
page.php
272 ms
pic_facebook.png
2000 ms
o_zjiOVHPPW.css
47 ms
U7mZ1oLxgw7.css
58 ms
0pOT4k1QLXd.css
57 ms
sOly--_YKmE.css
60 ms
_rx8naC75Dy.js
65 ms
t-KLv3gqZy0.js
56 ms
uLtKx7ldlvR.js
84 ms
xoyOB9tkUFt.js
83 ms
wyIfBc7KBcg.js
98 ms
zFbZAvnFYMt.js
108 ms
1bAMlWf_tTT.js
82 ms
Xs81m_2832G.js
112 ms
12308711_929950693749214_5475245630465166414_n.png
167 ms
safe_image.php
248 ms
1XOx6cJTSfg.js
88 ms
ZIpeqZ28WpD.js
88 ms
lRyN50VcaFW.js
83 ms
G1sZ2KvRXfK.css
82 ms
AIusK7M5MGT.css
80 ms
12790835_974303415980608_726019137314248160_n.jpg
108 ms
1911722_974122835998666_6203350105973234557_n.jpg
108 ms
12800305_972670946143855_3120808091321863090_n.jpg
112 ms
12794478_972643259479957_769845794337869933_n.jpg
109 ms
12799305_972643252813291_2927348552268747694_n.jpg
102 ms
10310957_972643256146624_3603344371922213812_n.jpg
104 ms
12745856_972643282813288_4325612396050063020_n.jpg
111 ms
12790835_974303415980608_726019137314248160_n.jpg
112 ms
1911722_974122835998666_6203350105973234557_n.jpg
113 ms
12800305_972670946143855_3120808091321863090_n.jpg
113 ms
12794478_972643259479957_769845794337869933_n.jpg
114 ms
12799305_972643252813291_2927348552268747694_n.jpg
113 ms
10310957_972643256146624_3603344371922213812_n.jpg
114 ms
12745856_972643282813288_4325612396050063020_n.jpg
115 ms
wL6VQj7Ab77.png
30 ms
CSXXCvknpgK.png
97 ms
7NEHk19WerA.png
96 ms
title_sns_kakao_story.png
1837 ms
tracker.tsp
1542 ms
tIFXiEZJgab.js
71 ms
K_c2YNQ5fbQ.png
16 ms
QijIVO3ZIrO.png
13 ms
content_kakao.png
1630 ms
R9a_DtVRZgv.js
6 ms
cUDgRFxaoIk.js
5 ms
0JBr1QHp8Gi.js
6 ms
kDOzhTr2W91.js
6 ms
wFYNJ9lyaMJ.js
9 ms
dot_board.png
1624 ms
bul_dot_black.png
1489 ms
dot2.gif
1496 ms
btn_more.png
1461 ms
icon_notice.png
1445 ms
icon_facebook_on.png
1398 ms
icon_blog_off.png
1402 ms
icon_kakao_story_off.png
1367 ms
blog_red_story.png
1411 ms
sns_content_kakao.png
2369 ms
web_accessibility.jpg
1932 ms
footer_div.png
1387 ms
bg_customer_center.png
1360 ms
icon_relsite.png
1403 ms
icon_footer_blog.png
1366 ms
icon_footer_facebook.png
1447 ms
icon_footer_kakao_story.png
1401 ms
bx_loader.gif
1470 ms
icon_main_image_rolling_off.png
1429 ms
controls_play_on.png
1524 ms
controls_stop.png
1485 ms
icon_main_image_rolling_on.png
1525 ms
btn_notification_rolling.png
1484 ms
bloodinfo.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
bloodinfo.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
bloodinfo.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bloodinfo.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Bloodinfo.net main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
bloodinfo.net
Open Graph description is not detected on the main page of Bloodinfo. 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: