Website review, no card needed

hoopladigital.com logo

hoopladigital.com website review

Visit site (opens in a new tab)Reviewed 11 October 202633 issues · 62 checks

This review found 33 issues worth fixing on hoopladigital.com, 14 of them high impact, across 62 checks. The most urgent: improve image delivery. 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
6.7 s4.3 sApr 18Oct 34.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20266.4 s
Apr 25, 20266.4 s
May 2, 20266.4 s
May 9, 20266.4 s
May 16, 20266.4 s
May 23, 20266.4 s
May 30, 20266.4 s
Jun 6, 20266.4 s
Jun 13, 20266.4 s
Jun 20, 20266.4 s
Jun 27, 20266.4 s
Jul 4, 20266.5 s
Jul 11, 20266.1 s
Jul 18, 20265.5 s
Jul 25, 20265.1 s
Aug 1, 20264.7 s
Aug 8, 20264.6 s
Aug 15, 20264.7 s
Aug 22, 20264.7 s
Aug 29, 20264.8 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
785 ms100 msApr 18Oct 3180 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026604 ms
Apr 25, 2026600 ms
May 2, 2026614 ms
May 9, 2026631 ms
May 16, 2026645 ms
May 23, 2026651 ms
May 30, 2026654 ms
Jun 6, 2026666 ms
Jun 13, 2026679 ms
Jun 20, 2026692 ms
Jun 27, 2026706 ms
Jul 4, 2026705 ms
Jul 11, 2026577 ms
Jul 18, 2026395 ms
Jul 25, 2026283 ms
Aug 1, 2026224 ms
Aug 8, 2026206 ms
Aug 15, 2026203 ms
Aug 22, 2026202 ms
Aug 29, 2026197 ms
Sep 5, 2026192 ms
Sep 12, 2026187 ms
Sep 19, 2026182 ms
Sep 26, 2026179 ms
Oct 3, 2026180 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 hoopladigital.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix73
  • Improve image delivery

    11.4 s · 2.1 MB

    6 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.4 s faster on a phone.

  • Use efficient cache lifetimes

    4.8 s · 835 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused CSS

    150 ms · 21 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (bc0a.com and Google Fonts), adding 130 KiB and 0 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 125 ms

    125 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.2 s

    5.2 s

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

  • Largest Contentful Paint: 19.1 s

    19.1 s

    Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LOG IN Welcome to hoopla hoopla puts your public library at…”.

  • Time to Interactive: 19.1 s

    19.1 s

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

  • Real-user INP: 213 ms

    213 ms

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 3 images without width and height

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

8 checks passed
  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (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: 679 ms

    679 ms

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

  • Tap response (INP) got 70% faster for real visitors

    -70%

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

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

    -27%

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

  • Speed Index: 2.4 s

    2.4 s

    Visually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix67
  • Page weight: 3.3 MB in 31 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 31 requests on a phone: images 2.9 MB (7), fonts 302 KiB (8) and stylesheets 47 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.95 g

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

Accessibility

3 to fixGoogle 9789
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

1 checks passed
  • 16 automated accessibility rules passed

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

SEO

9 to fixGoogle 9250
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

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

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

2 checks passed
  • 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.hoopladigital.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

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

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

Best practices

2 to fixGoogle 9689
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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.

  • No calls to action

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

  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 0 words

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

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 8 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

  • 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 hoopladigital.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
Next.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on hoopladigital.com, including 11 speed issues, 9 SEO issues and 6 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