15.5 sec in total
601 ms
14.5 sec
421 ms
Visit ibric.org now to see the best up-to-date I BRIC content for South Korea and also check out these interesting facts you probably never knew about ibric.org
BRIC(브릭, 생물학연구정보센터)은 국내・외 생명과학 중심의 연구정보들을 종합적・체계적으로 수집, 가공, 정리, 분석하여 데이터베이스화하고, 이를 인터넷을 통해 연구자들에게 제공 및 연구자들 간 정보교류의 장을 제공.
Visit ibric.orgWe analyzed Ibric.org page load time and found that the first response time was 601 ms and then it took 14.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ibric.org performance score
name
value
score
weighting
Value16.0 s
0/100
10%
Value43.9 s
0/100
25%
Value30.5 s
0/100
10%
Value450 ms
63/100
30%
Value0.173
69/100
15%
Value41.8 s
0/100
10%
601 ms
189 ms
1391 ms
731 ms
1106 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 99% of them (156 requests) were addressed to the original Ibric.org, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Ibric.org.
Page size can be reduced by 2.0 MB (36%)
5.7 MB
3.6 MB
In fact, the total size of Ibric.org main page is 5.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. 65% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 161.3 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 32.5 kB, which is 17% 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 161.3 kB or 86% of the original size.
Potential reduce by 216.3 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. I BRIC images are well optimized though.
Potential reduce by 914.4 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 914.4 kB or 76% of the original size.
Potential reduce by 720.2 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. Ibric.org needs all CSS files to be minified and compressed as it can save up to 720.2 kB or 85% of the original size.
Number of requests can be reduced by 59 (40%)
147
88
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I BRIC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 37 to 1 for CSS and as a result speed up the page load time.
ibric.org
601 ms
index.do
189 ms
index.do
1391 ms
cms.css
731 ms
font-awesome.min.css
1106 ms
cms-common.css
742 ms
board.css
1875 ms
swiper.css
973 ms
scroll.css
911 ms
popup.css
1484 ms
notification.widget.css
1093 ms
communities-main-bottom.widget.css
1111 ms
sitemap.widget.css
1167 ms
cms-common.css
1275 ms
main.css
1290 ms
main-content-02.content.css
1297 ms
main-content-04.content.css
1365 ms
side-ad-area.content.css
1457 ms
top-ad-area.content.css
1473 ms
main-content-03.content.css
1487 ms
top-header.content.css
1559 ms
body-ad-area.content.css
1638 ms
main-content-05.content.css
1658 ms
header.content.css
1667 ms
mobile-bottom-ad.content.css
1669 ms
footer-top-related-site-banner.content.css
1753 ms
main-content-01.content.css
1819 ms
footer.content.css
1841 ms
jquery-2.2.4.min.js
2222 ms
jquery-ui-1.12.1.min.js
2597 ms
cms.js
3890 ms
cms-common.js
2364 ms
jquery.prettydropdowns.js
2025 ms
board.js
2432 ms
swiper.js
2762 ms
scroll.js
2408 ms
popup.js
2547 ms
cms-common.js
2593 ms
js
62 ms
wa.css
1895 ms
froala_style.min.css
1992 ms
define.min.css
1873 ms
sub-guide.css
1865 ms
layout-guide.css
1840 ms
font.css
1823 ms
table.css
1846 ms
main.js
1860 ms
main-content-02.content.js
1808 ms
main-content-04.content.js
1725 ms
main-content-03.content.js
1808 ms
header.content.js
1838 ms
mobile-bottom-ad.content.js
1791 ms
footer-top-related-site-banner.content.js
1703 ms
main-content-01.content.js
1713 ms
notification.widget.js
1794 ms
gnb-mobile.widget.js
1833 ms
sitemap.widget.js
1783 ms
main-bio-news.widget.js
1707 ms
wa.js
1717 ms
select-ul.css
1590 ms
board-list.css
2184 ms
board-view.css
2026 ms
board-write.css
1845 ms
mypage.css
1692 ms
banner_279871720771514363.jpg
190 ms
img-logo.svg
201 ms
thumb_HhNlNkKPESNNSOKEMyrZfBiigr.png
931 ms
thumb_1301150_1723075235000.do
195 ms
thumb_1301072_1722992070000.do
380 ms
thumb_1301103_1723003240000.do
186 ms
thumb_1297612_1719359146000.do
372 ms
thumb_1301207_1723091318000.do
563 ms
thumb_XFqrdoKPkLTRDonOotMYKiKXQb.png
759 ms
thumb_udXOfJtkNVvIUbcGwjjryaPDtI.png
783 ms
thumb_IHaafHDCmnyJTssVezfqaxDdUe.png
1100 ms
0027414_1.jpg
564 ms
0035389_1.jpg
750 ms
0015046_1.jpg
749 ms
0046328_1.png
934 ms
0039189_1.jpg
937 ms
0035236_1.jpg
947 ms
0027946_1.jpg
977 ms
0000054_1.jpg
1116 ms
0041180_1.png
1303 ms
0035812_1.png
1309 ms
0046337_1.png
1321 ms
0024645_1.jpg
1173 ms
0029786_1.jpg
1281 ms
0029089_1.jpg
1301 ms
0026119_1.png
1368 ms
ico-mini-arr-prev.png
1463 ms
ico-mini-arr-next.png
1488 ms
ico-interview@2x.png
1487 ms
QnvlxxsfuLTTgvOfEnPatfpyGW.png
1496 ms
UhscIqnzhfSnbIaEyIJGGRgRPa.png
1508 ms
uyTquRcTUEipQNNEcTmlfwipsH.png
1562 ms
ywwfRoDuBEacYcUcoqUhRWsOMz.png
1645 ms
njkIpJknikzvldgVtXafdttoUV.png
1854 ms
fdWPGLugZgkJeitQMBtxLbjccm.png
1857 ms
diJvVuCuhltGHLyxCqbGqrGaNz.png
1756 ms
Pretendard-Regular.woff
4749 ms
Pretendard-SemiBold.woff
4688 ms
Pretendard-Light.woff
4740 ms
Pretendard-Bold.woff
4989 ms
NanumSquareNeoTTF-ExtraBold.woff
3715 ms
NanumSquareNeoTTF-Bold.woff
3542 ms
NanumSquareNeoTTF-Regular.woff
5408 ms
kqiJYuPZeXfedodHaLbtJHDTIK.png
3894 ms
IaFFeVplUePVCkVUaQyEdfzEMt.jpg
3896 ms
fEDpbHnGNPaCMTmKTkeLOwGEsW.jpg
4081 ms
OmHlCNBRUIRxgkUhxvRUSsMHCb.jpg
4260 ms
IHsvrKmLBYGTLllzbtjwTtNGix.jpg
4289 ms
hQqskwIxZpTGWcPsRIxMQvZSMF.jpg
4148 ms
sdKcHeNPXfgsXCIyQIVpuecuOU.jpg
4353 ms
ico-cal@2x.png
4299 ms
ico-people@2x.png
4320 ms
ico-youtube-play.png
4287 ms
thumb_0000766.png
4276 ms
thumb_0000741.png
4273 ms
thumb_0000743.png
4280 ms
thumb_0000750.png
4180 ms
thumb_0000762.png
4167 ms
thumb_0000757.png
4255 ms
thumb_0000746.png
4266 ms
thumb_0000751.png
4320 ms
thumb_0000755.png
4287 ms
thumb_0000749.png
4188 ms
thumb_1298928_1720662546000.do
4258 ms
thumb_1298076_1719810154000.do
4275 ms
thumb_1300675_1722479259000.do
4334 ms
thumb_1301094_1722996474000.do
4325 ms
thumb_1299548_1721352691000.do
4288 ms
hotbanner-nrf.png
4284 ms
hotbanner-search.png
4094 ms
brichot024.png
4537 ms
briccommunity.png
4149 ms
banner_279641721896601956.jpg
2312 ms
banner_280091722908923493.jpg
2022 ms
new2_161x58_akn.jpg
1679 ms
nrf.png
1513 ms
nric.png
1372 ms
msit.png
1417 ms
img-banner-ntis.gif
1391 ms
2023_08_03_16_26_25_019_1691047585.png
1405 ms
img-banner-abs.gif
1369 ms
cre.png
1367 ms
kolis.png
1411 ms
2023_08_03_16_40_33_027_16910484330.png
1310 ms
2023_08_03_16_49_35_033_1691048975.png
1298 ms
2023_08_03_16_51_28_036_1691049088.png
1304 ms
img-banner-hbn.gif
1321 ms
img-foot-logo.svg
1345 ms
ico-sns-youtube.png
1298 ms
ico-sns-facebook.png
1305 ms
ico-sns-twitter.png
1267 ms
ico-sns-rss.png
1288 ms
banner_280051722497314090.jpg
1679 ms
ibric.org 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.
ibric.org 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
ibric.org SEO score
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ibric.org can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Ibric.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.
ibric.org
Open Graph description is not detected on the main page of I BRIC. 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: