Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

jooen.com

우아하고 트렌디한 데일리룩, 쥬엔

Page Load Speed

15.9 sec in total

First Response

2.5 sec

Resources Loaded

11.7 sec

Page Rendered

1.7 sec

jooen.com screenshot

About Website

Visit jooen.com now to see the best up-to-date Jooen content for South Korea and also check out these interesting facts you probably never knew about jooen.com

우아하고 트렌디한, 명품스타일 여성의류 쇼핑몰, 원피스, 티셔츠, 가디건, 스커트 등 온라인 판매.

Visit jooen.com

Key Findings

We analyzed Jooen.com page load time and found that the first response time was 2.5 sec and then it took 13.4 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

jooen.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.531

14/100

15%

TTI (Time to Interactive)

Value39.8 s

0/100

10%

Network Requests Diagram

jooen.com

2467 ms

common.js

401 ms

cid.generate.js

403 ms

wcslog.js

7 ms

optimizer.php

623 ms

Our browser made a total of 212 requests to load all elements on the main page. We found that 87% of them (184 requests) were addressed to the original Jooen.com, 2% (4 requests) were made to Img.echosting.cafe24.com and 1% (3 requests) were made to Web226.cmc.cafe24.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Jooen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 398.2 kB (15%)

Content Size

2.6 MB

After Optimization

2.2 MB

In fact, the total size of Jooen.com main page is 2.6 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. 85% 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 260.0 kB

  • Original 290.5 kB
  • After minification 265.6 kB
  • After compression 30.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 260.0 kB or 90% of the original size.

Image Optimization

-5%

Potential reduce by 110.6 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Jooen images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 27.6 kB

  • Original 53.3 kB
  • After minification 50.0 kB
  • After compression 25.7 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 27.6 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (15%)

Requests Now

207

After Optimization

176

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

Accessibility Review

jooen.com accessibility score

76

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

Links do not have a discernible name

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

jooen.com best practices score

67

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

SEO Factors

jooen.com SEO score

85

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 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 Jooen.com 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 Jooen.com 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

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