2.9 sec in total
284 ms
2.4 sec
221 ms
Click here to check amazing Brainage content. Otherwise, check out these important facts you probably never knew about brainage.com
Find information, resources, and troubleshooting for Nintendo products from Nintendo Support.
Visit brainage.comWe analyzed Brainage.com page load time and found that the first response time was 284 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.
brainage.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value46.0 s
0/100
25%
Value30.9 s
0/100
10%
Value60,530 ms
0/100
30%
Value0.114
86/100
15%
Value74.0 s
0/100
10%
284 ms
321 ms
146 ms
150 ms
476 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Brainage.com, 30% (19 requests) were made to Media.nintendo.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (724 ms) relates to the external source Brainage.nintendo.com.
Page size can be reduced by 414.9 kB (29%)
1.4 MB
999.5 kB
In fact, the total size of Brainage.com main page is 1.4 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 14.0 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 14.0 kB or 73% of the original size.
Potential reduce by 135.3 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. Obviously, Brainage needs image optimization as it can save up to 135.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 203.8 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 203.8 kB or 72% of the original size.
Potential reduce by 61.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. Brainage.com needs all CSS files to be minified and compressed as it can save up to 61.8 kB or 85% of the original size.
Number of requests can be reduced by 23 (38%)
60
37
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brainage. 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 5 to 1 for CSS and as a result speed up the page load time.
brainage.nintendo.com
284 ms
main.css
321 ms
html5shiv.js
146 ms
html5shiv-printshiv.js
150 ms
jquery-1.8.3.min.js
476 ms
jquery.easing-1.3.js
219 ms
initialize.js
220 ms
modal.js
287 ms
carousel.js
295 ms
metrix.js
292 ms
pointroll.js
294 ms
css
23 ms
bg-main.jpg
147 ms
home-price.png
74 ms
hero-home.png
364 ms
qr-e-shop.png
76 ms
fearture-trailer-220x143.jpg
82 ms
fearture-intro-220x143.jpg
80 ms
fearture-gameplay-1-220x143.jpg
148 ms
fearture-gameplay-2-220x143.jpg
150 ms
box-art-290x193.jpg
151 ms
3ds-290x194.jpg
153 ms
video-boxart640x360.jpg
222 ms
qr-e-shop-large.png
220 ms
include.js
369 ms
base.css
101 ms
base.js
100 ms
s_code.js
102 ms
omniture-1.2.js
98 ms
globalnav.css
93 ms
globalnav.js
97 ms
footer.js
98 ms
swfobject.js
114 ms
player.js
112 ms
social.js
112 ms
btn-call-to-action.png
75 ms
logo-nintendo.png
31 ms
webfont.js
32 ms
logo-e-shop.png
76 ms
btn-arrows.png
79 ms
logo-game.png
77 ms
btn-nav-main.png
724 ms
btn-only-on-3ds.png
76 ms
frame-video-carousel.png
118 ms
bg-footer.png
147 ms
bg-footer-outer.png
147 ms
bg-footer-inner.png
150 ms
bg-vertical-rule.png
149 ms
newsletter_btn.png
6 ms
follow_facebook_solo.png
7 ms
follow_twitter_solo.png
6 ms
follow_youtube_solo.png
7 ms
ratingsymbol_e.png
7 ms
esrb_privacy.jpg
7 ms
btn_facebook.png
8 ms
bg-langnav-arrow.png
15 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
7 ms
css
13 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
5 ms
like.php
187 ms
s2505650506820
86 ms
qeKvIRsJabD.js
486 ms
LVx-xkvaJ0b.png
547 ms
brainage.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
brainage.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
brainage.com SEO score
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 uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brainage.com 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 Brainage.com 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.
brainage.com
Open Graph data is detected on the main page of Brainage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: