Access m.en.ojane.co.kr. 오나홀

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.566

12/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

m.en.ojane.co.kr

1506 ms

optimizer.php

479 ms

cid.generate.js

414 ms

wcslog.js

186 ms

optimizer.php

216 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 25% of them (14 requests) were addressed to the original M.en.ojane.co.kr, 35% (19 requests) were made to Img.echosting.cafe24.com and 31% (17 requests) were made to Cafe24img.poxo.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Cafe24img.poxo.com.

Content Size

2.9 MB

After Optimization

2.8 MB

In fact, the total size of M.en.ojane.co.kr 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. 40% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 61.3 kB

Original 81.1 kB
After minification 77.0 kB
After compression 19.9 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 61.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 2.9 kB

Original 2.5 MB
After minification 2.5 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. M En Ojane images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 20.8 kB

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

Requests Now

After Optimization

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M En Ojane. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 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 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 items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

Missing source maps for large first-party JavaScript

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

KO
Encoding

UTF-8

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

Report Summary

Performance

Accessibility

Best Practices

SEO

오나홀

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

m.en.ojane.co.kr

optimizer.php

cid.generate.js

wcslog.js

optimizer.php

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

{{url}}

Accessibility Review

Accessibility Issues

Best Practices

Areas of Improvement

SEO Factors

Search Engine Optimization Advices

Language and Encoding

Language Detected

Language Claimed

Encoding

Social Sharing Optimization

{{og_title}}