wheelofnames.com website review

A phone's processor spends 30.0 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.3 s.

8 third-party services load with your homepage (pub.network, Google/Doubleclick Ads and Pubmatic and others), adding 1.4 MB and 1.2 s of main-thread time.

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

99 files are served with short cache lifetimes, so returning visitors download them again (826 KiB).

About 569 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

pub.network costs a phone 294 ms of main-thread work and 436 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google/Doubleclick Ads costs a phone 252 ms of main-thread work and 458 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

17 long tasks block the main thread while loading, the longest for 289 ms. During a long task the page ignores taps.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

2 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 32.0 s. Good is under 3.8 s.

Visually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 617 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 414 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 394 ms to 411 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 1,244 requests on a phone: scripts 1.9 MB (117), other files 432 KiB (569) and HTML 260 KiB (116). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is only 14 characters: “Wheel of Names”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 6 pages on wheelofnames.com and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://wheelofnames.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/, https://wheelofnames.com/how-to-use-in-the-classroom, https://wheelofnames.com/user-reviews-and-tutorials, https://wheelofnames.com/privacy-policy, https://wheelofnames.com/streaming and https://wheelofnames.com/randomness-audit all use the title “Wheel of Names”. Search engines can't tell which page to show for a search, so each competes with the others.

https://wheelofnames.com/how-to-use-in-the-classroom, https://wheelofnames.com/user-reviews-and-tutorials, https://wheelofnames.com/privacy-policy, https://wheelofnames.com/streaming and https://wheelofnames.com/randomness-audit use the same meta description. A description written for each page earns more clicks.

https://wheelofnames.com/faq has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

37 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 959 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 14 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 84 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.