B — https://random.org | BeaverCheck Audit

Site Health

Score: 80 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Search Console · 3591 peers

You 80

Avg 73

+7 above average

0 50 100

Better than 95% of Google Search Console sites See full Google Search Console benchmark →

Google Workspace · 1679 peers

You 80

Avg 73

+7 above average

0 50 100

Better than 94% of Google Workspace sites See full Google Workspace benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

2 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure

15 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Frandom.org)](https://beavercheck.com/results/0535b706-7baa-4501-b5e1-9aef6c4f5816)

HTML

<a href="https://beavercheck.com/results/0535b706-7baa-4501-b5e1-9aef6c4f5816"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frandom.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Frandom.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. The 1 performance issue below shapes how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

1 performance issue — Akamai's research found 53% of mobile users abandon pages over 3s.

Conversion Barriers

7 warning

7 barrier(s) likely increasing bounce by ~20%.

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

2 form field(s) without a label

+4% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€510 investment → €0.01/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -100%

Investment

€510

6h · 5 findings

Monthly returns

€0.01 /mo

~€0.15 / year

Bandwidth savings €0.01

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

€85 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€510

6.0 developer hours at €85/hr

Based on Ireland rates (€85/hr)

Quick wins

€85 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,000 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+6 more

Bandwidth Waste

€0.01 /mo

172.6 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~17 KB per page load
Saves €0.01/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.61 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.61 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.61 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.61 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.random.org/graphics/nuvola/learn.png	14400.0 s	11.0 KiB
www.random.org/graphics/nuvola/graph.png	14400.0 s	7.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
www.random.org/graphics/nuvola/help.gif	14400.0 s	5.8 KiB
www.random.org/graphics/rdo-logo-300x44.png	14400.0 s	4.2 KiB
www.random.org/js/random.js	14400.0 s	2.1 KiB
www.random.org/css/style.css	14400.0 s	2.0 KiB
www.random.org/css/mobile-style.css	14400.0 s	1003 B
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	0 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.random.org/css/mobile-style.css	1003 B
www.random.org/css/style.css	2.0 KiB
www.random.org/js/random.js	2.1 KiB	150 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 802 ms

URL	Time Spent
random.org/	802 ms
www.random.org/	0.0 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.6 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 56 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.3 s

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 50 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search RANDOM.ORG `div#invisible > div#search > form > div`
What's this fuss about true randomness? `body > div#invisible > div#homepage-wide-column > h2`
true `div#invisible > div#homepage-wide-column > h2 > em`
Prof. Mads Haahr `div#invisible > div#homepage-wide-column > p > a`
School of Computer Science and Statistics `div#invisible > div#homepage-wide-column > p > a`
Trinity College, Dublin `div#invisible > div#homepage-wide-column > p > a`
Randomness and Integrity Services Ltd `div#invisible > div#homepage-wide-column > p > a`
Games and Lotteries `div > div.mainindent > h3 > a`
Lottery Quick Pick `div > div.mainindent > p > a`
Keno Quick Pick `div > div.mainindent > p > a`
Coin Flipper `div > div.mainindent > p > a`
Dice Roller `div > div.mainindent > p > a`
Playing Card Shuffler `div > div.mainindent > p > a`
Birdie Fund Generator `div > div.mainindent > p > a`
Random Drawings `div > div.mainindent > h3 > a`
Q3.1 in the FAQ `div > div.mainindent > p > a`
Third-Party Draw Service `div > div.mainindent > p > a`
Step by Step Guide `div > div.mainindent > p > a`
Step by Step Video `div > div.mainindent > p > a`
Price Calculator `div > div.mainindent > p > a`
Drawing FAQ `div > div.mainindent > p > a`
Public Records `div > div.mainindent > p > a`
Drawing Result Widget `div > div.mainindent > p > a`
Multi-Round Giveaway Service `div > div.mainindent > p > a`
Numbers `div > div.mainindent > h3 > a`
Integer Generator `div > div.mainindent > p > a`
Sequence Generator `div > div.mainindent > p > a`
Integer Set Generator `div > div.mainindent > p > a`
Gaussian Generator `div > div.mainindent > p > a`
Decimal Fraction Generator `div > div.mainindent > p > a`
Raw Random Bytes `div > div.mainindent > p > a`
Lists and Strings and Maps, Oh My! `div > div.mainindent > h3 > a`
List Randomizer `div > div.mainindent > p > a`
String Generator `div > div.mainindent > p > a`
Password Generator `div > div.mainindent > p > a`
Clock Time Generator `div > div.mainindent > p > a`
Calendar Date Generator `div > div.mainindent > p > a`
Geographic Coordinate Generator `div > div.mainindent > p > a`
Bitmaps `div > div.mainindent > p > a`
Hexadecimal Color Code Generator `div > div.mainindent > p > a`
Pregenerated Files `div > div.mainindent > p > a`
Pure White Audio Noise `div > div.mainindent > p > a`
Jazz Scales `div > div.mainindent > p > a`
Samuel Beckett `div > div.mainindent > p > a`
DNA Protein Sequence Randomizer `div > div.mainindent > p > a`
Web Tools and Widgets for Your Pages `div > div.mainindent > h3 > a`
Integer Widget Wizard `div > div.mainindent > p > a`
Draw Widget Wizard `div > div.mainindent > p > a`
HTTP API `div > div.mainindent > p > a`
Guidelines `div > div.mainindent > p > a`
Banned Hosts `div > div.mainindent > p > a`
Learn about Randomness `div > div.mainindent > h3 > a`
Introduction to Randomness `div > div.mainindent > p > a`
History `div > div.mainindent > p > a`
Many Testimonials `div > div.mainindent > p > a`
Acknowledgements `div > div.mainindent > p > a`
Quotations `div > div.mainindent > p > a`
Media Coverage and Scientific Citations `div > div.mainindent > p > a`
News `div > div.mainindent > p > a`
Statistics `div > div.mainindent > h3 > a`
Real-Time Statistics `div > div.mainindent > p > a`
Statistical Analysis `div > div.mainindent > p > a`
Bit Tally `div > div.mainindent > p > a`
Your Quota `div > div.mainindent > p > a`
Contact and Help `div#invisible > div > div.mainindent > h3`
FAQ `div > div.mainindent > p > a`
Newsletter `div > div.mainindent > p > a`
Contact Details `div > div.mainindent > p > a`
BlueSky `div#invisible > div > div > a`
Terms and Conditions `div#invisible > div > div > a`
About Us `div#invisible > div > div > a`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search > form > div > input `div#search > form > div > input`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#invisible > div#homepage-generator > iframe `body > div#invisible > div#homepage-generator > iframe`

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `div#invisible > ul#navigation > li > a.active`
Games `div#invisible > ul#navigation > li > a`
Numbers `div#invisible > ul#navigation > li > a`
Lists & More `div#invisible > ul#navigation > li > a`
Drawings `div#invisible > ul#navigation > li > a`
Web Tools `div#invisible > ul#navigation > li > a`
Statistics `div#invisible > ul#navigation > li > a`
Testimonials `div#invisible > ul#navigation > li > a`
Learn More `div#invisible > ul#navigation > li > a`
Login `div#invisible > ul#navigation > li > a`
Terms and Conditions `div#invisible > div > div > a`
About Us `div#invisible > div > div > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Input buttons have discernible text.

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Document has a `<title>` element

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.random.org/ line 457, col 6	`ReferenceError: $ is not defined at https://www.random.org/:458:7`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

804 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

804 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

804 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

804 ms

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
static.random.org/lib/jquery-3.4.1/jquery-3.4.1.min.js	30.1 KiB	272 ms
www.random.org/js/simpledropdown.jquery.js	258 B
www.random.org/js/random.js	2.0 KiB
www.random.org/css/style.css	2.0 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.random.org/graphics/nuvola/learn.png	14400.0 s	11.0 KiB
www.random.org/graphics/nuvola/graph.png	14400.0 s	7.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
www.random.org/graphics/nuvola/help.gif	14400.0 s	5.8 KiB
www.random.org/graphics/rdo-logo-475x70.png	14400.0 s	5.0 KiB
static.random.org/lib/jquery-3.4.1/jquery-3.4.1.min.js	1209600.0 s	30.1 KiB
www.random.org/js/random.js	14400.0 s	2.0 KiB
www.random.org/css/style.css	14400.0 s	2.0 KiB
www.random.org/js/simpledropdown.jquery.js	14400.0 s	258 B
www.random.org/graphics/tab_rounded.gif	14400.0 s	213 B
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	0 B

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Learn about Randomness `div#invisible > div > div.maingraphic3 > img`	www.random.org/graphics/nuvola/learn.png	10.9 KiB	10.2 KiB
Statistics `div#invisible > div > div.maingraphic3 > img`	www.random.org/graphics/nuvola/graph.png	7.8 KiB	7.1 KiB
Contact and Help `div#invisible > div > div.maingraphic3 > img`	www.random.org/graphics/nuvola/help.gif	5.7 KiB	4.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 249 ms

URL	Time Spent
random.org/	249 ms
www.random.org/	0.0 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.8 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 87 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.1 s

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 60 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy `div#cookie-banner > div > p > a`
Privacy Dashboard `div#cookie-banner > div > p > a`
Verify past results from this widget `div#invisible > div#homepage-generator > div > a`
Prof. Mads Haahr `div#invisible > div#homepage-wide-column > p > a`
School of Computer Science and Statistics `div#invisible > div#homepage-wide-column > p > a`
Trinity College, Dublin `div#invisible > div#homepage-wide-column > p > a`
Randomness and Integrity Services Ltd `div#invisible > div#homepage-wide-column > p > a`
Games and Lotteries `div > div.mainindent > h3 > a`
Lottery Quick Pick `div > div.mainindent > p > a`
Keno Quick Pick `div > div.mainindent > p > a`
Coin Flipper `div > div.mainindent > p > a`
Dice Roller `div > div.mainindent > p > a`
Playing Card Shuffler `div > div.mainindent > p > a`
Birdie Fund Generator `div > div.mainindent > p > a`
Random Drawings `div > div.mainindent > h3 > a`
Q3.1 in the FAQ `div > div.mainindent > p > a`
Third-Party Draw Service `div > div.mainindent > p > a`
Step by Step Guide `div > div.mainindent > p > a`
Step by Step Video `div > div.mainindent > p > a`
Price Calculator `div > div.mainindent > p > a`
Drawing FAQ `div > div.mainindent > p > a`
Public Records `div > div.mainindent > p > a`
Drawing Result Widget `div > div.mainindent > p > a`
Multi-Round Giveaway Service `div > div.mainindent > p > a`
Numbers `div > div.mainindent > h3 > a`
Integer Generator `div > div.mainindent > p > a`
Sequence Generator `div > div.mainindent > p > a`
Integer Set Generator `div > div.mainindent > p > a`
Gaussian Generator `div > div.mainindent > p > a`
Decimal Fraction Generator `div > div.mainindent > p > a`
Raw Random Bytes `div > div.mainindent > p > a`
Lists and Strings and Maps, Oh My! `div > div.mainindent > h3 > a`
List Randomizer `div > div.mainindent > p > a`
String Generator `div > div.mainindent > p > a`
Password Generator `div > div.mainindent > p > a`
Clock Time Generator `div > div.mainindent > p > a`
Calendar Date Generator `div > div.mainindent > p > a`
Geographic Coordinate Generator `div > div.mainindent > p > a`
Bitmaps `div > div.mainindent > p > a`
Hexadecimal Color Code Generator `div > div.mainindent > p > a`
Pregenerated Files `div > div.mainindent > p > a`
Pure White Audio Noise `div > div.mainindent > p > a`
Jazz Scales `div > div.mainindent > p > a`
Samuel Beckett `div > div.mainindent > p > a`
DNA Protein Sequence Randomizer `div > div.mainindent > p > a`
Web Tools and Widgets for Your Pages `div > div.mainindent > h3 > a`
Integer Widget Wizard `div > div.mainindent > p > a`
Draw Widget Wizard `div > div.mainindent > p > a`
HTTP API `div > div.mainindent > p > a`
Guidelines `div > div.mainindent > p > a`
Banned Hosts `div > div.mainindent > p > a`
Learn about Randomness `div > div.mainindent > h3 > a`
Introduction to Randomness `div > div.mainindent > p > a`
History `div > div.mainindent > p > a`
Many Testimonials `div > div.mainindent > p > a`
Acknowledgements `div > div.mainindent > p > a`
Quotations `div > div.mainindent > p > a`
Media Coverage and Scientific Citations `div > div.mainindent > p > a`
News `div > div.mainindent > p > a`
Statistics `div > div.mainindent > h3 > a`
Real-Time Statistics `div > div.mainindent > p > a`
Statistical Analysis `div > div.mainindent > p > a`
Bit Tally `div > div.mainindent > p > a`
Your Quota `div > div.mainindent > p > a`
Contact and Help `div#invisible > div > div.mainindent > h3`
FAQ `div > div.mainindent > p > a`
Newsletter `div > div.mainindent > p > a`
Contact Details `div > div.mainindent > p > a`
BlueSky `div#invisible > div > div > a`
Terms and Conditions `div#invisible > div > div > a`
About Us `div#invisible > div > div > a`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search > form > div > input `div#search > form > div > input`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#invisible > div#homepage-generator > iframe `body > div#invisible > div#homepage-generator > iframe`

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.

Internationalization and localization

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms and Conditions `div#invisible > div > div > a`
About Us `div#invisible > div > div > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Document has a `<title>` element

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Results for https://random.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Trust (1)

Usability (1)

Content (3)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Accessibility

Contrast

Names and labels

Internationalization and localization

Best practices

Best Practices

Browser Compatibility

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Accessibility

Contrast

Names and labels

Internationalization and localization

Best practices

Best Practices

Browser Compatibility

SEO

Keyboard Shortcuts