Tools & Wizards About Us
next.co.kr screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

next.co.kr

Next Official Site: Online Fashion, Kids Clothes & Homeware

Page Load Speed

4.1 sec in total

First Response

14 ms

Resources Loaded

3.4 sec

Page Rendered

690 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 14 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

next.co.kr performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.1 s

0/100

25%

SI (Speed Index)

Value29.1 s

0/100

10%

TBT (Total Blocking Time)

Value64,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value84.1 s

0/100

10%

Network Requests Diagram

14 ms

995 ms

Fonts.min.css

152 ms

core.min.js

312 ms

gtm.js

98 ms

Our browser made a total of 91 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, 7% (6 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Static.queue-it.net. The less responsive or slowest element that took the longest time to load (995 ms) relates to the external source Nextdirect.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.4 kB (71%)

Content Size

569.4 kB

After Optimization

163.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Next.co.kr main page is 569.4 kB. 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. HTML takes 363.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 309.1 kB

  • Original 363.2 kB
  • After minification 359.8 kB
  • After compression 54.1 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 309.1 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

-42%

Potential reduce by 74.2 kB

  • Original 174.8 kB
  • After minification 157.1 kB
  • After compression 100.5 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 74.2 kB or 42% of the original size.

CSS Optimization

-77%

Potential reduce by 23.0 kB

  • Original 29.8 kB
  • After minification 28.0 kB
  • After compression 6.8 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.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (74%)

Requests Now

84

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 84 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 43 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

14 ms

995 ms

Fonts.min.css

Fonts.min.css

152 ms

core.min.js

core.min.js

312 ms

gtm.js

gtm.js

98 ms

queueclient.min.js

queueclient.min.js

102 ms

queueconfigloader.js

queueconfigloader.js

102 ms

GAFirebase.js

GAFirebase.js

181 ms

userConsent

userConsent

109 ms

preloadwithmodernisedheader.css

preloadwithmodernisedheader.css

165 ms

storefronts.css

storefronts.css

533 ms

UI_plugins.css

UI_plugins.css

520 ms

CompetitionStorefront.css

CompetitionStorefront.css

274 ms

NextCreditPopup.css

NextCreditPopup.css

528 ms

body.css

body.css

208 ms

head.js

head.js

523 ms

preabdependencies.js

preabdependencies.js

288 ms

prerender.js

prerender.js

302 ms

lcAUWsB

lcAUWsB

498 ms

jquery.js

jquery.js

497 ms

jscontent

jscontent

504 ms

jssettings

jssettings

501 ms

libraries.js

libraries.js

499 ms

platmodheadercommon.js

platmodheadercommon.js

501 ms

TotalPlatformSuperLightHelper.js

TotalPlatformSuperLightHelper.js

569 ms

CountryRedirect.js

CountryRedirect.js

509 ms

postrender.js

postrender.js

503 ms

modernisedHeaderfavourites

modernisedHeaderfavourites

503 ms

UI_plugins.js

UI_plugins.js

506 ms

formValidation.js

formValidation.js

544 ms

storefronts.js

storefronts.js

683 ms

jquery.browser.js

jquery.browser.js

676 ms

StorefrontIERedirector.js

StorefrontIERedirector.js

582 ms

react.production.min.js

react.production.min.js

508 ms

react-dom.production.min.js

react-dom.production.min.js

520 ms

runtime~main.3.7.6.js

runtime~main.3.7.6.js

544 ms

8.3.7.6.chunk.js

8.3.7.6.chunk.js

558 ms

main.3.7.6.chunk.js

main.3.7.6.chunk.js

591 ms

0.3.7.6.chunk.js

0.3.7.6.chunk.js

620 ms

2.3.7.6.chunk.js

2.3.7.6.chunk.js

589 ms

1.3.7.6.chunk.js

1.3.7.6.chunk.js

551 ms

default-header.3.7.6.chunk.js

default-header.3.7.6.chunk.js

587 ms

2.2.2.1.chunk.js

2.2.2.1.chunk.js

546 ms

main.2.2.1.chunk.js

main.2.2.1.chunk.js

532 ms

queueclientConfig.js

queueclientConfig.js

76 ms

izh0xcr.css

izh0xcr.css

174 ms

1665257325631

1665257325631

366 ms

p.css

p.css

61 ms

new-next-white-logo.svg

new-next-white-logo.svg

71 ms

search.svg

search.svg

71 ms

search-input-button.svg

search-input-button.svg

68 ms

next_my-account.svg

next_my-account.svg

71 ms

next_my-account_desktop.svg

next_my-account_desktop.svg

81 ms

favourites-inactive.svg

favourites-inactive.svg

84 ms

shopping-bag.svg

shopping-bag.svg

115 ms

kr.png

kr.png

120 ms

lipsy-data.png

lipsy-data.png

82 ms

adidas-data.png

adidas-data.png

81 ms

joules-data.jpg

joules-data.jpg

116 ms

bakerbytedbaker-data.png

bakerbytedbaker-data.png

117 ms

monsoon-data.png

monsoon-data.png

116 ms

boden-data.png

boden-data.png

121 ms

adenanais-data.png

adenanais-data.png

121 ms

tommyhilfiger-data.png

tommyhilfiger-data.png

118 ms

fatface-data.png

fatface-data.png

119 ms

roman-data.png

roman-data.png

121 ms

own-denim-data.jpg

own-denim-data.jpg

122 ms

hp-banner-order-tracking-eng-dt-data.jpg

hp-banner-order-tracking-eng-dt-data.jpg

123 ms

loader.gif

loader.gif

312 ms

icon-social-facebook.svg

icon-social-facebook.svg

125 ms

icon-social-twitter.svg

icon-social-twitter.svg

151 ms

icon-social-instagram.svg

icon-social-instagram.svg

152 ms

icon-social-pinterest.svg

icon-social-pinterest.svg

156 ms

icon-social-youtube.svg

icon-social-youtube.svg

155 ms

myaccount.svg

myaccount.svg

175 ms

languageselector.svg

languageselector.svg

176 ms

chevron.svg

chevron.svg

172 ms

AzoSans-Regular-webfont.woff

AzoSans-Regular-webfont.woff

54 ms

AzoSans-Light-webfont.woff

AzoSans-Light-webfont.woff

54 ms

AzoSans-Thin-webfont.woff

AzoSans-Thin-webfont.woff

184 ms

AzoSans-Medium-webfont.woff

AzoSans-Medium-webfont.woff

182 ms

gtm.js

gtm.js

181 ms

gtm.js

gtm.js

32 ms

gtm.js

gtm.js

97 ms

gtm.js

gtm.js

85 ms

gtm.js

gtm.js

178 ms

gtm.js

gtm.js

179 ms

own-hp-dt-3.jpg

own-hp-dt-3.jpg

72 ms

PlayfairDisplay-Regular.woff

PlayfairDisplay-Regular.woff

169 ms

girls-coats-data.jpg

girls-coats-data.jpg

170 ms

boys-coats-data.jpg

boys-coats-data.jpg

167 ms

Accessibility Review

next.co.kr accessibility score

77

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

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

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

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

93

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

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

    EN

  • 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. Our service has detected that English is used on the page, and it matches the claimed language. 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

next.co.kr

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: