8.2 sec in total
530 ms
7.3 sec
377 ms
Click here to check amazing M DBpia content for South Korea. Otherwise, check out these important facts you probably never knew about m.dbpia.co.kr
DBpia는 국내 우수 학술기관이 발행한 저널과 논문을 제공하고 있습니다. 연구자에게 꼭 맞는 콘텐츠와 서비스를 한 곳에서 만나보세요.
Visit m.dbpia.co.krWe analyzed M.dbpia.co.kr page load time and found that the first response time was 530 ms and then it took 7.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.
m.dbpia.co.kr performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value21.5 s
0/100
25%
Value8.6 s
17/100
10%
Value4,860 ms
0/100
30%
Value0.078
94/100
15%
Value24.5 s
0/100
10%
530 ms
1119 ms
66 ms
521 ms
531 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 69% of them (84 requests) were addressed to the original M.dbpia.co.kr, 20% (25 requests) were made to Chat-static.happytalkio.com and 4% (5 requests) were made to Nurimedia-upload.s3.ap-northeast-2.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain M.dbpia.co.kr.
Page size can be reduced by 379.6 kB (30%)
1.3 MB
881.5 kB
In fact, the total size of M.dbpia.co.kr main page is 1.3 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 794.2 kB which makes up the majority of the site volume.
Potential reduce by 199.5 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 58.8 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 199.5 kB or 84% of the original size.
Potential reduce by 178.1 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. Obviously, M DBpia needs image optimization as it can save up to 178.1 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 333 B
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.
Potential reduce by 1.7 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. M.dbpia.co.kr has all CSS files already compressed.
Number of requests can be reduced by 68 (60%)
113
45
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M DBpia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
m.dbpia.co.kr
530 ms
m.dbpia.co.kr
1119 ms
gtm.js
66 ms
font.min.css
521 ms
nuri_slider.css
531 ms
dp_main.min.css
715 ms
common.min.css
533 ms
layer.min.css
537 ms
ai_idea_search_box_recommendation.css
542 ms
wcslog.js
34 ms
header_ai_idea.js
528 ms
lottie-player.js
36 ms
lottie-player.js
34 ms
alarm_after_login.js
362 ms
js
45 ms
mobile_app_utils.min.js
366 ms
utils.js
380 ms
lodash.min.js
576 ms
text_formatter.js
530 ms
statistics.min.js
534 ms
cookie_task.min.js
540 ms
layer_util.min.js
547 ms
layer_event.min.js
566 ms
layer_api.js
706 ms
layer_template.min.js
707 ms
multilingual.min.js
716 ms
local_storage_util.min.js
724 ms
header.js
745 ms
left_navigation_utils.min.js
754 ms
node_list_utils.min.js
882 ms
kakao.min.js
1274 ms
social_network_share.min.js
892 ms
gnb.min.js
899 ms
top_banner_uiux.min.js
923 ms
listener-util.min.js
933 ms
loader.js
22 ms
nuri_slider.js
1059 ms
index-v2.min.js
1067 ms
comn_common.css
889 ms
maxresdefault.jpg
92 ms
DBpia_app_android.png
719 ms
idea_logo.png
193 ms
loading.gif
255 ms
ico_close.svg
193 ms
ico_school.svg
194 ms
ico_arrow.svg
196 ms
ico_person.svg
376 ms
dbpia_2.jpg
388 ms
ico_twitter.svg
373 ms
ico_facebook.svg
371 ms
ico_kakao.svg
378 ms
ico_blog.svg
383 ms
citeasy_slider_1.png
760 ms
citeasy_slider_2.png
745 ms
citeasy_slider_3.png
963 ms
citeasy_slider_4.png
969 ms
chrome.png
961 ms
img_support.png
564 ms
img_chrom.png
746 ms
service_info1.svg
1548 ms
service_info2.svg
935 ms
service_info3.svg
1141 ms
service_info4.svg
1690 ms
img_sample_layer.png
1134 ms
bn-GCS.png
1171 ms
Right-Ok.png
1172 ms
kepa.png
1319 ms
aws.png
1314 ms
ISMS-P.png
1325 ms
instagram.png
1326 ms
x_logo.png
1487 ms
youtube.png
1500 ms
ico_naverblog.png
1501 ms
DBpia_app_android_mo.png
711 ms
DBpia_app_ios.png
718 ms
DBpia_app_ios_mo.png
734 ms
main_alarm_emptyIMG.svg
744 ms
logo_dbpia.png
1481 ms
mybook.svg
1636 ms
bell.svg
1656 ms
notokr-regular.woff
1749 ms
notokr-demilight.woff
1764 ms
notokr-medium.woff
1610 ms
notokr-light.woff
1696 ms
notokr-thin.woff
1871 ms
happytalk.chat.v2.min.js
1785 ms
notokr-bold.woff
1840 ms
global-menu-normal.svg
1649 ms
language.svg
1689 ms
ico_use.png
1752 ms
ico_visit.png
1766 ms
btn_banner_prev.svg
1824 ms
btn_banner_next.svg
1852 ms
ico_study.png
1690 ms
img_statistics_01.png
1545 ms
img_statistics_02.png
1546 ms
img_statistics_03.png
1552 ms
button
771 ms
polyfills-4f07b0c20fc9b3d5aa59.js
380 ms
main-8f14ee0978249d4838d8.js
569 ms
webpack-e067438c4cf4ef2ef178.js
569 ms
framework.1cde045124b4a7914091.js
760 ms
f357f4e3.d32c165e533a63787f2e.js
584 ms
cb1608f2.e165191215595e067da9.js
585 ms
958b4c57.32684ee438d552036466.js
587 ms
c943faba.7d1a899dac0432e83bce.js
758 ms
af13d906.a804e7b996dbeb810f1b.js
758 ms
ec1189df.ef5f80c4bafde0f1cc8b.js
766 ms
dfe1566c.66318f9ca02279f24098.js
780 ms
commons.5ed0d082ed0306261c06.js
979 ms
74dfff515e69b5b4dc2cf810cb4cecee4ab83217.ce4a353312c9f732911f.js
1134 ms
3f46df925423d5c64a69562d6ae1385432735eb0.1e351bb4edd232575d41.js
1137 ms
4b40f431fcde1732c0dd294d0cf9b2fac504dae5.603d37ea579e85699571.js
948 ms
_app-6572cbbea19ab51ae84b.js
1145 ms
b0d83d1a.859f89eb1c277efc1273.js
1363 ms
e8ee99f13f1e4d46881f90903eaae49123b0869d.a0e8f1f96d69d171c055.js
1329 ms
40332ee1415d5430f4fa0be30d5c1ba7b73cdd43.0321725c7ab3673bb83b.js
1174 ms
f7a9922557e4ecbe96b1a45137be304e5aafa26d.0f3fae6b97f3e7d98060.js
1323 ms
959782938b524824b2749953f9a55103c0edf640.657e7e67be70241e7674.js
1327 ms
button-95f139fa6838301368b5.js
1338 ms
_buildManifest.js
1370 ms
_ssgManifest.js
1513 ms
m.dbpia.co.kr accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
m.dbpia.co.kr 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
m.dbpia.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 M.dbpia.co.kr 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 M.dbpia.co.kr 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.
m.dbpia.co.kr
Open Graph data is detected on the main page of M DBpia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: