Tools & Wizards About Us
stanga.io screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

stanga.io

Page Load Speed

741 ms in total

First Response

73 ms

Resources Loaded

609 ms

Page Rendered

59 ms

stanga.io screenshot

About Website

Click here to check amazing Stanga content. Otherwise, check out these important facts you probably never knew about stanga.io

Visit stanga.io

Key Findings

We analyzed Stanga.io page load time and found that the first response time was 73 ms and then it took 668 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

stanga.io performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.74

6/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

www.tenko.games

73 ms

minified.js

27 ms

focus-within-polyfill.js

23 ms

polyfill.min.js

23 ms

thunderbolt-commons.adaa8d77.bundle.min.js

80 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Stanga.io, 34% (12 requests) were made to Sentry-next.wixpress.com and 20% (7 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (322 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.8 kB (40%)

Content Size

742.8 kB

After Optimization

448.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Stanga.io main page is 742.8 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. 40% of websites need less resources to load. HTML takes 304.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 229.4 kB

  • Original 304.1 kB
  • After minification 302.4 kB
  • After compression 74.7 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 229.4 kB or 75% of the original size.

Image Optimization

-13%

Potential reduce by 17.3 kB

  • Original 135.2 kB
  • After minification 117.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. Obviously, Stanga needs image optimization as it can save up to 17.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.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 303.5 kB
  • After minification 303.5 kB
  • After compression 255.4 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 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tenko.games

www.tenko.games

73 ms

minified.js

minified.js

27 ms

focus-within-polyfill.js

focus-within-polyfill.js

23 ms

polyfill.min.js

polyfill.min.js

23 ms

thunderbolt-commons.adaa8d77.bundle.min.js

thunderbolt-commons.adaa8d77.bundle.min.js

80 ms

main.213217e1.bundle.min.js

main.213217e1.bundle.min.js

100 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

80 ms

lodash.min.js

lodash.min.js

81 ms

react.production.min.js

react.production.min.js

82 ms

react-dom.production.min.js

react-dom.production.min.js

81 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

97 ms

tenko_logo.png

tenko_logo.png

289 ms

bundle.min.js

bundle.min.js

64 ms

IMG_20210215_140821.jpg

IMG_20210215_140821.jpg

256 ms

unnamed.jpg

unnamed.jpg

204 ms

store_icon.png

store_icon.png

248 ms

game_logo_Website.jpg

game_logo_Website.jpg

322 ms

Two%20Computer%20Screens.jpg

Two%20Computer%20Screens.jpg

140 ms

Startup.jpg

Startup.jpg

234 ms

120 ms

117 ms

111 ms

107 ms

112 ms

109 ms

131 ms

130 ms

129 ms

130 ms

127 ms

125 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

31 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

stanga.io accessibility score

97

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.

Best Practices

stanga.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

stanga.io SEO score

93

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanga.io can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Stanga.io 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

stanga.io

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