Access jw.co.kr. (주)중원

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.247

1/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

jw.co.kr

873 ms

common.css

224 ms

css2

38 ms

css2

52 ms

jquery-1.7.2.min.js

802 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 73% of them (45 requests) were addressed to the original Jw.co.kr, 24% (15 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Jw.co.kr.

Content Size

2.9 MB

After Optimization

2.7 MB

In fact, the total size of Jw.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. Only a small number of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 27.0 kB

Original 34.7 kB
After minification 28.2 kB
After compression 7.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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 19% 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 27.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 27.8 kB

Original 2.6 MB
After minification 2.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. Jw images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 122.6 kB

Original 212.7 kB
After minification 207.6 kB
After compression 90.1 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 122.6 kB or 58% of the original size.

CSS Optimization

-52%

Potential reduce by 14.2 kB

Original 27.3 kB
After minification 23.4 kB
After compression 13.1 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. Jw.co.kr needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 52% of the original size.

Requests Now

After Optimization

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jw. 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 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

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 Jw.co.kr 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 Jw.co.kr 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

jw.co.kr

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

jw.co.kr

common.css

css2

css2

jquery-1.7.2.min.js

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

jw.co.kr

common.css

css2

css2

jquery-1.7.2.min.js

lazyload.min.js

flash.js

rightbanner.js

bookmark.js

main.css

unit_aos.css

unit_aos.js

shopRbanner.html

header.1.css

header.1.js

menu.1.css

slick.css

slick.js

footer.1.css

main.js

wishlist.js

detailpage.js

product_list.js

jquery.language.js

basket_send.js

jquery-datepicker-ko.js

referer_cookie.js

cookie.js

product_rollover_image.js

newlogo.png

Triangle_over.png

1920x960_1.jpg

1920x960_2.jpg

1920x960_3.jpg

our_contact1.png

our_contact_arr.png

our_contact2.png

our_contact3.png

JW_logo_B-01.png

JW_logo_W-06_footer.png

scroll.css

bg_logo_pc.png

test.jpg