Tools & Wizards About Us
vintageuncle.co.kr screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

vintageuncle.co.kr

빈티지삼촌

Page Load Speed

5.3 sec in total

First Response

780 ms

Resources Loaded

4.5 sec

Page Rendered

86 ms

vintageuncle.co.kr screenshot

About Website

Visit vintageuncle.co.kr now to see the best up-to-date Vintageuncle content for South Korea and also check out these interesting facts you probably never knew about vintageuncle.co.kr

남다른 퀄리티 구제, 구제의류. 구제 쇼핑몰, 미국, 유럽, 일본 해외 브랜드구제

Visit vintageuncle.co.kr

Key Findings

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

Performance Metrics

vintageuncle.co.kr performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

36/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

vintageuncle.co.kr

780 ms

vintageuncle.co.kr

1050 ms

jet.js

209 ms

css

22 ms

css

38 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 83% of them (62 requests) were addressed to the original Vintageuncle.co.kr, 8% (6 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Vintageuncle.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.3 kB (12%)

Content Size

408.0 kB

After Optimization

357.6 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-73%

Potential reduce by 48.1 kB

  • Original 65.5 kB
  • After minification 63.6 kB
  • After compression 17.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. 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.1 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 1.1 kB

  • Original 60.6 kB
  • After minification 59.5 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. Vintageuncle images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 281.9 kB
  • After minification 281.9 kB
  • After compression 280.8 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 54 (76%)

Requests Now

71

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vintageuncle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vintageuncle.co.kr

vintageuncle.co.kr

780 ms

vintageuncle.co.kr

vintageuncle.co.kr

1050 ms

jet.js

jet.js

209 ms

css

css

22 ms

css

css

38 ms

css

css

39 ms

css

css

41 ms

css

css

40 ms

css

css

41 ms

common.js

common.js

372 ms

cid.generate.js

cid.generate.js

560 ms

optimizer.php

optimizer.php

397 ms

optimizer_user.php

optimizer_user.php

401 ms

i18n.php

i18n.php

1505 ms

optimizer.php

optimizer.php

1351 ms

optimizer_user.php

optimizer_user.php

577 ms

txt_progress.gif

txt_progress.gif

188 ms

sns_01.gif

sns_01.gif

207 ms

sns_02.gif

sns_02.gif

217 ms

sns_03.gif

sns_03.gif

214 ms

sns_04.gif

sns_04.gif

385 ms

main_search.gif

main_search.gif

397 ms

main_logo.png

main_logo.png

406 ms

cate1_01.gif

cate1_01.gif

414 ms

cate1_02.gif

cate1_02.gif

573 ms

cate1_03.gif

cate1_03.gif

589 ms

cate1_04.gif

cate1_04.gif

600 ms

cate1_05.gif

cate1_05.gif

613 ms

cate1_06.gif

cate1_06.gif

761 ms

cate1_07.gif

cate1_07.gif

780 ms

cate1_08.gif

cate1_08.gif

792 ms

cate1_09.gif

cate1_09.gif

810 ms

cate1_10.gif

cate1_10.gif

951 ms

cate1_11.gif

cate1_11.gif

972 ms

cate1_12.gif

cate1_12.gif

985 ms

cate2_01.gif

cate2_01.gif

1009 ms

cate2_02.gif

cate2_02.gif

1178 ms

cate2_03.gif

cate2_03.gif

1178 ms

cate2_04.gif

cate2_04.gif

1178 ms

cate2_05.gif

cate2_05.gif

1179 ms

cate2_06.gif

cate2_06.gif

1207 ms

cate2_07.gif

cate2_07.gif

1309 ms

cate2_08.gif

cate2_08.gif

1327 ms

cate2_09.gif

cate2_09.gif

1344 ms

cate2_10.gif

cate2_10.gif

1354 ms

cate2_11.gif

cate2_11.gif

1371 ms

cate2_12.gif

cate2_12.gif

1404 ms

img_loading.gif

img_loading.gif

184 ms

cate2_13.gif

cate2_13.gif

1495 ms

cate2_14.gif

cate2_14.gif

1502 ms

mirae_log.js

mirae_log.js

719 ms

cate3_01.gif

cate3_01.gif

1471 ms

font

font

8 ms

font

font

85 ms

cate3_02.gif

cate3_02.gif

1351 ms

cate3_03.gif

cate3_03.gif

1360 ms

cate3_04.gif

cate3_04.gif

1393 ms

cate3_05.gif

cate3_05.gif

1470 ms

cate3_06.gif

cate3_06.gif

1320 ms

cate3_07.gif

cate3_07.gif

1324 ms

cate3_08.gif

cate3_08.gif

1333 ms

cate3_09.gif

cate3_09.gif

1344 ms

cate3_10.gif

cate3_10.gif

1231 ms

cate3_11.gif

cate3_11.gif

1284 ms

cate3_12.gif

cate3_12.gif

1293 ms

ws.jpg

ws.jpg

1296 ms

mirae_response_check.php

mirae_response_check.php

798 ms

bank_ico_01.gif

bank_ico_01.gif

1171 ms

bank_ico_02.gif

bank_ico_02.gif

1171 ms

bank_ico_03.gif

bank_ico_03.gif

1210 ms

bottom_ico.gif

bottom_ico.gif

1248 ms

c1.jpg

c1.jpg

1317 ms

page_top.gif

page_top.gif

1128 ms

main_search_bg.gif

main_search_bg.gif

1150 ms

company_bg.gif

company_bg.gif

1159 ms

Accessibility Review

vintageuncle.co.kr accessibility score

56

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.

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

High

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

vintageuncle.co.kr best practices score

58

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

vintageuncle.co.kr SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

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

vintageuncle.co.kr

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