Tools & Wizards About Us
nintendo.co.kr screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nintendo.co.kr

Nintendo

Page Load Speed

4.7 sec in total

First Response

595 ms

Resources Loaded

3.9 sec

Page Rendered

214 ms

nintendo.co.kr screenshot

About Website

Click here to check amazing Nintendo content for South Korea. Otherwise, check out these important facts you probably never knew about nintendo.co.kr

콘솔 게임기 전문업체, Nintendo Switch, 게임 소프트웨어 등 제품 소개, 약도 제공.

Visit nintendo.co.kr

Key Findings

We analyzed Nintendo.co.kr page load time and found that the first response time was 595 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 65% of websites can load faster.

Performance Metrics

nintendo.co.kr performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value29.6 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.259

48/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

nintendo.co.kr

595 ms

www.nintendo.co.kr

34 ms

gtm.js

68 ms

owl.carousel.min.css

9 ms

owl.theme.default.min.css

21 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 78% of them (39 requests) were addressed to the original Nintendo.co.kr, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Cr.acecounter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cr.acecounter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.3 kB (5%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nintendo.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. 70% of websites need less resources to load. CSS take 891.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 20.3 kB

  • Original 26.7 kB
  • After minification 24.2 kB
  • After compression 6.4 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 20.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 102 B

  • Original 704.6 kB
  • After minification 704.5 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. Nintendo images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 50.2 kB

  • Original 340.9 kB
  • After minification 334.6 kB
  • After compression 290.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 50.2 kB or 15% of the original size.

CSS Optimization

-3%

Potential reduce by 27.7 kB

  • Original 891.2 kB
  • After minification 891.2 kB
  • After compression 863.5 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. Nintendo.co.kr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (64%)

Requests Now

47

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nintendo.co.kr

nintendo.co.kr

595 ms

www.nintendo.co.kr

www.nintendo.co.kr

34 ms

gtm.js

gtm.js

68 ms

owl.carousel.min.css

owl.carousel.min.css

9 ms

owl.theme.default.min.css

owl.theme.default.min.css

21 ms

common.css

common.css

18 ms

main.css

main.css

33 ms

amiibo.css

amiibo.css

22 ms

3ds.css

3ds.css

34 ms

software.css

software.css

24 ms

etc.css

etc.css

41 ms

main-purchase.css

main-purchase.css

40 ms

AceCounter_AW.js

AceCounter_AW.js

1120 ms

jquery-1.12.0.min.js

jquery-1.12.0.min.js

46 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

44 ms

owl.carousel.min.js

owl.carousel.min.js

47 ms

TweenMax.min.js

TweenMax.min.js

577 ms

jquery.ellipsis.min.js

jquery.ellipsis.min.js

44 ms

ui.js

ui.js

517 ms

js

js

95 ms

ai.2.min.js

ai.2.min.js

51 ms

svgpack.js

svgpack.js

625 ms

ncommon.js

ncommon.js

48 ms

top.js

top.js

49 ms

shared_imgpack.css

shared_imgpack.css

1110 ms

main.css

main.css

797 ms

js

js

37 ms

sendid

sendid

920 ms

css2

css2

147 ms

css2

css2

162 ms

right-stroke-red.svg

right-stroke-red.svg

34 ms

main_banner_eshop.gif

main_banner_eshop.gif

486 ms

banner_main_bottom01.jpg

banner_main_bottom01.jpg

511 ms

banner_main_bottom02.jpg

banner_main_bottom02.jpg

528 ms

banner_main_bottom04.jpg

banner_main_bottom04.jpg

496 ms

banner_main_bottom05.jpg

banner_main_bottom05.jpg

489 ms

banner_main_bottom06.jpg

banner_main_bottom06.jpg

496 ms

unit_icon.png

unit_icon.png

1009 ms

banner_arrow.png

banner_arrow.png

1006 ms

btn_close_layer_popup.gif

btn_close_layer_popup.gif

1024 ms

banner_main_bottom03.jpg

banner_main_bottom03.jpg

976 ms

gtp13.acecounter.com

gtp13.acecounter.com

1103 ms

AceCounter_AW.js

AceCounter_AW.js

805 ms

gtp13.acecounter.com

gtp13.acecounter.com

597 ms

fe9670547d20a5209f8ad7c7b748dd2b.jpg

fe9670547d20a5209f8ad7c7b748dd2b.jpg

932 ms

a270093fd21f6abcdacf16d7723d8da1.jpg

a270093fd21f6abcdacf16d7723d8da1.jpg

874 ms

a270093fd21f6abcdacf16d7723d8da1.jpg

a270093fd21f6abcdacf16d7723d8da1.jpg

965 ms

a270093fd21f6abcdacf16d7723d8da1.jpg

a270093fd21f6abcdacf16d7723d8da1.jpg

974 ms

a270093fd21f6abcdacf16d7723d8da1.jpg

a270093fd21f6abcdacf16d7723d8da1.jpg

917 ms

a270093fd21f6abcdacf16d7723d8da1.jpg

a270093fd21f6abcdacf16d7723d8da1.jpg

899 ms

Accessibility Review

nintendo.co.kr accessibility score

86

Accessibility Issues

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.

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

nintendo.co.kr best practices score

83

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

Page has valid source maps

SEO Factors

nintendo.co.kr SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

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

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

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

nintendo.co.kr

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