Tools & Wizards About Us
superhex.io screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

superhex.io

Superhex.io

Page Load Speed

1.5 sec in total

First Response

219 ms

Resources Loaded

1.2 sec

Page Rendered

115 ms

superhex.io screenshot

About Website

Welcome to superhex.io homepage info - get ready to check Superhex best content for United States right away, or after learning these important things about superhex.io

Conquer as much territory as possible, don't get hit and try to become the biggest of them all!

Visit superhex.io

Key Findings

We analyzed Superhex.io page load time and found that the first response time was 219 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

superhex.io performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

superhex.io

219 ms

super-hex.io

225 ms

mainloop.min.js

14 ms

pixi.min.js

32 ms

priority-queue.min.js

21 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Superhex.io, 59% (22 requests) were made to Super-hex.io and 8% (3 requests) were made to Static.criteo.net. The less responsive or slowest element that took the longest time to load (377 ms) relates to the external source Super-hex.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.5 kB (16%)

Content Size

799.1 kB

After Optimization

674.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Superhex.io main page is 799.1 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. 45% of websites need less resources to load. Images take 532.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 71.4 kB

  • Original 83.2 kB
  • After minification 67.4 kB
  • After compression 11.9 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 15.9 kB, which is 19% 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 71.4 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 23.3 kB

  • Original 532.6 kB
  • After minification 509.4 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. Superhex images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 29.9 kB

  • Original 183.2 kB
  • After minification 183.2 kB
  • After compression 153.3 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 29.9 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

25

  • AJAX
  • Images
  • JavaScript

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Superhex. 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

superhex.io

superhex.io

219 ms

super-hex.io

super-hex.io

225 ms

mainloop.min.js

mainloop.min.js

14 ms

pixi.min.js

pixi.min.js

32 ms

priority-queue.min.js

priority-queue.min.js

21 ms

game.min.js

game.min.js

23 ms

publishertag.js

publishertag.js

18 ms

js

js

104 ms

tag.min.js

tag.min.js

140 ms

254 ms

pixel.gif

pixel.gif

42 ms

widget.png

widget.png

117 ms

widgets.js

widgets.js

70 ms

sdk.js

sdk.js

66 ms

syncframe

syncframe

68 ms

disconnect.png

disconnect.png

188 ms

left-arrow.png

left-arrow.png

181 ms

right-arrow.png

right-arrow.png

191 ms

background4.png

background4.png

180 ms

fox.png

fox.png

186 ms

add-plus-button2.png

add-plus-button2.png

211 ms

friends.png

friends.png

190 ms

leave-party.png

leave-party.png

359 ms

logotext.png

logotext.png

194 ms

fox.png

fox.png

194 ms

chick.png

chick.png

364 ms

duck.png

duck.png

203 ms

cow.png

cow.png

206 ms

owls.png

owls.png

377 ms

pixel.gif

pixel.gif

45 ms

sdk.js

sdk.js

14 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

30 ms

settings

settings

100 ms

js

js

31 ms

texturepack2.json

texturepack2.json

90 ms

traine.png

traine.png

169 ms

texturepack2.png

texturepack2.png

178 ms

Accessibility Review

superhex.io accessibility score

64

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

superhex.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

Missing source maps for large first-party JavaScript

SEO Factors

superhex.io SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

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 Superhex.io 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 Superhex.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

superhex.io

Open Graph data is detected on the main page of Superhex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: