Website review, no card needed

welleco.eu logo

welleco.eu website review

Visit site (opens in a new tab)Reviewed 5 November 202640 issues · 90 checks

This review found 40 issues worth fixing on welleco.eu, 14 of them high impact, across 90 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
3.1 s2.4 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
320 ms245 msMay 16Oct 31281 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026275 ms
May 23, 2026275 ms
May 30, 2026269 ms
Jun 6, 2026263 ms
Jun 13, 2026254 ms
Jun 20, 2026256 ms
Jun 27, 2026279 ms
Jul 4, 2026296 ms
Jul 11, 2026310 ms
Jul 18, 2026308 ms
Jul 25, 2026302 ms
Aug 1, 2026304 ms
Aug 8, 2026309 ms
Aug 15, 2026311 ms
Aug 22, 2026306 ms
Aug 29, 2026307 ms
Sep 5, 2026302 ms
Sep 12, 2026296 ms
Sep 19, 2026297 ms
Sep 26, 2026276 ms
Oct 3, 2026271 ms
Oct 10, 2026261 ms
Oct 17, 2026262 ms
Oct 24, 2026276 ms
Oct 31, 2026281 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 welleco.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. welleco.eu at 1.2 s1.2 s
  2. welleco.eu at 2.4 s2.4 s
  3. welleco.eu at 3.6 s3.6 s
  4. welleco.eu at 4.8 s4.8 s
  5. welleco.eu at 6.0 s6.0 s
  6. welleco.eu at 7.2 s7.2 s
  7. welleco.eu at 8.4 s8.4 s
  8. welleco.eu at 9.5 s9.5 s

Speed

14 to fix47
  • Render-blocking requests

    1.6 s

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

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

  • Main-thread work: 6.0 s

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

  • 4,113 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, Shopify and Klaviyo and others), adding 2.7 MB and 1.3 s of main-thread time.

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    150 ms · 696 KiB

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

  • Use efficient cache lifetimes

    764 KiB

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

  • Reduce unused CSS

    300 ms · 134 KiB

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

  • alia-prod.com adds 352 ms

    352 ms

    alia-prod.com costs a phone 352 ms of main-thread work and 741 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.

  • Shopify adds 282 ms

    282 ms

    Shopify costs a phone 282 ms of main-thread work and 437 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.

  • 14 long tasks on the main thread

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

  • Klaviyo adds 181 ms

    181 ms

    Klaviyo costs a phone 181 ms of main-thread work and 518 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.

  • siena.cx adds 62 ms

    62 ms

    siena.cx costs a phone 62 ms of main-thread work and 416 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.

  • Font display

    150 ms

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

  • Legacy JavaScript

    68 KiB

    Polyfills for old browsers add 68 KiB JavaScript that modern phones do not need.

  • Minify CSS

    23 KiB

    23 KiB could be saved by minifying CSS.

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 27.7 s

    27.7 s

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

  • Speed Index: 13.2 s

    13.2 s

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

  • Largest Contentful Paint: 5.5 s

    5.5 s

    Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Simple routine. Complex benefits.”.

  • Total Blocking Time: 750 ms

    750 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 193 ms

    193 ms

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

  • Real-user CLS: 0.08

    0.08

    For real visitors the layout shifts by 0.08 (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.

  • Real-user TTFB: 223 ms

    223 ms

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

  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

1 to fix70
  • Page weight: 13.0 MB in 480 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 480 requests on a phone: media 6.8 MB (3), scripts 2.6 MB (187) and images 1.8 MB (45). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (106 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.

  • About 3.7 g of CO₂ per visit

    3.69 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

9 to fixGoogle 8490
  • Certain ARIA roles must contain particular children (1 element)

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 33 form fields without a label

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

  • 21 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9286
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.welleco.com.au/)”.

  • 161 internal links, 21 external

    The homepage links to 161 pages on welleco.eu and 21 external pages.

6 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Discover nourishing beauty and wellness supplements to help you glow from inside out. Enjoy free shipping on orders €10…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “WelleCo Europe | Beauty and Wellness Supplements – WelleCo EU”.

  • Canonical URL set

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

  • 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://welleco.eu/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://welleco.eu/collections/minis has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://welleco.eu/products/welleco-super-elixir-greens and https://welleco.eu/products/the-evening-elixir have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://welleco.eu/collections/subscribe-and-thrive, https://welleco.eu/collections/all, https://welleco.eu/products/the-evening-elixir, https://welleco.eu/collections/menopause, https://welleco.eu/collections/protein and https://welleco.eu/collections/sleep took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 17 small tap targets

    17 of 70 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 (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

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

    The homepage carries about 453 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: “SUBSCRIBE & SAVE 20%” and “START TODAY”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “SHOP ALL”, “Subscribe & Save Up To 25%” and “Shop All”.

  • 41 short forms

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

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks, 6 customer or partner logos, a star rating and 13 trust badges.

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

  • 26 cookies set on arrival

    26

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

  • 49 other companies contacted

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

Apps on your store

Your storefront loads 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Tapcart Mobile App · Variant Image Wizard Swatch · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Okendo · Instafeed · Hulk Form Builder · Profy Announcement Bar · Gdpr Backpack · Rivo Loyalty Rewards Referrals · Revoq Eu Withdrawal Button · gorgias.chat · rechargecdn.com · 9gtb.com · googleapis.com · siena.cx

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

  • The footer still says © 2025.

Stack

Framework
Bootstrap
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on welleco.eu, including 20 speed issues, 2 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