Tools & Wizards About Us
diaryshop.co.kr screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

diaryshop.co.kr

다이어리 맞춤제작 전문

Page Load Speed

15.9 sec in total

First Response

1.4 sec

Resources Loaded

14.2 sec

Page Rendered

293 ms

diaryshop.co.kr screenshot

About Website

Click here to check amazing Diaryshop content. Otherwise, check out these important facts you probably never knew about diaryshop.co.kr

맞춤제작 다이어리 전문 쇼핑몰

Visit diaryshop.co.kr

Key Findings

We analyzed Diaryshop.co.kr page load time and found that the first response time was 1.4 sec and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

diaryshop.co.kr performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value7.1 s

32/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.023

2/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

indexpage.php

1401 ms

default.css

400 ms

utils.js

822 ms

jquery-1.4.2.min.js

1590 ms

jQuery.plugin.getQueryString.js

466 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 42% of them (55 requests) were addressed to the original Diaryshop.co.kr, 52% (68 requests) were made to Cypower.co.kr and 4% (5 requests) were made to Asp3.http.or.kr. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Cypower.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.7 kB (76%)

Content Size

346.5 kB

After Optimization

84.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Diaryshop.co.kr main page is 346.5 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. 20% of websites need less resources to load. Javascripts take 287.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 48.0 kB

  • Original 57.3 kB
  • After minification 52.5 kB
  • After compression 9.3 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 48.0 kB or 84% of the original size.

JavaScript Optimization

-74%

Potential reduce by 212.8 kB

  • Original 287.8 kB
  • After minification 251.3 kB
  • After compression 75.1 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 212.8 kB or 74% of the original size.

CSS Optimization

-67%

Potential reduce by 910 B

  • Original 1.4 kB
  • After minification 1.2 kB
  • After compression 445 B

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. Diaryshop.co.kr needs all CSS files to be minified and compressed as it can save up to 910 B or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (62%)

Requests Now

130

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Diaryshop. 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.

Network Requests Diagram

indexpage.php

indexpage.php

1401 ms

default.css

default.css

400 ms

utils.js

utils.js

822 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1590 ms

jQuery.plugin.getQueryString.js

jQuery.plugin.getQueryString.js

466 ms

jQuery.plugin.cart_matrix.js

jQuery.plugin.cart_matrix.js

1392 ms

popup_products_detail.js

popup_products_detail.js

793 ms

popup_cart_modify.js

popup_cart_modify.js

734 ms

wcslog.js

wcslog.js

5 ms

index_font.css

index_font.css

833 ms

index_font.css

index_font.css

970 ms

embed.js

embed.js

584 ms

ASP_Conf.js

ASP_Conf.js

1064 ms

top_logo.gif

top_logo.gif

1735 ms

top_logo_02.gif

top_logo_02.gif

1366 ms

top_1_1.gif

top_1_1.gif

1384 ms

top_1_2.gif

top_1_2.gif

1815 ms

top_1_3.gif

top_1_3.gif

1836 ms

top_1_4.gif

top_1_4.gif

2162 ms

top_1_5.gif

top_1_5.gif

2313 ms

top_1_6.gif

top_1_6.gif

2290 ms

top_1_7.gif

top_1_7.gif

2319 ms

left_menu_01.gif

left_menu_01.gif

2363 ms

left_menu_003.gif

left_menu_003.gif

2391 ms

left_menu_004.gif

left_menu_004.gif

2614 ms

left_menu_23.gif

left_menu_23.gif

2733 ms

left_menu_24.gif

left_menu_24.gif

3363 ms

left_menu_25.gif

left_menu_25.gif

2724 ms

left_menu_26.gif

left_menu_26.gif

2800 ms

left_menu_27.gif

left_menu_27.gif

2844 ms

left_menu_28.gif

left_menu_28.gif

3727 ms

left_menu_29.gif

left_menu_29.gif

3137 ms

left_menu_30.gif

left_menu_30.gif

3215 ms

left_menu_31.gif

left_menu_31.gif

3239 ms

left_menu_32.gif

left_menu_32.gif

3623 ms

left_menu_33.gif

left_menu_33.gif

3651 ms

left_menu_001.gif

left_menu_001.gif

3697 ms

left_menu_15.gif

left_menu_15.gif

3814 ms

pbbs_a_1.gif

pbbs_a_1.gif

4050 ms

pbbs_a_2.gif

pbbs_a_2.gif

4115 ms

pbbs_a_3.gif

pbbs_a_3.gif

4096 ms

pbbs_a_4.gif

pbbs_a_4.gif

4163 ms

great.gif

great.gif

5456 ms

left_b02.gif

left_b02.gif

4422 ms

point1_1.gif

point1_1.gif

7186 ms

point1_2.gif

point1_2.gif

4586 ms

point1_3.gif

point1_3.gif

4600 ms

point1_4.gif

point1_4.gif

4577 ms

point1_5.gif

point1_5.gif

4877 ms

top_menu_01.gif

top_menu_01.gif

464 ms

top_menu_02.gif

top_menu_02.gif

