Tools & Wizards About Us
scenariogenerator.net screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

scenariogenerator.net

Scenario Generator | Random Challenges for Popular Games

Page Load Speed

1.2 sec in total

First Response

30 ms

Resources Loaded

1.1 sec

Page Rendered

126 ms

scenariogenerator.net screenshot

About Website

Click here to check amazing Scenario Generator content for United States. Otherwise, check out these important facts you probably never knew about scenariogenerator.net

Scenario Generator has challenge randomizers for all your favourite games including Skyrim, Minecraft, and Pokemon.

Visit scenariogenerator.net

Key Findings

We analyzed Scenariogenerator.net page load time and found that the first response time was 30 ms and then it took 1.2 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

scenariogenerator.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value2,920 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

scenariogenerator.net

30 ms

www.scenariogenerator.net

151 ms

css

39 ms

application-2372502f0ee5a919e73eadfaad353666.css

79 ms

application-3b24546014a3bbf7c9645c96d8425405.js

97 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 12% of them (4 requests) were addressed to the original Scenariogenerator.net, 15% (5 requests) were made to Platform.twitter.com and 15% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (595 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.7 kB (66%)

Content Size

646.8 kB

After Optimization

221.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Scenariogenerator.net main page is 646.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. 45% of websites need less resources to load. Javascripts take 388.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 21.6 kB

  • Original 26.2 kB
  • After minification 21.9 kB
  • After compression 4.6 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 4.3 kB, which is 16% 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 21.6 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 207 B

  • Original 4.9 kB
  • After minification 4.7 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. Scenario Generator images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 213.6 kB

  • Original 388.0 kB
  • After minification 383.3 kB
  • After compression 174.4 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 213.6 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 190.4 kB

  • Original 227.7 kB
  • After minification 226.2 kB
  • After compression 37.4 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. Scenariogenerator.net needs all CSS files to be minified and compressed as it can save up to 190.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (45%)

Requests Now

29

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scenariogenerator.net

scenariogenerator.net

30 ms

www.scenariogenerator.net

www.scenariogenerator.net

151 ms

css

css

39 ms

application-2372502f0ee5a919e73eadfaad353666.css

application-2372502f0ee5a919e73eadfaad353666.css

79 ms

application-3b24546014a3bbf7c9645c96d8425405.js

application-3b24546014a3bbf7c9645c96d8425405.js

97 ms

adsbygoogle.js

adsbygoogle.js

5 ms

mc-validate.js

mc-validate.js

36 ms

button.js

button.js

63 ms

analytics.js

analytics.js

82 ms

widgets.js

widgets.js

181 ms

pixel.gif

pixel.gif

95 ms

ca-pub-2676186968823013.js

ca-pub-2676186968823013.js

50 ms

zrt_lookup.html

zrt_lookup.html

100 ms

show_ads_impl.js

show_ads_impl.js

48 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

44 ms

collect

collect

83 ms

like.php

like.php

104 ms

ads

ads

199 ms

osd.js

osd.js

17 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

127 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

528 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

595 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

52 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

74 ms

m_js_controller.js

m_js_controller.js

60 ms

abg.js

abg.js

72 ms

favicon

favicon

91 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

86 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

34 ms

s

s

21 ms

x_button_blue2.png

x_button_blue2.png

10 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

3 ms

jot.html

jot.html

29 ms

Accessibility Review

scenariogenerator.net accessibility score

75

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

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

scenariogenerator.net best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

scenariogenerator.net SEO score

92

Search Engine Optimization Advices

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scenariogenerator.net 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 Scenariogenerator.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

scenariogenerator.net

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