Tools & Wizards About Us
council.wax.io screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

council.wax.io

WAX Advisory Council | Where tech, video gaming, and entertainment experts meet blockchain

Page Load Speed

21.6 sec in total

First Response

61 ms

Resources Loaded

16.2 sec

Page Rendered

5.4 sec

council.wax.io screenshot

About Website

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

WAX Advisory Council members are leaders from prestigious global companies in tech, video gaming, and entertainment, to accelerate the adoption of WAX Blockchain technology.

Visit council.wax.io

Key Findings

We analyzed Council.wax.io page load time and found that the first response time was 61 ms and then it took 21.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

council.wax.io performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value38.4 s

0/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.177

68/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

council.wax.io

61 ms

afq5kjp.css

137 ms

style.css

1042 ms

wax.svg

182 ms

read_more.svg

92 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 78% of them (21 requests) were addressed to the original Council.wax.io, 15% (4 requests) were made to Use.typekit.net and 4% (1 request) were made to Js.createsend1.com. The less responsive or slowest element that took the longest time to load (16.1 sec) belongs to the original domain Council.wax.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.1 kB (4%)

Content Size

2.3 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Council.wax.io main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 13.0 kB

  • Original 15.5 kB
  • After minification 8.9 kB
  • After compression 2.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 6.6 kB, which is 42% 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 13.0 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 76.1 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Council WAX images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 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.

Requests Breakdown

We found no issues to fix!

Requests Now

23

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

council.wax.io

council.wax.io

61 ms

afq5kjp.css

afq5kjp.css

137 ms

style.css

style.css

1042 ms

wax.svg

wax.svg

182 ms

read_more.svg

read_more.svg

92 ms

microsoft.png

microsoft.png

292 ms

marvel.png

marvel.png

156 ms

Magic-Leap-Logo.png

Magic-Leap-Logo.png

183 ms

atari-logo.png

atari-logo.png

414 ms

animoca-logo.png

animoca-logo.png

241 ms

copypastesubscribeformlogic.js

copypastesubscribeformlogic.js

638 ms

Exploding-Kittens.png

Exploding-Kittens.png

210 ms

Gumi-Website-Logo.png

Gumi-Website-Logo.png

208 ms

Unity-Logo.png

Unity-Logo.png

575 ms

topps.svg

topps.svg

258 ms

badcrypto-logo-white.png

badcrypto-logo-white.png

16061 ms

Pranksy-Website-Logo-Size.png

Pranksy-Website-Logo-Size.png

709 ms

networking.svg

networking.svg

405 ms

mail.svg

mail.svg

726 ms

twitter.svg

twitter.svg

436 ms

telegram.svg

telegram.svg

499 ms

p.css

p.css

27 ms

nasa-unsplash.png

nasa-unsplash.png

455 ms

Pranksy-Website-Partner-Highlight.jpg

Pranksy-Website-Partner-Highlight.jpg

915 ms

d

d

109 ms

d

d

137 ms

d

d

135 ms

Accessibility Review

council.wax.io accessibility score

97

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

council.wax.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

SEO Factors

council.wax.io SEO score

85

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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

council.wax.io

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