9.7 sec in total
1.5 sec
7.7 sec
509 ms
Click here to check amazing Offeng Dangi content for South Korea. Otherwise, check out these important facts you probably never knew about offeng.dangi.co.kr
Visit offeng.dangi.co.krWe analyzed Offeng.dangi.co.kr page load time and found that the first response time was 1.5 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
offeng.dangi.co.kr performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value27.7 s
0/100
25%
Value15.9 s
0/100
10%
Value2,040 ms
7/100
30%
Value0.507
16/100
15%
Value28.2 s
0/100
10%
1495 ms
404 ms
998 ms
614 ms
614 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 79% of them (126 requests) were addressed to the original Offeng.dangi.co.kr, 11% (17 requests) were made to Eng.dangi.co.kr and 8% (13 requests) were made to Static-cache.dangi.co.kr. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Eng.dangi.co.kr.
Page size can be reduced by 567.5 kB (14%)
4.0 MB
3.5 MB
In fact, the total size of Offeng.dangi.co.kr main page is 4.0 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. 70% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 115.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 38.7 kB, which is 29% 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 115.4 kB or 87% of the original size.
Potential reduce by 119.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. Offeng Dangi images are well optimized though.
Potential reduce by 283.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 283.9 kB or 70% of the original size.
Potential reduce by 49.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. Offeng.dangi.co.kr needs all CSS files to be minified and compressed as it can save up to 49.2 kB or 83% of the original size.
Number of requests can be reduced by 27 (17%)
158
131
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Offeng Dangi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
offeng.dangi.co.kr
1495 ms
tgnb.css
404 ms
jquery-1.11.0.min.js
998 ms
site.js
614 ms
common.js
614 ms
pub.js
429 ms
common.js
645 ms
jquery.bxslider.min.js
855 ms
modernizr.min.js
403 ms
new_left_menu.js
796 ms
TweenMax.min.js
1034 ms
reset.css
410 ms
common_v2.css
991 ms
jquery.bxslider.min.js
816 ms
CresendoScriptV60.js
817 ms
main_v2.css
670 ms
conversion.js
15 ms
logo_offeng_v2.gif
204 ms
ex_08.jpg
949 ms
ex_01.jpg
1171 ms
ex_07.jpg
3607 ms
ex_03.jpg
1467 ms
ex_04.jpg
2526 ms
ex_05.jpg
2310 ms
ex_06.jpg
2760 ms
popup_busan_event.png
1873 ms
logo_offeng_on.gif
1713 ms
logo_st.gif
1957 ms
nav01.gif
2108 ms
nav02.gif
2202 ms
btn_change.png
2344 ms
nav03.gif
2446 ms
a294f2ec897b9deb8ca3ed816b9e8655.gif
209 ms
7c3c5e1680e0a0544745ffb6bbdbe5e3.gif
219 ms
gnb_tab_01.gif
209 ms
72e4b77fd48fe9111a1118fe1897ef5b.png
217 ms
gnb_tit_01.png
203 ms
gnb_tab_01.png
396 ms
gnb_tab_02.png
402 ms
gnb_tab_03.png
411 ms
gnb_tab_04.png
414 ms
gnb_tit_02.png
430 ms
gnb_tab_05.png
432 ms
gnb_tab_06.png
598 ms
gnb_tab_07.png
601 ms
gnb_tab_08.png
616 ms
gnb_tab_09.png
618 ms
gnb_tab_10.png
644 ms
gnb_tab_11.png
648 ms
gnb_tab_02.gif
799 ms
gnb_nav_01.gif
800 ms
gnb_nav_02.gif
821 ms
gnb_nav_08.gif
825 ms
gnb_nav_03.gif
857 ms
gnb_nav_04.gif
862 ms
bg_num.png
998 ms
gnb_nav_05.gif
999 ms
gnb_nav_06.gif
1025 ms
gnb_nav_07.gif
1028 ms
ban_aca_tit.gif
1072 ms
ban_layer_01.gif
1078 ms
btn_close.png
1199 ms
ban_layer_02.gif
1395 ms
ban_layer_03.gif
1433 ms
ban_layer_04.gif
1233 ms
ban_layer_05.gif
1285 ms
skybnn2.png
1295 ms
105 ms
bg_bar.gif
200 ms
fst_class.png
214 ms
lnb_login_icon.png
213 ms
lnb_sign_icon.png
216 ms
count
468 ms
lnb_arrow_down_wh.png
208 ms
icon_new.png
307 ms
lnb_arrow_up_wh.png
324 ms
lnb_arrow_down_dk.png
324 ms
my_sm.png
2435 ms
msg_ceo.png
2446 ms
link_dangi_tab.jpg
2559 ms
41 ms
get_famous_list
1527 ms
calendar_ajax_v2
1802 ms
tit_advice_online.gif
1298 ms
btn_cancle_02.gif
1308 ms
btn_confirm_02.gif
1385 ms
skybnn3.png
1426 ms
ban_lec_summatus_t100_120.gif
1324 ms
tit_live_ask.gif
1330 ms
ico_asking_state_on.gif
1391 ms
ico_class_receive.png
1437 ms
c08341a797a622581164751c3f54e07e.png
1504 ms
1d60466ff7e830363979869b786d679d.png
1890 ms
16eaefdfcf79876a66166d32e91d775a.png
1566 ms
938f612e83f1fc59eb470d1bd9cc37e3.png
1400 ms
24d86d76ebd22ba7f88a6dfa10214147.png
2257 ms
dddeb583686cddb0ee96f5b4971e9ce4.png
1743 ms
5a991d72fbf00f54e065b0b9c2817af3.jpg
1955 ms
612ae5e09ab17011bf24937107f1bdd8.jpg
1560 ms
tit_sale_event.png
1579 ms
88ef8ba651b8a9b1b60c574b2ee46c89.jpg
1612 ms
23678fcae2e52b52e1d6b52c46453eef.jpg
2103 ms
c21684510f9bd6d391c3f693581454e1.jpg
1964 ms
b9ee416415bb0ce33975d619954db6f8.jpg
1951 ms
491261b245958a7f29ddb42e4d83e0d8.jpg
1757 ms
96eef4c286e115766bfdd428df3aeaa0.jpg
1802 ms
1c840793041e434a0a400acfc01b142b.jpg
1825 ms
be5c0395cc61d071867c958c9f0dc652.gif
1978 ms
99a97fcc0e91301950215c45d033d8f1.gif
1971 ms
eb263017bbaf745efa82f48ccdd8ea11.gif
1954 ms
tit_aca_notice.gif
1952 ms
btn_aca_schedule.gif
1877 ms
btn_room_list.gif
1890 ms
btn_qna.gif
1913 ms
btn_faq.gif
1922 ms
btn_more.gif
1845 ms
tit_lineup.png
1801 ms
lineup_ban.jpg
1782 ms
e3f443699c70bc0165ad2e4e7853a40a.jpg
3016 ms
ffb78c50493d46e23f1abd2bf16fb686.jpg
2199 ms
ec86952817bab22b6b0e3aa476418e6b.jpg
2219 ms
f715b1d6e78752324dbf271fa9d7998f.jpg
1929 ms
a9b900e965cc7ec78aea9b9a97374f30.jpg
2168 ms
d7209fc8104896639b49f20253d6b645.jpg
1965 ms
107a6cad6b47c87d892601c8cab6f723.jpg
2053 ms
7dd59b2e6dfc1ad89d23db7f62c7743e.jpg
3074 ms
cc70184dab9250c4b4d990583bfb4959.jpg
2260 ms
tit_live_lecture.png
2059 ms
tit_aca_schedule.png
2066 ms
tit_epilogue.png
1944 ms
e4d8d7aefa88612e0620db80691801c0.jpg
2054 ms
5df65fcccb65e532f469e5f62c6f1a20.jpg
1971 ms
bf9de445100f70a56d955083f62b4594.jpg
2176 ms
03462cf2eb12cb1526b1b68f650763c0.jpg
2020 ms
fb7120ab5b8fef5bdfa3a6e28482f872.jpg
2056 ms
470631c2e15f1adbe92197d47d4ac26e.jpg
1908 ms
e87a944b2bbcff4a23192cc3856075df.jpg
1976 ms
4c6d7707d20fb5c4faeb7a79a0fb50c6.jpg
1890 ms
e14e6c89e878677312961ada2cdff66a.jpg
1917 ms
ee8aff9452214164b1225d49ea00605f.jpg
1921 ms
b16f95e19c72799452147a9af96876e4.jpg
1929 ms
49a200e2ccb0662ec0cd70997b4cd7df.jpg
1924 ms
2d94124d629539d182422cc28a5870c7.jpg
1960 ms
7868c75ae3526835d7a1291511ad433e.jpg
1936 ms
1643cbb8c6be7115a6bf96bf10325caf.jpg
1926 ms
7d26af8ea75b195179f4109fa6b53781.jpg
1944 ms
d2aa688002235186b7ac0eb54ca1355d.jpg
1970 ms
img_medal.jpg
2627 ms
dc21856109f3f48c0979330675cd81ed.png
2004 ms
ico_bg_dday.png
1934 ms
bt_cls.png
1932 ms
bg_ban_indicator.png
1952 ms
btn_view_mov.gif
1958 ms
TOEI_1.jpg
2051 ms
btn_play.png
1689 ms
TOEI_2.jpg
1885 ms
TOEI_3.jpg
1605 ms
TOEI_4.jpg
1549 ms
TOEI_5.jpg
1676 ms
bg_calendar_on.png
1653 ms
offeng.dangi.co.kr 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
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
offeng.dangi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
offeng.dangi.co.kr 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
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Offeng.dangi.co.kr 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 Offeng.dangi.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.
offeng.dangi.co.kr
Open Graph description is not detected on the main page of Offeng Dangi. 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: