Tools & Wizards About Us
prettee.co.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

prettee.co.kr

PRETTEE

Page Load Speed

8.8 sec in total

First Response

1.4 sec

Resources Loaded

7.1 sec

Page Rendered

318 ms

prettee.co.kr screenshot

About Website

Visit prettee.co.kr now to see the best up-to-date PRETTEE content and also check out these interesting facts you probably never knew about prettee.co.kr

프리티는 그래픽, 레터링 티셔츠 쇼핑몰입니다. 후드티, 후드집업, 맨투맨, 긴팔, 반팔라운드티를 제작, 공급합니다.

Visit prettee.co.kr

Key Findings

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

Performance Metrics

prettee.co.kr performance score

0

Network Requests Diagram

prettee.co.kr

1399 ms

pre_style.css

804 ms

css

50 ms

font-awesome.min.css

13 ms

style.css

407 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 65% of them (35 requests) were addressed to the original Prettee.co.kr, 11% (6 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Prettee.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.9 kB (21%)

Content Size

766.6 kB

After Optimization

602.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prettee.co.kr main page is 766.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 570.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 18.9 kB

  • Original 24.4 kB
  • After minification 19.3 kB
  • After compression 5.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 5.1 kB, which is 21% 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 18.9 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 20.8 kB

  • Original 570.8 kB
  • After minification 550.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. PRETTEE images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 85.9 kB

  • Original 122.0 kB
  • After minification 99.6 kB
  • After compression 36.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 85.9 kB or 70% of the original size.

CSS Optimization

-77%

Potential reduce by 38.3 kB

  • Original 49.4 kB
  • After minification 45.2 kB
  • After compression 11.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. Prettee.co.kr needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (46%)

Requests Now

46

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PRETTEE. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

prettee.co.kr

prettee.co.kr

1399 ms

pre_style.css

pre_style.css

804 ms

css

css

50 ms

font-awesome.min.css

font-awesome.min.css

13 ms

style.css

style.css

407 ms

const.js

const.js

456 ms

require.min.js

require.min.js

55 ms

require.config.js

require.config.js

466 ms

jquery.js

jquery.js

15 ms

skdslider.js

skdslider.js

508 ms

nanumgothic.css

nanumgothic.css

14 ms

skdslider.css

skdslider.css

397 ms

logo.png

logo.png

405 ms

3561fe3b33b3b8_1444930483.jpg

3561fe3b33b3b8_1444930483.jpg

1018 ms

15655c8e6ec93ffb_1439229676.jpg

15655c8e6ec93ffb_1439229676.jpg

837 ms

FILE13561e88f6b6d58_1444841718.jpg

FILE13561e88f6b6d58_1444841718.jpg

1130 ms

4569646175a7c4_1452688919.jpg

4569646175a7c4_1452688919.jpg

1381 ms

45696458d769f9_1452688781.jpg

45696458d769f9_1452688781.jpg

1780 ms

4569645dfc6315_1452688863.jpg

4569645dfc6315_1452688863.jpg

1950 ms

FILE21565f93e57017e_1449104357.jpg

FILE21565f93e57017e_1449104357.jpg

1754 ms

FILE2355b7ad2d0313d_1438100781.jpg

FILE2355b7ad2d0313d_1438100781.jpg

1823 ms

FILE23561e88f6c6f55_1444841718.jpg

FILE23561e88f6c6f55_1444841718.jpg

2027 ms

1001_56dd1498e997f_thumb.jpg

1001_56dd1498e997f_thumb.jpg

1780 ms

893_56d6cc1260f46_thumb.jpg

893_56d6cc1260f46_thumb.jpg

2432 ms

976_56d024ab95f49_thumb.jpg

976_56d024ab95f49_thumb.jpg

2698 ms

myphoto.jpg

myphoto.jpg

2299 ms

192_55e700968fe7b_thumb.jpg

192_55e700968fe7b_thumb.jpg

2513 ms

193_55e6760722b1d_thumb.jpg

193_55e6760722b1d_thumb.jpg

2865 ms

250_560123e1a04a5_thumb.jpg

250_560123e1a04a5_thumb.jpg

3787 ms

arrow_top.png

arrow_top.png

2756 ms

0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf

0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf

13 ms

OsJ2DjdpjqFRVUSto6IffKCWcynf_cDxXwCLxiixG1c.ttf

OsJ2DjdpjqFRVUSto6IffKCWcynf_cDxXwCLxiixG1c.ttf

14 ms

2Q-AW1e_taO6pHwMXcXW5w.ttf

2Q-AW1e_taO6pHwMXcXW5w.ttf

15 ms

NanumGothic-Regular.woff

NanumGothic-Regular.woff

72 ms

NanumGothic-Bold.woff

NanumGothic-Bold.woff

67 ms

NanumGothic-ExtraBold.woff

NanumGothic-ExtraBold.woff

70 ms

line.gif

line.gif

2912 ms

icon_date_end.png

icon_date_end.png

3003 ms

icon_winner.png

icon_winner.png

3119 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

54 ms

Ngom.Util.js

Ngom.Util.js

3174 ms

domReady.min.js

domReady.min.js

82 ms

analytics.js

analytics.js

84 ms

slide-bg-active.png

slide-bg-active.png

3099 ms

slide-bg.png

slide-bg.png

3165 ms

left.png

left.png

3312 ms

right.png

right.png

3435 ms

12088587_1729696727253783_3285700682083441253_n.jpg

12088587_1729696727253783_3285700682083441253_n.jpg

83 ms

12278686_906579856104471_6433383951189082505_n.jpg

12278686_906579856104471_6433383951189082505_n.jpg

118 ms

jquery-ui.min.js

jquery-ui.min.js

21 ms

collect

collect

31 ms

sdk.js

sdk.js

30 ms

Ngom.SnsLogin.js

Ngom.SnsLogin.js

4587 ms

jquery-loader.js

jquery-loader.js

517 ms

SEO Factors

prettee.co.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prettee.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed language. Our system also found out that Prettee.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.

Social Sharing Optimization

prettee.co.kr

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