228 ms

top_menu_03.gif

top_menu_03.gif

234 ms

top_menu_04.gif

top_menu_04.gif

198 ms

top_menu_05.gif

top_menu_05.gif

395 ms

top_menu_06.gif

top_menu_06.gif

455 ms

top_menu_07.gif

top_menu_07.gif

455 ms

top_menu_08.gif

top_menu_08.gif

465 ms

top_menu_09.gif

top_menu_09.gif

535 ms

top_img.gif

top_img.gif

1376 ms

icon_search2.gif

icon_search2.gif

677 ms

icon_search.gif

icon_search.gif

679 ms

icon_ball_01.gif

icon_ball_01.gif

692 ms

icon_ball_02.gif

icon_ball_02.gif

693 ms

customer_03_01.gif

customer_03_01.gif

800 ms

customer_03_03.gif

customer_03_03.gif

902 ms

customer_03_02.gif

customer_03_02.gif

904 ms

customerm_01.gif

customerm_01.gif

922 ms

customerm_02.gif

customerm_02.gif

926 ms

customerm_03.gif

customerm_03.gif

1067 ms

customerm_04.gif

customerm_04.gif

1126 ms

customerm_05.gif

customerm_05.gif

1130 ms

customerm_06.gif

customerm_06.gif

1153 ms

customerm_07.gif

customerm_07.gif

1158 ms

customerm_08.gif

customerm_08.gif

1331 ms

customer_04_01.gif

customer_04_01.gif

1352 ms

bottom_menu_01.gif

bottom_menu_01.gif

1354 ms

bottom_menu_02.gif

bottom_menu_02.gif

1383 ms

bottom_menu_03.gif

bottom_menu_03.gif

1388 ms

bottom_menu_04.gif

bottom_menu_04.gif

1605 ms

bottom_menu_05.gif

bottom_menu_05.gif

1576 ms

bottom_menu_06.gif

bottom_menu_06.gif

1579 ms

bottom_menu_07.gif

bottom_menu_07.gif

1564 ms

bottom_menu_08.gif

bottom_menu_08.gif

1613 ms

bottom_menu_09.gif

bottom_menu_09.gif

1618 ms

bottom_menu_10.gif

bottom_menu_10.gif

1760 ms

bottom_menu_11.gif

bottom_menu_11.gif

1615 ms

bottom_menu_12.gif

bottom_menu_12.gif

1592 ms

bottom_menu_13.gif

bottom_menu_13.gif

1651 ms

bottom_02.gif

bottom_02.gif

1694 ms

emd_pt.js

emd_pt.js

473 ms

[sr].gif

[sr].gif

483 ms

m

m

426 ms

bottom_01.gif

bottom_01.gif

1406 ms

topm_space2.gif

topm_space2.gif

1511 ms

icon_search3.gif

icon_search3.gif

1576 ms

customer_04_02.gif

customer_04_02.gif

1579 ms

HTTP_s.js

HTTP_s.js

1404 ms

point2_1.gif

point2_1.gif

4879 ms

point2_2.gif

point2_2.gif

3658 ms

point2_3.gif

point2_3.gif

3332 ms

point2_4.gif

point2_4.gif

3473 ms

point2_5.gif

point2_5.gif

3619 ms

point3_1.gif

point3_1.gif

6324 ms

point3_2.gif

point3_2.gif

3463 ms

point3_3.gif

point3_3.gif

3570 ms

point3_4.gif

point3_4.gif

3585 ms

point3_5.gif

point3_5.gif

3834 ms

st.php

st.php

742 ms

point4_1.gif

point4_1.gif

5325 ms

point4_2.gif

point4_2.gif

3703 ms

point4_3.gif

point4_3.gif

3884 ms

point4_4.gif

point4_4.gif

3962 ms

point4_5.gif

point4_5.gif

3914 ms

bookcover1.gif

bookcover1.gif

4871 ms

bookcover2.gif

bookcover2.gif

4150 ms

gift.gif

gift.gif

5154 ms

check1_1.gif

check1_1.gif

5341 ms

check1_2.gif

check1_2.gif

4323 ms

sst.php

sst.php

479 ms

check1_3.gif

check1_3.gif

4465 ms

check2_1.gif

check2_1.gif

5300 ms

check2_2.gif

check2_2.gif

4846 ms

check2_3.gif

check2_3.gif

5109 ms

system1.gif

system1.gif

5074 ms

system2.gif

system2.gif

5680 ms

system3.gif

system3.gif

5175 ms

system4.gif

system4.gif

5201 ms

log_run.php

log_run.php

474 ms

system5.gif

system5.gif

6491 ms

system6.gif

system6.gif

5060 ms

system7.gif

system7.gif

4872 ms

customer_01.gif

customer_01.gif

5124 ms

Accessibility Review

diaryshop.co.kr accessibility score

77

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

diaryshop.co.kr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

diaryshop.co.kr SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diaryshop.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 Diaryshop.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.

Social Sharing Optimization

diaryshop.co.kr

Open Graph description is not detected on the main page of Diaryshop. 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: