Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

Page Load Speed

3 sec in total

First Response

12 ms

Resources Loaded

2.5 sec

Page Rendered

506 ms

next.co.kr screenshot

About Website

Click here to check amazing Next content. Otherwise, check out these important facts you probably never knew about next.co.kr

Shop the latest women's, men's and children's fashion plus homeware, beauty and more. Next day delivery and free returns available. Shop now!

Visit next.co.kr

Key Findings

We analyzed Next.co.kr page load time and found that the first response time was 12 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

next.co.kr performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value4,000 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

Network Requests Diagram

12 ms

862 ms

Fonts.min.css

109 ms

gtm.js

33 ms

queueclient.min.js

32 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Next.co.kr, 6% (6 requests) were made to Use.typekit.net and 2% (2 requests) were made to Static.queue-it.net. The less responsive or slowest element that took the longest time to load (862 ms) relates to the external source Nextdirect.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (65%)

Content Size

2.0 MB

After Optimization

683.9 kB

In fact, the total size of Next.co.kr main page is 2.0 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. 75% 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. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 312.8 kB

  • Original 367.5 kB
  • After minification 363.9 kB
  • After compression 54.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. 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 312.8 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.6 kB
  • After minification 1.6 kB

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. Next images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 943.0 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 620.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 943.0 kB or 60% of the original size.

CSS Optimization

-77%

Potential reduce by 23.6 kB

  • Original 30.6 kB
  • After minification 24.2 kB
  • After compression 6.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. Next.co.kr needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (80%)

Requests Now

88

After Optimization

18

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

Accessibility Review

next.co.kr accessibility score

85

Accessibility Issues

ARIA

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.

Impact

Issue

High

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

next.co.kr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

next.co.kr SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Next.co.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Next.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 Next. 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: