Access monostory.com. 모노스토리 : 일상의 행복 모노스토리가 함께합니다~~♡

monostory.com screenshot

44

Performance

Renders faster than
63% of other websites
89

Accessibility

Visual factors better than
that of 71% of websites
67

Best Practices

More advanced features
available than in
24% of websites
92

SEO

Google-friendlier than
74% of websites

First Response

1 sec

Resources Loaded

6.8 sec

Page Rendered

3 sec

monostory.com screenshot

About Website

Click here to check amazing Monostory content. Otherwise, check out these important facts you probably never knew about monostory.com

모노스토리 : 일상의 행복 모노스토리가 함께합니다~~♡

Visit monostory.com

Key Findings

We analyzed Monostory.com page load time and found that the first response time was 1 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

monostory.com

1047 ms

product_list.js

605 ms

wcslog.js

55 ms

bookmark.js

395 ms

design_func.js

397 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 94% of them (143 requests) were addressed to the original Monostory.com, 2% (3 requests) were made to Web6.logcounter.com and 1% (2 requests) were made to Serial6.logcounter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Monostory.com.

Content Size

2.9 MB

After Optimization

2.5 MB

In fact, the total size of Monostory.com main page is 2.9 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. 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 182.4 kB

Original 206.6 kB
After minification 195.5 kB
After compression 24.2 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 182.4 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 122.1 kB

Original 2.5 MB
After minification 2.4 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. Monostory images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 77.2 kB

Original 111.8 kB
After minification 95.0 kB
After compression 34.6 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 77.2 kB or 69% of the original size.

Requests Now

151

After Optimization

126

The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Monostory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

N/A
Encoding

EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Monostory.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Monostory.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

monostory.com

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