Website review, no card needed

lotteryusa.com logo

lotteryusa.com website review

Visit site (opens in a new tab)Reviewed 11 October 202639 issues · 76 checks

This review found 39 issues worth fixing on lotteryusa.com, 10 of them high impact, across 76 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.1 sApr 18Oct 32.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.5 s
Apr 25, 20262.5 s
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
517 ms296 msApr 18Oct 3488 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026327 ms
Apr 25, 2026330 ms
May 2, 2026327 ms
May 9, 2026324 ms
May 16, 2026321 ms
May 23, 2026336 ms
May 30, 2026357 ms
Jun 6, 2026380 ms
Jun 13, 2026406 ms
Jun 20, 2026417 ms
Jun 27, 2026423 ms
Jul 4, 2026427 ms
Jul 11, 2026426 ms
Jul 18, 2026427 ms
Jul 25, 2026438 ms
Aug 1, 2026454 ms
Aug 8, 2026473 ms
Aug 15, 2026488 ms
Aug 22, 2026491 ms
Aug 29, 2026487 ms
Sep 5, 2026480 ms
Sep 12, 2026480 ms
Sep 19, 2026480 ms
Sep 26, 2026482 ms
Oct 3, 2026488 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of lotteryusa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lotteryusa.com at 0.4 s0.4 s
  2. lotteryusa.com at 0.8 s0.8 s
  3. lotteryusa.com at 1.1 s1.1 s
  4. lotteryusa.com at 1.5 s1.5 s
  5. lotteryusa.com at 1.9 s1.9 s
  6. lotteryusa.com at 2.3 s2.3 s
  7. lotteryusa.com at 2.6 s2.6 s
  8. lotteryusa.com at 3.0 s3.0 s

Speed

13 to fix61
  • Render-blocking requests

    2.7 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.

  • Use efficient cache lifetimes

    150 ms · 2.6 MB

    20 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

  • Reduce unused JavaScript

    1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (adthrive.com, Google Tag Manager and Google/Doubleclick Ads and others), adding 1.9 MB and 980 ms of main-thread time.

  • Mobile performance score: 61

    61/100

    Your mobile performance score is 61 (desktop: 61). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    933 KiB

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

  • Reduce unused CSS

    300 ms · 94 KiB

    About 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.9 s

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

  • adthrive.com adds 310 ms

    310 ms

    adthrive.com costs a phone 310 ms of main-thread work and 736 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.

  • 16 long tasks on the main thread

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

  • Google/Doubleclick Ads adds 192 ms

    192 ms

    Google/Doubleclick Ads costs a phone 192 ms of main-thread work and 533 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 Tag Manager adds 192 ms

    192 ms

    Google Tag Manager costs a phone 192 ms of main-thread work and 299 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.

  • 1,836 HTML elements

    The page has 1,836 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    79 KiB

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

  • Chained critical requests

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

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 25.2 s

    25.2 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 623 ms

    623 ms

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

  • Real-user INP: 206 ms

    206 ms

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

  • Tap response (INP) got 48% slower for real visitors

    +48%

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Latest Powerball and Mega Millions results”.

  • 29 images without width and height

    29 images have no width and height attributes, so the layout jumps as each one loads.

6 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 399 ms

    399 ms

    Real visitors wait 399 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix33
  • Page weight: 4.7 MB in 149 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 149 requests on a phone: scripts 3.1 MB (30), images 1.3 MB (21) and other files 109 KiB (85). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.34 g

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

Accessibility

5 to fixGoogle 8768
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 5 buttons without a name

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (6 elements).

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 5 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 8 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 10069
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Lottery USA: Lottery Numbers, Results, Payouts, Rules & more. Est. 1995”.

  • Meta description is long (224 characters)

    Your meta description is 224 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 243 internal links, 5 external

    The homepage links to 243 pages on lotteryusa.com and 5 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.lotteryusa.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.lotteryusa.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.lotteryusa.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 99 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No call to action on the first screen

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

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

  • Only about 2 words

    The homepage has only about 2 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Sign up for free”, “Join” and “Contact us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Microsoft Clarity.

Privacy and tracking

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at lotteryusa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on lotteryusa.com, including 22 speed issues, 6 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25