11.7 sec in total
1.9 sec
9.5 sec
287 ms
Click here to check amazing Nado content for United States. Otherwise, check out these important facts you probably never knew about nado.kr
나도코리아
Visit nado.krWe analyzed Nado.kr page load time and found that the first response time was 1.9 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
nado.kr performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value10.8 s
0/100
25%
Value8.6 s
17/100
10%
Value40 ms
100/100
30%
Value0.164
72/100
15%
Value10.1 s
26/100
10%
1917 ms
438 ms
446 ms
468 ms
472 ms
Our browser made a total of 203 requests to load all elements on the main page. We found that 88% of them (179 requests) were addressed to the original Nado.kr, 10% (21 requests) were made to Nadokorea.co.kr and 0% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Nadokorea.co.kr.
Page size can be reduced by 208.4 kB (10%)
2.0 MB
1.8 MB
In fact, the total size of Nado.kr main page is 2.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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 96.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. 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 96.5 kB or 84% of the original size.
Potential reduce by 38.7 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. Nado images are well optimized though.
Potential reduce by 70.5 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 70.5 kB or 74% of the original size.
Potential reduce by 2.6 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. Nado.kr needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 78% of the original size.
Number of requests can be reduced by 58 (29%)
202
144
The browser has sent 202 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nado. 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 as a result speed up the page load time.
nado.kr
1917 ms
css.css
438 ms
java.js
446 ms
float.js
468 ms
js_rolling.js
472 ms
scroll.js
480 ms
jquery-1.7.2.min.js
5 ms
jquery.ajaxQueue.js
515 ms
thickbox-compressed.js
659 ms
jquery.autocomplete.js
667 ms
jquery.autocomplete.css
700 ms
java.js
711 ms
postcode.v2.js
828 ms
data_09e2421a336b32e0520a9502380aee53.jpg
2279 ms
data_a542cd5e0142c09ec3b400bc6fb269fc.jpg
1659 ms
data_cc8187512d73bec82be0fc1bba27f069.jpg
1022 ms
data_d3b3d027f12a73f010f3e413738f2824.gif
4171 ms
data_c5a9e72edcddad5dc918632ccc4ac4d7.jpg
1267 ms
data_cf48757d93c64f60a5908970a4923776.jpg
1031 ms
data_5ce8b501fbdc3ce19095b94ac9b14cd5.jpg
1269 ms
data_650ebebdd10268a3e827042398576b69.jpg
1278 ms
data_24cc76c1130aaeb887848be772d7a837.jpg
1755 ms
data_0c3b46a979acc1776cb1ebe430444188.jpg
1757 ms
data_4adffd704a65d18e0af1529d81415c72.jpg
1526 ms
data_4a96556fcde7abcded2b4db3062dd0c0.jpg
2259 ms
data_9c077f8fcfe9a30a7ca800138549cfba.jpg
1889 ms
data_097b5817662bc22f9bb010690ac420b1.jpg
2243 ms
data_564da24b37168d5240a9c2438bc4e35c.jpg
2003 ms
data_3ff89585c7b73716e9d4edf7af096d5f.jpg
2121 ms
data_ecdd5eec8956e2d893d3d15e9d7b941c.jpg
2248 ms
data_aee15f84a5e281fcd2b97674c297e475.jpg
2353 ms
data_69cbb9ac67d29e5c633a6d79db091bf8.jpg
2490 ms
data_44f3f6c97137ea2614b00ffcd6f863d3.jpg
2736 ms
data_e9acb2e4a3b0594638c58a6fd6449e9c.jpg
2513 ms
mini_back.gif
274 ms
navi_home.gif
274 ms
gubun_bar.gif
388 ms
id.gif
394 ms
pw.gif
438 ms
login.gif
448 ms
%BB%F3%B4%DC%B7%CE%B0%ED.jpg
482 ms
search_bt.gif
497 ms
btt.gif
610 ms
keyword.gif
617 ms
kakao.gif
672 ms
%B8%F0%B9%D9%C0%CF%B9%E8%B3%CA.gif
686 ms
cate01.gif
721 ms
cate02.gif
743 ms
cate03.gif
831 ms
cate04.gif
838 ms
cate05.gif
904 ms
cate06.gif
921 ms
cate07.gif
959 ms
cate08.gif
989 ms
balloon_arrow.gif
1054 ms
balloon_01.gif
1060 ms
balloon_03.gif
1136 ms
balloon_04.gif
1156 ms
balloon_07.gif
1198 ms
balloon_09.gif
1234 ms
data_1907635cfe0a1f39bdfc789e515dd4e3.jpg
1277 ms
left_bg2.gif
1281 ms
today_title.gif
1370 ms
today_bg2.gif
1392 ms
%B4%EB%B7%AE%B1%B8%B8%C5%B9%E8%B3%CA.gif
1427 ms
1373004915.jpg
1468 ms
1373004964.jpg
1339 ms
1373005031.jpg
1338 ms
new_title.gif
1396 ms
ifr.php
1372 ms
roll_today.htm
1443 ms
roll.htm
1494 ms
roll_main.htm
1374 ms
roll_main.htm
1376 ms
roll_main.htm
1438 ms
roll_main.htm
1463 ms
roll_main.htm
1506 ms
new_bg2.gif
1486 ms
160223.js
1949 ms
item_title.gif
1404 ms
1373006868.jpg
1375 ms
1373006891.jpg
1668 ms
1373006907.jpg
1695 ms
1373006930.jpg
1484 ms
1373006974.jpg
1481 ms
%B0%ED%B0%B4%BC%BE%C5%B8.gif
1383 ms
%C0%D4%B1%DD%B0%E8%C1%C2%BE%C8%B3%BB.gif
1422 ms
guide_title.gif
1525 ms
guide1.gif
1517 ms
guide2.gif
1505 ms
guide3.gif
1521 ms
guide4.gif
1520 ms
guide5.gif
1557 ms
guide6.gif
1514 ms
notice_title.gif
1503 ms
n_dot.gif
1505 ms
link_bnr1.jpg
1520 ms
link_bnr2.jpg
1529 ms
link_bnr3.jpg
1572 ms
link_bnr4.jpg
1503 ms
link_bnr5.jpg
1490 ms
link_bnr6.jpg
1505 ms
link_bnr7.jpg
1519 ms
link_bnr8.jpg
1541 ms
quick_top.gif
1584 ms
scroll_today_up.gif
1491 ms
tinyfader.js
1466 ms
css.css
1472 ms
scroll_today_down.gif
1497 ms
quick_bg2.gif
1511 ms
quick_btn_top.gif
1563 ms
%BF%C0%B8%A5%C2%CA%B4%EB%B7%AE%B1%B8%B8%C5.gif
1447 ms
%BF%C0%B8%A5%C2%CA%C5%A5%BE%CB%C4%DA%B5%E5.gif
1423 ms
quick_a.gif
1444 ms
copy_menu.gif
1522 ms
%C4%AB%C7%C7%B6%F3%C0%CC%C6%AE.gif
1522 ms
search_back.gif
1532 ms
menu_back.gif
1361 ms
left_top.gif
1340 ms
left_bg1.gif
1442 ms
balloon_02.gif
1500 ms
balloon_05.gif
1407 ms
balloon_06.gif
1386 ms
balloon_08.gif
1350 ms
today_bg1.gif
1365 ms
new_bg1.gif
1441 ms
cs_back.gif
1470 ms
quick_bg1.gif
1440 ms
copy_back.gif
1371 ms
1373011546.jpg
1790 ms
1373262483.jpg
1848 ms
1376962824.jpg
2895 ms
7601S.JPG
1459 ms
7426S.JPG
1401 ms
7384S.JPG
1411 ms
7381S.JPG
1557 ms
7370S.JPG
1564 ms
7454S.JPG
1573 ms
6441S.JPG
1652 ms
6436S.JPG
1622 ms
6454S.JPG
1591 ms
6478S.JPG
1650 ms
7545S.JPG
1659 ms
6072S.JPG
1652 ms
7418S.JPG
1633 ms
6327S.JPG
1638 ms
7428S.JPG
1663 ms
6514S.JPG
1694 ms
2496S.JPG
1768 ms
6452S.JPG
1685 ms
3497S.JPG
1643 ms
6522S.JPG
1709 ms
5787S.JPG
1733 ms
3534S.JPG
1768 ms
5941S.JPG
1768 ms
5673S.JPG
1719 ms
6513S.JPG
1712 ms
5558S.JPG
1768 ms
5786S.JPG
1777 ms
5175S.JPG
1780 ms
7383S.JPG
1816 ms
3650S.JPG
1790 ms
3471S.JPG
1802 ms
5041S.JPG
1778 ms
6332S.JPG
1768 ms
5298S.JPG
1629 ms
4666S.JPG
1640 ms
6197S.JPG
1667 ms
6442S.JPG
1557 ms
5113S.JPG
1561 ms
6272S.JPG
1585 ms
4829S.JPG
1570 ms
4583S.JPG
1568 ms
6353S.JPG
1514 ms
4785S.JPG
1546 ms
6382S.JPG
1545 ms
2632S.JPG
1539 ms
6589S.JPG
1549 ms
6084S.JPG
1444 ms
5040S.JPG
1518 ms
5845S.JPG
1518 ms
3198S.JPG
1466 ms
6539S.JPG
1515 ms
5138S.JPG
1460 ms
6325S.JPG
1444 ms
5797S.JPG
1492 ms
758S.JPG
1435 ms
2760S.JPG
1397 ms
5812S.JPG
1470 ms
5788S.JPG
1455 ms
4635S.JPG
1414 ms
3541S.JPG
1422 ms
3938S.JPG
1350 ms
6690S.JPG
1352 ms
2222S.JPG
1466 ms
670S.JPG
1444 ms
3363S.JPG
1420 ms
loadingAnimation.gif
1414 ms
mnum_off.png
1350 ms
mnum_1.png
1337 ms
mnum_2.png
1474 ms
mnum_3.png
1439 ms
mnum_on.png
1443 ms
nado.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
Image elements do not have [alt] attributes
Links do not have a discernible name
nado.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
nado.kr SEO score
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
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nado.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Nado.kr 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.
nado.kr
Open Graph description is not detected on the main page of Nado. 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: