Website review, no card needed

prodigystore.eu logo

prodigystore.eu website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 74 checks

This review found 36 issues worth fixing on prodigystore.eu, 10 of them high impact, across 74 checks. The most urgent: avoid multiple page redirects. 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 prodigystore.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. prodigystore.eu at 0.5 s0.5 s
  2. prodigystore.eu at 1.1 s1.1 s
  3. prodigystore.eu at 1.6 s1.6 s
  4. prodigystore.eu at 2.2 s2.2 s
  5. prodigystore.eu at 2.7 s2.7 s
  6. prodigystore.eu at 3.3 s3.3 s
  7. prodigystore.eu at 3.8 s3.8 s
  8. prodigystore.eu at 4.4 s4.4 s

Speed

12 to fix47
  • Avoid multiple page redirects

    7.1 s

    The page goes through 3 redirects before it starts loading, costing about 7.1 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    3.6 s · 641 KiB

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

  • Mobile performance score: 47

    47/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (powergrip.fi, Google Tag Manager and JSDelivr CDN and others), adding 2.1 MB and 1.1 s of main-thread time.

  • powergrip.fi adds 828 ms

    828 ms

    powergrip.fi costs a phone 828 ms of main-thread work and 1.6 MB 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.

  • Document request latency

    700 ms

    The HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 63 KiB

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

  • Font display

    350 ms

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

  • 2,977 HTML elements

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

  • Google Tag Manager adds 260 ms

    260 ms

    Google Tag Manager costs a phone 260 ms of main-thread work and 325 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.2 s

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

  • Minify CSS

    15 KiB

    15 KiB could be saved by minifying CSS.

  • Forced reflow

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

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

8 to fix100
  • 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: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Prodigy Disc”.

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Time to Interactive: 15.9 s

    15.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 387 ms

    387 ms

    Scripts block taps and scrolling for 387 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.

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 147 ms

    147 ms

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

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

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.6 MB in 118 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 118 requests on a phone: scripts 1.2 MB (38), images 1.1 MB (55) and fonts 198 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    10 KiB

    1 image is downloaded at several times the size a phone draws it, for example prodigydisc.jpg at 2,160 px wide, shown at 645 px. Resized copies would save about 10 KiB.

  • 1 image in older formats

    1 image (51 KiB) is 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.

  • About 0.8 g of CO₂ per visit

    0.75 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9696
  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Prodigystore.eu | Prodigy Disc Golf Official Online Store in Europe”.

  • Meta description is long (199 characters)

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 200 internal links, 10 external

    The homepage links to 200 pages on prodigystore.eu and 10 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Prodigy Store EU”.

  • Canonical URL set

    The canonical URL is https://prodigystore.eu/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://prodigystore.eu/sitemap.xml.

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    44%

    The HTML your server sends has 546 of the 1,241 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

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.

  • llms.txt published

    The site publishes https://prodigystore.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 2 pages share a title

    https://prodigystore.eu/collections/mystery-boxes-sets and https://prodigystore.eu/collections/disc-sets all use the title “Disc Sets & Bundles”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://prodigystore.eu/collections/black-week-2025, https://prodigystore.eu/collections/sale, https://prodigystore.eu/collections/outlet, https://prodigystore.eu/blogs/news, https://prodigystore.eu/collections/all-discs and https://prodigystore.eu/collections/all-bags and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://prodigystore.eu/collections/black-week-2025, https://prodigystore.eu/collections/sale, https://prodigystore.eu/collections/outlet, https://prodigystore.eu/collections/all-discs, https://prodigystore.eu/collections/all-bags and https://prodigystore.eu/collections/all-accessories and 8 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 89 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Refused to apply style from 'https://prodigystore.eu/cdn/shop/t/41/assets/tiny.content.min.css?v=77926' because its MIM…”.

2 checks passed
  • Tap targets are thumb-sized

    91 of 99 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 1,241 words of copy

    The homepage carries about 1,241 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “Try advanced search”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Shop our products” and “Subscribe”.

  • 4 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 6 of them by other companies (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.

  • 11 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Lieto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on prodigystore.eu, including 20 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