11.2 sec in total
2.2 sec
8.5 sec
498 ms
Welcome to diaryworld.co.kr homepage info - get ready to check Diaryworld best content right away, or after learning these important things about diaryworld.co.kr
다이어리, 시스템 다이어리, 수첩, 캘린더, 각종부채 및 각종 인쇄물 제작
Visit diaryworld.co.krWe analyzed Diaryworld.co.kr page load time and found that the first response time was 2.2 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
diaryworld.co.kr performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value8.5 s
2/100
25%
Value16.5 s
0/100
10%
Value60 ms
100/100
30%
Value0.286
42/100
15%
Value4.1 s
87/100
10%
2174 ms
1109 ms
902 ms
1581 ms
694 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 98% of them (118 requests) were addressed to the original Diaryworld.co.kr, 2% (2 requests) were made to Adlog.adinsight.co.kr. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Diaryworld.co.kr.
Page size can be reduced by 154.3 kB (11%)
1.4 MB
1.2 MB
In fact, the total size of Diaryworld.co.kr main page is 1.4 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 28.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 4.9 kB, which is 15% 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 28.4 kB or 86% 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. Diaryworld images are well optimized though.
Potential reduce by 80.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 80.9 kB or 68% of the original size.
Potential reduce by 6.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. Diaryworld.co.kr needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 69% of the original size.
Number of requests can be reduced by 9 (8%)
119
110
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diaryworld. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
diaryworld.co.kr
2174 ms
style.css
1109 ms
common.js
902 ms
jquery.min.js
1581 ms
slides.min.jquery.js
694 ms
reset.css
227 ms
basic.css
229 ms
layout.css
224 ms
main.css
234 ms
product.css
704 ms
board.css
451 ms
302_b.GIF
228 ms
301_b.JPEG
906 ms
logo.png
483 ms
cate_1.gif
229 ms
cate_11.gif
234 ms
cate_12.gif
456 ms
cate_13.gif
452 ms
cate_14.gif
455 ms
cate_15.gif
466 ms
cate_2.gif
676 ms
cate_21.gif
682 ms
cate_22.gif
683 ms
cate_23.gif
698 ms
cate_24.gif
703 ms
cate_25.gif
1633 ms
cate_3.gif
909 ms
cate_31.gif
909 ms
cate_32.gif
929 ms
cate_4.gif
926 ms
cate_41.gif
1128 ms
cate_42.gif
1133 ms
cate_5.gif
1137 ms
cate_51.gif
1149 ms
cate_52.gif
1159 ms
cate_53.gif
1353 ms
h_center.gif
1360 ms
h_bank.gif
1365 ms
h_webhard.gif
1369 ms
h_search.gif
1390 ms
h_search_btn.gif
1579 ms
main_visual_1.jpg
2039 ms
main_visual_2.jpg
2274 ms
main_visual_3.jpg
3583 ms
main_visual_4.jpg
2082 ms
main_bn1.gif
1804 ms
main_bn2.gif
2279 ms
trs_esc.js
2757 ms
main_list_1.gif
1814 ms
num_more.gif
2038 ms
num1_1.gif
2040 ms
num1_2.gif
1870 ms
num1_3.gif
2039 ms
num1_4.gif
2045 ms
num1_5.gif
2044 ms
world_104.JPEG
2050 ms
main_picon_best.gif
1876 ms
main_picon_dis.gif
2039 ms
world_244.JPEG
2044 ms
main_picon_att.gif
2042 ms
world_387.JPEG
2054 ms
main_picon_new.gif
1881 ms
world_361.JPEG
2037 ms
world_249.JPEG
2044 ms
world_358.JPEG
2038 ms
world_388.JPEG
2054 ms
world_253.JPEG
1887 ms
163.JPEG
2039 ms
world_374.JPEG
2043 ms
world_152.JPEG
2045 ms
world_258.JPEG
2047 ms
world_407.JPEG
1894 ms
world_260.JPEG
2038 ms
world_408.JPEG
2042 ms
world_264.JPEG
2052 ms
main_list_2.gif
2041 ms
num2_1.gif
1900 ms
num2_2.gif
1996 ms
num2_3.gif
1826 ms
num2_4.gif
1616 ms
num2_5.gif
1616 ms
world_371.JPEG
1626 ms
world_384.JPEG
1551 ms
177.JPEG
1586 ms
176.JPEG
1586 ms
world_283.JPEG
1578 ms
world_370.JPEG
1565 ms
world_286.JPEG
1454 ms
world_185.JPEG
1537 ms
world_398.JPEG
1575 ms
world_292.JPEG
1560 ms
world_131.JPEG
1558 ms
190.JPEG
1390 ms
main_list_3.gif
1451 ms
num3_1.gif
1520 ms
num3_2.gif
1552 ms
num3_3.gif
1533 ms
log.php
181 ms
world_402.JPEG
1390 ms
world_410.JPEG
1386 ms
world_267.JPEG
1442 ms
world_405.JPEG
1497 ms
world_375.JPEG
1521 ms
world_193.JPEG
1371 ms
world_397.JPEG
1384 ms
100.JPEG
1374 ms
copyright.gif
1435 ms
quick_1.gif
1456 ms
quick_2.gif
1365 ms
quick_3.gif
1367 ms
quick_4.gif
1363 ms
quick_8.gif
1365 ms
quick_5.gif
1393 ms
quick_7.gif
1341 ms
quick_6.gif
1364 ms
header_bg.gif
1368 ms
cate_bg.gif
1360 ms
quick_bg.gif
1368 ms
btn_roll_on.gif
1393 ms
btn_roll_off.gif
1336 ms
diaryworld.co.kr 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.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
diaryworld.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
diaryworld.co.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
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diaryworld.co.kr 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 Diaryworld.co.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.
diaryworld.co.kr
Open Graph description is not detected on the main page of Diaryworld. 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: