Website review, no card needed

luckyduckgames.com logo

luckyduckgames.com website review

Visit site (opens in a new tab)Reviewed 19 October 202647 issues · 82 checks

This review found 47 issues worth fixing on luckyduckgames.com, 20 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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 25Oct 102.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.3 s
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
692 ms155 msApr 25Oct 10609 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026217 ms
May 2, 2026486 ms
May 9, 2026510 ms
May 16, 2026537 ms
May 23, 2026548 ms
May 30, 2026554 ms
Jun 6, 2026531 ms
Jun 13, 2026519 ms
Jun 20, 2026515 ms
Jun 27, 2026512 ms
Jul 4, 2026553 ms
Jul 11, 2026585 ms
Jul 18, 2026602 ms
Jul 25, 2026611 ms
Aug 1, 2026621 ms
Aug 8, 2026620 ms
Aug 15, 2026623 ms
Aug 22, 2026630 ms
Aug 29, 2026622 ms
Sep 5, 2026625 ms
Sep 12, 2026626 ms
Sep 19, 2026617 ms
Sep 26, 2026615 ms
Oct 3, 2026608 ms
Oct 10, 2026609 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 luckyduckgames.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. luckyduckgames.com at 0.5 s0.5 s
  2. luckyduckgames.com at 1.0 s1.0 s
  3. luckyduckgames.com at 1.5 s1.5 s
  4. luckyduckgames.com at 2.0 s2.0 s
  5. luckyduckgames.com at 2.5 s2.5 s
  6. luckyduckgames.com at 3.0 s3.0 s
  7. luckyduckgames.com at 3.5 s3.5 s
  8. luckyduckgames.com at 4.0 s4.0 s

Speed

10 to fix29
  • Use efficient cache lifetimes

    12.5 s · 5.4 MB

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

  • Render-blocking requests

    3.3 s

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

  • Reduce unused JavaScript

    1.5 s · 757 KiB

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and Google Fonts and others), adding 1.5 MB and 908 ms of main-thread time.

  • Google Tag Manager adds 689 ms

    689 ms

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

    600 ms · 118 KiB

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

  • Improve image delivery

    500 ms · 98 KiB

    4 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Facebook adds 219 ms

    219 ms

    Facebook costs a phone 219 ms of main-thread work and 565 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.

  • Main-thread work: 2.1 s

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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: 51 ms

    51 ms

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

Core Web Vitals

11 to fix32
  • 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.

  • Largest Contentful Paint: 15.6 s

    15.6 s

    Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “…”.

  • Time to Interactive: 27.9 s

    27.9 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Total Blocking Time: 644 ms

    644 ms

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

  • Cumulative Layout Shift: 0.252

    0.252

    The layout shifts by 0.252 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

    +73%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-10, 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).

Images and page weight

4 to fix36
  • Page weight: 6.5 MB in 46 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 46 requests on a phone: images 4.2 MB (19), scripts 1.9 MB (8) and fonts 315 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 5 images in older formats

    5 images (3.9 MB) 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.

  • An image on the first screen is lazy-loaded

    chronicles-of-crime.webp 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 1.9 g of CO₂ per visit

    1.85 g

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

1 checks passed
  • 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 8891
  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h3 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

6 to fixGoogle 8570
  • No meta description

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Lucky Duck Games”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 84 internal links, 8 external

    The homepage links to 84 pages on luckyduckgames.com and 8 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://luckyduckgames.com/usa/.

  • 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://luckyduckgames.com/usa/1_index_sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing 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://luckyduckgames.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 (674 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix70
  • 1 page without a title

    https://luckyduckgames.com/usa/page/16-newsletter has no <title>, so Google invents the link text in results.

  • 10 pages without a meta description

    https://luckyduckgames.com/usa/games/187-universe, https://luckyduckgames.com/usa/games/188-the-dark-quarter, https://luckyduckgames.com/usa/games/189-chronicles-of-crime, https://luckyduckgames.com/usa/games/190-kingdom-rush, https://luckyduckgames.com/usa/games/191-andromeda-s-edge and https://luckyduckgames.com/usa/games/192-tranquility and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://luckyduckgames.com/usa/game/820-2045-andromeda-s-edge-supernova-component-upgrade-kit, whose canonical is https://luckyduckgames.com/usa/game/820-andromeda-s-edge-supernova-component-upgrade-kit. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://luckyduckgames.com/usa/games/187-universe, https://luckyduckgames.com/usa/games/188-the-dark-quarter, https://luckyduckgames.com/usa/games/189-chronicles-of-crime, https://luckyduckgames.com/usa/games/190-kingdom-rush, https://luckyduckgames.com/usa/games/191-andromeda-s-edge and https://luckyduckgames.com/usa/games/192-tranquility and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

2 to fixGoogle 7791
  • 5 small tap targets

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

  • Deprecated browser APIs

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 social proof

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

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

    The homepage carries about 270 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Join the Lucky Duck Newsletter” and “Subscribe”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 4 cookies set on arrival

    4

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

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

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 luckyduckgames.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 © 2025.

Stack

E-commerce
PrestaShop
Analytics
Google Analytics | Google Tag Manager

Company

Founded
2016
Headquarters
Kraków

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on luckyduckgames.com, including 21 speed issues, 6 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