1.7 sec in total
120 ms
907 ms
626 ms
Click here to check amazing Tetris content. Otherwise, check out these important facts you probably never knew about tetris.org
Visit the official Tetris® website to play FREE online Tetris, get game and merchandise updates, and read about global Tetris events.
Visit tetris.orgWe analyzed Tetris.org page load time and found that the first response time was 120 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
tetris.org performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value23.7 s
0/100
25%
Value14.5 s
1/100
10%
Value11,610 ms
0/100
30%
Value0.033
100/100
15%
Value24.6 s
0/100
10%
120 ms
56 ms
73 ms
216 ms
65 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tetris.org, 81% (50 requests) were made to Tetris.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (534 ms) relates to the external source Cc.cdn.civiccomputing.com.
Page size can be reduced by 112.1 kB (46%)
244.2 kB
132.1 kB
In fact, the total size of Tetris.org main page is 244.2 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. Javascripts take 167.8 kB which makes up the majority of the site volume.
Potential reduce by 52.5 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 7.9 kB, which is 12% 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 52.5 kB or 80% of the original size.
Potential reduce by 59.6 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 59.6 kB or 36% of the original size.
Potential reduce by 0 B
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. Tetris.org has all CSS files already compressed.
Number of requests can be reduced by 14 (67%)
21
7
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tetris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
tetris.org
120 ms
style.css
56 ms
app-built.js
73 ms
js
216 ms
gpt.js
65 ms
widgets.js
51 ms
cookieControl-8.x.min.js
534 ms
addthis_widget.js
405 ms
analytics.js
192 ms
tetriminos-banner.png
294 ms
project-logo.png
316 ms
tetris-appletv-nowstreaming.jpg
315 ms
e60-playnow-feature.jpg
316 ms
tetris-mobile-hero-1560x639.jpg
313 ms
spreadshirtxtetris.jpg
314 ms
header-website.jpg
315 ms
untitled-design-22-.png
327 ms
tetris-podcast-688x387-v2_688x387.jpg
320 ms
spacer-16x9.png
323 ms
dt-tetris-688x387_688x387.jpg
321 ms
tec-ps5-tetriscom-688x387_688x387.png
322 ms
tetris-movie-banner-template-688x387_688x387.jpg
320 ms
play-button.svg
423 ms
tetris-game-boy-nso-688x387_688x387.jpg
326 ms
slide5_688x387.jpeg
325 ms
tgm-blogroll-688x387_688x387.jpg
327 ms
kura2-blogroll-688x387-1-688x387_688x387.png
420 ms
madlab-blogroll-688x387_688x387.jpg
420 ms
t99-maximuscup30-688x387_688x387.jpg
423 ms
tec-lrg-688x387-v2_688x387.jpg
418 ms
t99-maximuscup29-688x387_688x387.jpg
420 ms
nyt-022522-blogroll-688x387_688x387.png
436 ms
blogroll-688x387_688x387.png
437 ms
footer-tetriminos.png
437 ms
t99-maximuscup28-688x387_688x387.jpg
434 ms
t99-maximuscup27-688x387_688x387.jpg
433 ms
kura-sushi-v2-launch-688x387_688x387.jpg
439 ms
feelin-lucky-sweepstakes-header_688x387.jpg
445 ms
19-01-16-tetris-theme-article_688x387.jpg
444 ms
tetris-holiday-gift-feature_688x387.jpg
442 ms
19-04-18-look-a-like-day-rectangular-v2_688x387.jpg
441 ms
footer-pattern.png
444 ms
footer-logo.png
469 ms
gc-emblem-black.svg
470 ms
pubads_impl.js
243 ms
MuseoSans500.otf
371 ms
collect
31 ms
MuseoSans100.otf
186 ms
Museo700.otf
166 ms
nucleo-mini.woff
234 ms
nucleo-outline.woff
253 ms
nucleo-glyph.woff
226 ms
tetrimino-orange.svg
233 ms
collect
127 ms
tetrimino-blue.svg
164 ms
tetrimino-cyan.svg
162 ms
tetrimino-purple.svg
162 ms
tetrimino-green.svg
163 ms
tetrimino-red.svg
193 ms
tetrimino-yellow.svg
191 ms
ga-audiences
75 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
203 ms
tetris.org 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
tetris.org 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
Page has valid source maps
tetris.org 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 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 Tetris.org 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 Tetris.org 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.
tetris.org
Open Graph description is not detected on the main page of Tetris. 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: