Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

streamerbans.com

StreamerBans

Page Load Speed

2.8 sec in total

First Response

222 ms

Resources Loaded

2.4 sec

Page Rendered

139 ms

streamerbans.com screenshot

About Website

Click here to check amazing Streamer Bans content for Poland. Otherwise, check out these important facts you probably never knew about streamerbans.com

StreamerBans keeps track of all partnered Twitch streamers that get banned on Twitch

Visit streamerbans.com

Key Findings

We analyzed Streamerbans.com page load time and found that the first response time was 222 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

streamerbans.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.316

37/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

streamerbans.com

222 ms

streamerbans.com

1571 ms

adsbygoogle.js

190 ms

t.js

39 ms

032c6949a6d9ebd2.css

95 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 58% of them (15 requests) were addressed to the original Streamerbans.com, 31% (8 requests) were made to Static-cdn.jtvnw.net and 4% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Streamerbans.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.9 kB (7%)

Content Size

788.6 kB

After Optimization

729.7 kB

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

HTML Optimization

-77%

Potential reduce by 52.3 kB

  • Original 67.7 kB
  • After minification 67.6 kB
  • After compression 15.4 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 52.3 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 6.6 kB

  • Original 720.2 kB
  • After minification 713.5 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. Streamer Bans images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 12 B

  • Original 744 B
  • After minification 744 B
  • After compression 732 B

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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 12 (50%)

Requests Now

24

After Optimization

12

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

Accessibility Review

streamerbans.com accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

streamerbans.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

streamerbans.com SEO score

100

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

    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 Streamerbans.com 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 Streamerbans.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 data is detected on the main page of Streamer Bans. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: