Access hexbug.com. HEXBUG Micro Robotic Creatures

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value82.5 s

0/100

25%

SI (Speed Index)

Value43.2 s

0/100

10%

TBT (Total Blocking Time)

Value8,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.895

3/100

15%

TTI (Time to Interactive)

Value74.4 s

0/100

10%

hexbug.com

50 ms

www.hexbug.com

48 ms

cookie.js

2 ms

d7f9dfb5bd36903f340b439e8e3d6123.css

48 ms

c1a7a498b60ed1ff5b08869df7dd035c.js

17 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 93% of them (133 requests) were addressed to the original Hexbug.com, 7% (10 requests) were made to Cdn.spinmasterstudios.com. The less responsive or slowest element that took the longest time to load (130 ms) relates to the external source Cdn.spinmasterstudios.com.

Content Size

783.8 kB

After Optimization

717.4 kB

In fact, the total size of Hexbug.com main page is 783.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. 70% of websites need less resources to load. Images take 705.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 66.4 kB

Original 78.4 kB
After minification 70.8 kB
After compression 12.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 66.4 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 36 B

Original 705.3 kB
After minification 705.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. HEXBUG images are well optimized though.

Requests Now

141

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hexbug.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 Hexbug.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.

Social Sharing Optimization

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