Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 95

    SEO

    Google-friendlier than
    93% of websites

random.org

RANDOM.ORG - True Random Number Service

Page Load Speed

1.3 sec in total

First Response

279 ms

Resources Loaded

849 ms

Page Rendered

155 ms

random.org screenshot

About Website

Visit random.org now to see the best up-to-date RANDOM content for United States and also check out these interesting facts you probably never knew about random.org

RANDOM.ORG offers true random numbers to anyone on the Internet. The randomness comes from atmospheric noise, which for many purposes is better than the pseudo-random number algorithms typically used ...

Visit random.org

Key Findings

We analyzed Random.org page load time and found that the first response time was 279 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

random.org performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

92/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value730 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

www.random.org

279 ms

style.css

15 ms

random.js

24 ms

jquery.min.js

70 ms

simpledropdown.jquery.js

16 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 36% of them (13 requests) were addressed to the original Random.org, 19% (7 requests) were made to Apis.google.com and 8% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (279 ms) belongs to the original domain Random.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 93.5 kB (57%)

Content Size

163.3 kB

After Optimization

69.8 kB

In fact, the total size of Random.org main page is 163.3 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. 35% of websites need less resources to load. Javascripts take 105.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 17.6 kB

  • Original 24.3 kB
  • After minification 21.2 kB
  • After compression 6.7 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 3.0 kB, which is 13% 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 17.6 kB or 72% of the original size.

Image Optimization

-11%

Potential reduce by 2.7 kB

  • Original 25.4 kB
  • After minification 22.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. Obviously, RANDOM needs image optimization as it can save up to 2.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 67.0 kB

  • Original 105.9 kB
  • After minification 103.4 kB
  • After compression 38.9 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 67.0 kB or 63% of the original size.

CSS Optimization

-80%

Potential reduce by 6.1 kB

  • Original 7.7 kB
  • After minification 5.8 kB
  • After compression 1.6 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. Random.org needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (53%)

Requests Now

34

After Optimization

16

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

Accessibility Review

random.org accessibility score

68

Accessibility Issues

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

High

Form elements do not have associated labels

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

random.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

random.org SEO score

95

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

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 Random.org 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 Random.org 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 RANDOM. 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: