Access yellostory.co.kr. REVU Corporation

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%

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.

Content Size

726.5 kB

After Optimization

241.5 kB

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 Now

After Optimization

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.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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

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: