Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 85% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

nindb.net

NinDB: The Unofficial Nintendo Archive

Page Load Speed

1.2 sec in total

First Response

258 ms

Resources Loaded

746 ms

Page Rendered

235 ms

nindb.net screenshot

About Website

Click here to check amazing NinDB content for United States. Otherwise, check out these important facts you probably never knew about nindb.net

The original unofficial reference for every Nintendo game ever made.

Visit nindb.net

Key Findings

We analyzed Nindb.net page load time and found that the first response time was 258 ms and then it took 981 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

nindb.net performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

nindb.net

258 ms

new.css

126 ms

screenshot.jpg

249 ms

screenshot.jpg

487 ms

20150306-splatoon.png

188 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 80% of them (12 requests) were addressed to the original Nindb.net, 13% (2 requests) were made to Google-analytics.com and 7% (1 request) were made to Twitter-badges.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (487 ms) belongs to the original domain Nindb.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.5 kB (9%)

Content Size

396.6 kB

After Optimization

361.1 kB

In fact, the total size of Nindb.net main page is 396.6 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. 15% of websites need less resources to load. Images take 352.7 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 5.3 kB

  • Original 8.4 kB
  • After minification 8.1 kB
  • After compression 3.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 5.3 kB or 63% of the original size.

Image Optimization

-4%

Potential reduce by 15.8 kB

  • Original 352.7 kB
  • After minification 336.9 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. NinDB images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-79%

Potential reduce by 14.4 kB

  • Original 18.3 kB
  • After minification 16.6 kB
  • After compression 3.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. Nindb.net needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NinDB. According to our analytics all requests are already optimized.

Accessibility Review

nindb.net accessibility score

94

Accessibility Issues

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

nindb.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

nindb.net SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nindb.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nindb.net 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 NinDB. 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: