Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

theriotroom.com

The Riot Room - Kansas City, MO : The Riot Room

Page Load Speed

6.7 sec in total

First Response

1.7 sec

Resources Loaded

3.8 sec

Page Rendered

1.3 sec

theriotroom.com screenshot

About Website

Welcome to theriotroom.com homepage info - get ready to check The Riot Room best content for United States right away, or after learning these important things about theriotroom.com

Kansas City, MO

Visit theriotroom.com

Key Findings

We analyzed Theriotroom.com page load time and found that the first response time was 1.7 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

theriotroom.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value48.1 s

0/100

10%

Network Requests Diagram

www.theriotroom.com

1666 ms

style.css

554 ms

facebook-comments-hidewpcomments.css

114 ms

facebook-rsvp.css

117 ms

facebook-comments-widgets.css

119 ms

Our browser made a total of 163 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Theriotroom.com, 79% (129 requests) were made to Cdn.ticketfly.com and 8% (13 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Theriotroom.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 445.2 kB (25%)

Content Size

1.8 MB

After Optimization

1.3 MB

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

HTML Optimization

-88%

Potential reduce by 128.8 kB

  • Original 146.6 kB
  • After minification 135.0 kB
  • After compression 17.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. 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 128.8 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 14.7 kB

  • Original 1.2 MB
  • After minification 1.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. The Riot Room images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 243.0 kB

  • Original 384.4 kB
  • After minification 374.8 kB
  • After compression 141.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 243.0 kB or 63% of the original size.

CSS Optimization

-80%

Potential reduce by 58.7 kB

  • Original 73.0 kB
  • After minification 55.3 kB
  • After compression 14.3 kB

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. Theriotroom.com needs all CSS files to be minified and compressed as it can save up to 58.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (30%)

Requests Now

162

After Optimization

113

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

Accessibility Review

theriotroom.com accessibility score

85

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

High

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

Best Practices

theriotroom.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

theriotroom.com SEO score

93

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

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 Theriotroom.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 Theriotroom.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 The Riot Room. 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: