Tools & Wizards About Us
yellostory.co.kr screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yellostory.co.kr

REVU Corporation

Page Load Speed

4.8 sec in total

First Response

386 ms

Resources Loaded

4 sec

Page Rendered

405 ms

yellostory.co.kr screenshot

About Website

Click here to check amazing Yellostory content for South Korea. Otherwise, check out these important facts you probably never knew about yellostory.co.kr

레뷰코퍼레이션은 한국 및 아시아 6개국에서 서비스 중인 글로벌 인플루언서 플랫폼 브랜드 'REVU'를 통해 인플루언서와 고객의 비즈니스를 연결하여 가치를 창출하는 국내 최대 규모의 인플루언서 비즈니스 전문 기업입니다.

Visit yellostory.co.kr

Key Findings

We analyzed Yellostory.co.kr page load time and found that the first response time was 386 ms and then it took 4.4 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

yellostory.co.kr performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value195.3 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

corp.revu.net

386 ms

corp.revu.net

1249 ms

pretendard.css

32 ms

maps.js

1588 ms

e77c20fa4cdf501f.css

524 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yellostory.co.kr, 26% (12 requests) were made to Fonts.gstatic.com and 21% (10 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source D1uuuninuo43kf.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 485.0 kB (67%)

Content Size

726.5 kB

After Optimization

241.5 kB

  • HTML
  • JavaScript

In fact, the total size of Yellostory.co.kr main page is 726.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. Only a small number of websites need less resources to load. HTML takes 638.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 485.0 kB

  • Original 638.8 kB
  • After minification 638.7 kB
  • After compression 153.8 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 485.0 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 87.8 kB
  • After minification 87.8 kB
  • After compression 87.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 14 (78%)

Requests Now

18

After Optimization

4

  • JavaScript
  • CSS

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

Network Requests Diagram

corp.revu.net

corp.revu.net

386 ms

corp.revu.net

corp.revu.net

1249 ms

pretendard.css

pretendard.css

32 ms

maps.js

maps.js

1588 ms

e77c20fa4cdf501f.css

e77c20fa4cdf501f.css

524 ms

2a36ea7255127547.css

2a36ea7255127547.css

557 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

786 ms

webpack-38cee4c0e358b1a3.js

webpack-38cee4c0e358b1a3.js

555 ms

framework-7751730b10fa0f74.js

framework-7751730b10fa0f74.js

1120 ms

main-6d33b1c7e8583eab.js

main-6d33b1c7e8583eab.js

759 ms

_app-107aff716cf69a9b.js

_app-107aff716cf69a9b.js

760 ms

204-95ec43d6574c7213.js

204-95ec43d6574c7213.js

759 ms

959-5acbe57423dfce65.js

959-5acbe57423dfce65.js

769 ms

764-ea987b2bbe47d7b5.js

764-ea987b2bbe47d7b5.js

1150 ms

998-700e1422a69d3ccd.js

998-700e1422a69d3ccd.js

1118 ms

176-cdfc28af124894e5.js

176-cdfc28af124894e5.js

1422 ms

354-66e8906f085aac31.js

354-66e8906f085aac31.js

1150 ms

index-c0db08f23cda9cc6.js

index-c0db08f23cda9cc6.js

1116 ms

_buildManifest.js

_buildManifest.js

1426 ms

_ssgManifest.js

_ssgManifest.js

1427 ms

graph-img-1.png

graph-img-1.png

803 ms

graph-img-2.png

graph-img-2.png

1634 ms

w-vietnam-icon@3x.png

w-vietnam-icon@3x.png

1639 ms

w-taiwan-icon@3x.png

w-taiwan-icon@3x.png

1648 ms

w-cmd-m-btn-korea@3x.png

w-cmd-m-btn-korea@3x.png

1637 ms

w-indonesia-icon@3x.png

w-indonesia-icon@3x.png

1675 ms

Pretendard-Bold.woff

Pretendard-Bold.woff

23 ms

Pretendard-ExtraBold.woff

Pretendard-ExtraBold.woff

49 ms

Pretendard-Black.woff

Pretendard-Black.woff

134 ms

Pretendard-SemiBold.woff

Pretendard-SemiBold.woff

142 ms

Pretendard-Medium.woff

Pretendard-Medium.woff

138 ms

Pretendard-Regular.woff

Pretendard-Regular.woff

135 ms

Pretendard-Light.woff

Pretendard-Light.woff

136 ms

Pretendard-ExtraLight.woff

Pretendard-ExtraLight.woff

139 ms

Pretendard-Thin.woff

Pretendard-Thin.woff

141 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01eLc.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01eLc.woff

144 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1eLc.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1eLc.woff

405 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgyeLc.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgyeLc.woff

502 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoyeLc.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoyeLc.woff

663 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQyeLc.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQyeLc.woff

510 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozeLc.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozeLc.woff

509 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

397 ms

KFOlCnqEu92Fr1MmYUtvAA.woff

KFOlCnqEu92Fr1MmYUtvAA.woff

399 ms

KFOlCnqEu92Fr1MmEU9vAA.woff

KFOlCnqEu92Fr1MmEU9vAA.woff

399 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

400 ms

KFOlCnqEu92Fr1MmSU5vAA.woff

KFOlCnqEu92Fr1MmSU5vAA.woff

465 ms

KFOkCnqEu92Fr1MmgWxM.woff

KFOkCnqEu92Fr1MmgWxM.woff

465 ms

Accessibility Review

yellostory.co.kr accessibility score

91

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

yellostory.co.kr best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yellostory.co.kr SEO score

92

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

    KO

  • Encoding

    UTF-8

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

yellostory.co.kr

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