Website review, no card needed

thewedogame.com logo

thewedogame.com website review

Visit site (opens in a new tab)Reviewed 12 November 202635 issues · 75 checks

This review found 35 issues worth fixing on thewedogame.com, 10 of them high impact, across 75 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

Full-page screenshot of thewedogame.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thewedogame.com at 0.8 s0.8 s
  2. thewedogame.com at 1.6 s1.6 s
  3. thewedogame.com at 2.4 s2.4 s
  4. thewedogame.com at 3.2 s3.2 s
  5. thewedogame.com at 4.0 s4.0 s
  6. thewedogame.com at 4.8 s4.8 s
  7. thewedogame.com at 5.6 s5.6 s
  8. thewedogame.com at 6.4 s6.4 s

Speed

10 to fix53
  • Render-blocking requests

    4.2 s

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

  • Improve image delivery

    1.4 s · 633 KiB

    13 images could be 633 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 472 KiB

    About 472 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Font display

    1.0 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, WordPress Site Stats and Google/Doubleclick Ads and others), adding 1.8 MB and 869 ms of main-thread time.

  • Mobile performance score: 53

    53/100

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

  • Google Tag Manager adds 855 ms

    855 ms

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

  • Use efficient cache lifetimes

    350 ms · 43 KiB

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

  • 8 long tasks on the main thread

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

  • WordPress adds 0 ms

    0 ms

    WordPress costs a phone 0 ms of main-thread work and 862 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.

  • Reduce unused CSS

    150 ms · 34 KiB

    About 34 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.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 820 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

6 to fix57
  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Easy games to play at home australia”. Most of its time is resource load delay (5.7 s).

  • Speed Index: 10.4 s

    10.4 s

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

  • Time to Interactive: 12.5 s

    12.5 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 404 ms

    404 ms

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

  • 1 image without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix81
  • Page weight: 2.3 MB in 106 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 106 requests on a phone: scripts 1.1 MB (38), images 877 KiB (22) and fonts 232 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    The-WeDo-Game.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.65 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8892
  • 17 text elements with low contrast

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

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • No main landmark

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

  • 25 links without text

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • 6 H1 headlines

    There are 6 <h1> headlines (“Creative, fun activities to do together.”, “A Lifetime Of Memories: The Collection” and “The WeDo Game – Baby Edition”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 12 internal links, 24 external

    The homepage links to 12 pages on thewedogame.com and 24 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Sensory Play For Baby Toddler Family And Couples. Gift Idea. Fun Games To Play. Family Games And Activities. Games For …”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Easy Games to Play at Home in Australia - The WeDo Game”.

  • Canonical URL set

    The canonical URL is https://thewedogame.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://thewedogame.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://thewedogame.com/terms-conditions, https://thewedogame.com/privacy-policy, https://thewedogame.com/shipping-information and https://thewedogame.com/sitemap have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://thewedogame.com/contact, https://thewedogame.com/wholesale-3, https://thewedogame.com/terms-conditions, https://thewedogame.com/privacy-policy, https://thewedogame.com/shipping-information and https://thewedogame.com/sitemap have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://thewedogame.com/contact, https://thewedogame.com/how-to-play, https://thewedogame.com/wholesale-3, https://thewedogame.com/shipping-information and https://thewedogame.com/sitemap have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 5 pages slow to respond

    https://thewedogame.com/buy-the-game, https://thewedogame.com/wholesale-3, https://thewedogame.com/terms-conditions, https://thewedogame.com/privacy-policy and https://thewedogame.com/shipping-information took over 3 s to send their HTML from our server.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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: 27 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 820 words of copy

    The homepage carries about 820 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Buy the Game” and “Contact Us”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 12 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2024.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Synergywholesale Ap Synergy Wholesale Pty Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on thewedogame.com, including 16 speed issues, 3 SEO issues and 2 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