Access hayannamoo.com. 하얀나무

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.004

2/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

hayannamoo.com

1404 ms

reset.css

369 ms

common.css

372 ms

layer.css

382 ms

layout.css

387 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 35% of them (44 requests) were addressed to the original Hayannamoo.com, 34% (43 requests) were made to Godomall.speedycdn.net and 29% (36 requests) were made to Cdn-pro-web-211-100.cdn-nhncommerce.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Cdn-pro-web-211-100.cdn-nhncommerce.com.

Content Size

7.3 MB

After Optimization

1.7 MB

In fact, the total size of Hayannamoo.com main page is 7.3 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. 70% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 123.0 kB

Original 137.7 kB
After minification 91.9 kB
After compression 14.7 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. This page needs HTML code to be minified as it can gain 45.9 kB, which is 33% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 123.0 kB or 89% of the original size.

Image Optimization

-77%

Potential reduce by 5.4 MB

Original 7.0 MB
After minification 1.6 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. Obviously, Hayannamoo needs image optimization as it can save up to 5.4 MB or 77% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 19.7 kB

Original 123.9 kB
After minification 123.8 kB
After compression 104.2 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 19.7 kB or 16% of the original size.

CSS Optimization

-39%

Potential reduce by 18.2 kB

Original 46.1 kB
After minification 43.6 kB
After compression 27.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Hayannamoo.com needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 39% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Image elements do not have [alt] attributes

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

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

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

High

Page is blocked from indexing

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

KO
Language Claimed

N/A
Encoding

UTF-8

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

hayannamoo.com

Open Graph data is detected on the main page of Hayannamoo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

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

hayannamoo.com

reset.css

common.css

layer.css

layout.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

hayannamoo.com

reset.css

common.css

layer.css

layout.css

list.css

button.css

main.css

chosen.css

custom.css

gd_gettext.js

jquery.min.js

underscore-min.js

jquery.validate.min.js

additional-methods.min.js

numeral.min.js

accounting.min.js

money.min.js

chosen.jquery.min.js

placeholders.jquery.min.js

clipboard.min.js

jquery.vticker.js

gd_ui.js

gd_common.js

gd_visit.js

jquery.cookie.js

wcslog.js

naverCommonInflowScript.js

slick.js

gd_multi_select_box.js

e5c2e11ebd34bfad91451c5d618f39eb_75256.png

868_main_030.jpg

escrow_60x60_color.png

839_main_010.jpg

744_main_028.jpg

81_main_046.jpg

773_main_061.jpg

772_main_029.jpg

293_main_056.jpg

302_main_076.jpg

853_main_037.jpg

101_main_095.jpg

596_main_097.jpg