7.7 sec in total
1.8 sec
5.8 sec
162 ms
Welcome to blog.donga.com homepage info - get ready to check Blog Donga best content for South Korea right away, or after learning these important things about blog.donga.com
대한민국을 대표하는 정론지 동아일보는 디지털 창인 동아닷컴과 함께 공정하고 정확한 뉴스로 독자 여러분과 더 나은 미래를 만들어 나가겠습니다.
Visit blog.donga.comWe analyzed Blog.donga.com page load time and found that the first response time was 1.8 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
blog.donga.com performance score
name
value
score
weighting
Value7.0 s
2/100
10%
Value12.8 s
0/100
25%
Value15.0 s
1/100
10%
Value1,020 ms
27/100
30%
Value0.202
62/100
15%
Value17.7 s
4/100
10%
1769 ms
616 ms
577 ms
387 ms
385 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 94% of them (88 requests) were addressed to the original Blog.donga.com, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Img.donga.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Blog.donga.com.
Page size can be reduced by 377.0 kB (55%)
683.3 kB
306.2 kB
In fact, the total size of Blog.donga.com main page is 683.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 255.3 kB which makes up the majority of the site volume.
Potential reduce by 53.1 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 53.1 kB or 81% of the original size.
Potential reduce by 17.0 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. Blog Donga images are well optimized though.
Potential reduce by 172.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 172.4 kB or 68% of the original size.
Potential reduce by 134.5 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. Blog.donga.com needs all CSS files to be minified and compressed as it can save up to 134.5 kB or 85% of the original size.
Number of requests can be reduced by 57 (61%)
93
36
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Donga. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
blog.donga.com
1769 ms
style.css
616 ms
styles.css
577 ms
style.css
387 ms
pagenavi-css.css
385 ms
l10n.js
387 ms
jquery.js
1151 ms
editable-comments.js
578 ms
superfish.js
579 ms
general.js
762 ms
jquery-ui.css
1337 ms
default.css
768 ms
shortcodes.css
1349 ms
custom.css
802 ms
head_line1.js
951 ms
easySlider1.7.js
669 ms
screen.css
511 ms
copyright_donga.js
585 ms
ui.core.js
818 ms
ui.widget.js
774 ms
ui.mouse.js
779 ms
ui.resizable.js
1164 ms
ui.draggable.js
1344 ms
ui.button.js
964 ms
ui.position.js
973 ms
ui.dialog.js
973 ms
ui.sortable.js
1584 ms
menu.js
1156 ms
acecounter_V70.20130719.js
794 ms
reset.css
1127 ms
analytics.js
21 ms
logo1.gif
196 ms
thumb.php
194 ms
thumb.php
195 ms
thumb.php
383 ms
thumb.php
749 ms
thumb.php
386 ms
2.jpg
386 ms
3.jpg
389 ms
widget_banner01.png
576 ms
widget_banner02.png
578 ms
widget_social.png
774 ms
thumb.php
583 ms
thumb.php
595 ms
thumb.php
958 ms
thumb.php
772 ms
thumb.php
778 ms
thumb.php
984 ms
lan6762-264x172.jpg
1320 ms
15883485691455751448-264x172.jpg
1347 ms
13874807271455701148-264x172.jpg
964 ms
11205623961455743270-264x172.jpg
1357 ms
1855924871455666904-264x172.jpg
1542 ms
p1460260-264x172.jpg
1543 ms
lan6737-264x172.jpg
1368 ms
style_copyright.css
1509 ms
gnb_logo.gif
809 ms
collect
11 ms
menu_recommend.png
1481 ms
menu_vertical_line.png
1494 ms
menu_reporter.png
1503 ms
menu_arrow.png
1640 ms
menu_specialist_hover.png
1659 ms
menu_singlecut.png
1669 ms
menu_searchform.png
1671 ms
bg_login.png
1683 ms
btn_login.png
1690 ms
bg_gnb_line.gif
206 ms
widget_title_notice.png
380 ms
bullet.png
399 ms
widget_title_best.png
411 ms
widget_title_freshman.png
412 ms
widget_title_recommend.png
426 ms
tab_daily_hover.png
408 ms
tab_yesterday.png
546 ms
tab_weekly.png
568 ms
tab_monthly.png
579 ms
tab_ngh.png
581 ms
widget_title_photocenter.png
596 ms
bg60.png
600 ms
widget_title_latest.png
724 ms
widget_title_comment.png
745 ms
reporter_title01.png
757 ms
reporter_btn_close.gif
759 ms
reporter_title02.png
777 ms
reporter_title03.png
779 ms
reporter_title04.png
915 ms
footer_logo.gif
922 ms
footer_menu.gif
937 ms
ui-bg_flat_75_ffffff_40x100.png
905 ms
ui-icons_222222_256x240.png
925 ms
widget_arrow_left.png
926 ms
widget_arrow_right.png
1250 ms
gather.donga.com
390 ms
blog.donga.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
blog.donga.com 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
blog.donga.com 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
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.donga.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Blog.donga.com 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.
blog.donga.com
Open Graph description is not detected on the main page of Blog Donga. 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: