Website review, no card needed

hoodamath.com logo

hoodamath.com website review

Visit site (opens in a new tab)Reviewed 11 October 202630 issues · 70 checks

This review found 30 issues worth fixing on hoodamath.com, 5 of them high impact, across 70 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
1.5 s687 msJun 13Aug 221.4 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 2026776 ms
Jun 20, 2026858 ms
Jun 27, 2026911 ms
Jul 4, 2026967 ms
Jul 11, 2026991 ms
Jul 18, 2026967 ms
Jul 25, 2026967 ms
Aug 1, 2026962 ms
Aug 8, 20261.1 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
246 ms93 msJun 20Aug 22153 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 2026159 ms
Jun 27, 2026159 ms
Jul 4, 2026158 ms
Jul 11, 2026120 ms
Jul 18, 2026111 ms
Jul 25, 2026120 ms
Aug 1, 2026127 ms
Aug 8, 2026142 ms
Aug 15, 2026228 ms
Aug 22, 2026153 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 hoodamath.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix90
  • Render-blocking requests

    1.8 s

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

  • Use efficient cache lifetimes

    1.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Other Google APIs/SDKs, Google Tag Manager and Google/Doubleclick Ads and others), adding 1.1 MB and 495 ms of main-thread time.

  • Improve image delivery

    541 KiB

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

  • Reduce unused JavaScript

    461 KiB

    About 461 KiB of JavaScript is downloaded but never used on this page.

  • Other Google APIs/SDKs adds 154 ms

    154 ms

    Other Google APIs/SDKs costs a phone 154 ms of main-thread work and 344 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.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90 (desktop: 94). That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 682 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix94
  • Time to Interactive: 10.8 s

    10.8 s

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

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

    +20%

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

  • Largest content (LCP) got 62% slower for real visitors

    +62%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Yes, you're in the right place — HoodaMath.com has a new lo…”.

  • Speed Index: 3.6 s

    3.6 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.06

    0.06

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

  • Total Blocking Time: 33 ms

    33 ms

    Scripts block the page for only 33 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix58
  • Page weight: 2.3 MB in 87 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 87 requests on a phone: images 1.2 MB (46), scripts 938 KiB (21) and fonts 69 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (829 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 8 images far larger than shown

    443 KiB

    8 images are downloaded at several times the size a phone draws them, for example androidmobile_709x131.png at 709 px wide, shown at 184 px. Resized copies would save about 443 KiB.

  • 9 images below the first screen load straight away

    9 images further down the page (403 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

Accessibility

6 to fixGoogle 9293
  • 3 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 111 links without text

    111 visible links have no text or label, so screen readers cannot say where they go.

  • All page content should be contained by landmarks (4 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (48 elements)

    Alternative text of images should not be repeated as text: 48 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (180 characters)

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

  • No X (Twitter) card tag

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

  • 278 internal links, 4 external

    The homepage links to 278 pages on hoodamath.com and 4 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Free Math Games for School”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Hooda Math - Free Online Math Games for School”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: FAQPage, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

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

3 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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,265 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 7791
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.google.com/cse/static/element/3735a6ee3000c0cb/default_v6+en.css' from origin …”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    185 of 189 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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: “3M+ students”. 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.

  • No form on the homepage

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

  • 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.

  • About 696 words of copy

    The homepage carries about 696 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop”, “OOO QuizQuick order-of-operations check.” and “Contact”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 3 cookies set on arrival

    3

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

  • 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.

  • 18 other companies contacted

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

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 hoodamath.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on hoodamath.com, including 13 speed issues, 1 SEO issue and 3 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