3.2 sec in total
622 ms
2.4 sec
147 ms
Click here to check amazing Nintendo content for Taiwan. Otherwise, check out these important facts you probably never knew about nintendo.tw
任天堂官方網站(台灣)
Visit nintendo.twWe analyzed Nintendo.tw page load time and found that the first response time was 622 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
nintendo.tw performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value17.1 s
0/100
25%
Value8.7 s
16/100
10%
Value700 ms
43/100
30%
Value0
100/100
15%
Value13.1 s
12/100
10%
622 ms
477 ms
84 ms
86 ms
150 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 86% of them (55 requests) were addressed to the original Nintendo.tw, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (901 ms) belongs to the original domain Nintendo.tw.
Page size can be reduced by 545.1 kB (20%)
2.7 MB
2.1 MB
In fact, the total size of Nintendo.tw main page is 2.7 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 43.2 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 30.7 kB, which is 65% 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 43.2 kB or 92% of the original size.
Potential reduce by 61.8 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.
Potential reduce by 212.0 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 212.0 kB or 62% of the original size.
Potential reduce by 228.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. Nintendo.tw needs all CSS files to be minified and compressed as it can save up to 228.1 kB or 84% of the original size.
Number of requests can be reduced by 20 (33%)
60
40
The browser has sent 60 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 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
nintendo.tw
622 ms
www.nintendo.tw
477 ms
base.css
84 ms
top.css
86 ms
plugin.js
150 ms
run.js
89 ms
mWSCYwGkCkY
132 ms
copyright.htm
303 ms
ga.js
51 ms
nintendo_logo.gif
90 ms
index_middle_bg.gif
92 ms
index_game_bg.gif
86 ms
index_game_3ds_a.png
87 ms
index_game_3ds_over.gif
92 ms
index_game_wii_a.png
188 ms
index_game_wii_over.gif
190 ms
index_game_amiibo_a.png
188 ms
index_game_amiibo_over.gif
192 ms
index_topics_title.gif
191 ms
eshop_vcamap_banner.png
568 ms
index_topics_over_w.gif
259 ms
eshop_mocomoco_friends_banner.png
270 ms
eshop_rio2016_banner.png
314 ms
eshop_topics.png
265 ms
eshop_megaman_banner.png
341 ms
mhx_banner.png
427 ms
eshop_ironfall_banner.png
468 ms
eshop_zelda_majora.png
381 ms
eshop_pxz2_banner.png
396 ms
eshop_johnny_banner.png
559 ms
eshop_goonyan.png
464 ms
eshop_drmario_banner.png
484 ms
eshop_pad_m_banner.png
508 ms
eshop_pazuru_banner.png
547 ms
eshop_fossilfighter_banner.png
901 ms
eshop_codename_banner.png
600 ms
eshop_toy_banner.png
598 ms
pokemon_oras_banner.png
721 ms
eshop_attorney123_banner.png
832 ms
eshop_pokemonart_banner.png
670 ms
eshop_kir_dedede_banner.png
819 ms
yoshi_200x200px_1.png
696 ms
554G_topics_banner.png
821 ms
train_banner.png
795 ms
__utm.gif
14 ms
index_topics_navi.gif
725 ms
index_topics_pos.gif
800 ms
index_news_frame.gif
801 ms
index_news_line.gif
821 ms
index_news_ico.gif
817 ms
www-embed-player-vflZsBgOl.css
67 ms
www-embed-player.js
96 ms
new_icon.gif
735 ms
index_navi_frame.gif
778 ms
index_navi.gif
785 ms
fb_banner.jpg
795 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
42 ms
ad_status.js
50 ms
index_footer_bg.gif
772 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
100 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
111 ms
index_footer_ico.gif
737 ms
nintendo.css
737 ms
FB.gif
82 ms
nintendo.tw accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nintendo.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
nintendo.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nintendo.tw can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Nintendo.tw 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.
nintendo.tw
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: