Website review, no card needed
alua.nl website review
Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 80 checks
This review found 35 issues worth fixing on alua.nl, 10 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #28,367 of 124,954 reviewed websitesbeats 72%
- #18,506 of 70,076 online storesbeats 67%
- #17,914 of 63,686 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 209 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 217 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 222 ms |
| Jun 20, 2026 | 227 ms |
| Jun 27, 2026 | 230 ms |
| Jul 4, 2026 | 237 ms |
| Jul 11, 2026 | 238 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 228 ms |
| Aug 1, 2026 | 221 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 222 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 216 ms |
| Sep 19, 2026 | 212 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 148 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 136 ms |
| Oct 31, 2026 | 136 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
Speed
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 228 KiBAbout 228 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
600 ms · 206 KiB9 images could be 206 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
650 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Klaviyo and loox.io and others), adding 753 KiB and 554 ms of main-thread time.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
250 ms · 49 KiB12 files are served with short cache lifetimes, so returning visitors download them again (49 KiB).
Legacy JavaScript
150 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Reduce unused CSS
41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page.
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.
1 checks passed
Server response: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 11.5 s
11.5 sYour largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday bij Alua”.
Time to Interactive: 11.5 s
11.5 sThe page becomes fully interactive after 11.5 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). 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.
7 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 490 ms
490 msReal visitors wait 490 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 209 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 123 ms
123 msScripts block the page for only 123 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 254 requests
2.2 MBYour homepage downloads 2.2 MB in 254 requests on a phone: scripts 789 KiB (109), other files 749 KiB (84) and images 518 KiB (27). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
62 KiB1 image is downloaded at several times the size a phone draws it, for example Kopie_van_BLISSCOL-3002_1080_x_1300_px_12_5ee3be02-8695-4021 at 1,620 px wide, shown at 390 px. Resized copies would save about 62 KiB.
1 image in older formats
1 image (178 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.
4 images below the first screen load straight away
4 images further down the page (132 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 76.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA progressbar nodes must have an accessible name (4 elements)
ARIA progressbar nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (5 characters)
Your title is only 5 characters: “Alua™”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
24 internal links, 0 external
The homepage links to 24 pages on alua.nl and 0 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.alua.nl/.
Structured data in place
Structured data found: Organization 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://www.alua.nl/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (720 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.alua.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://www.alua.nl/products/colla-bfsub and https://www.alua.nl/products/vrouwelijke-balans-sub are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://www.alua.nl/products/vrouwelijke-balans and https://www.alua.nl/products/vrouwelijke-balans-sub all use the title “Alua™ Vrouwelijke Balans Capsules”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://www.alua.nl/products/vrouwelijke-balans, https://www.alua.nl/pages/contact, https://www.alua.nl/products/vrouwelijke-balans-sub, https://www.alua.nl/policies/refund-policy, https://www.alua.nl/policies/privacy-policy and https://www.alua.nl/policies/shipping-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.alua.nl/products/colla-bfsub and https://www.alua.nl/products/sub use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.alua.nl/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.alua.nl/pages/contact and https://www.alua.nl/policies/shipping-policy 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.
8 pages slow to respond
https://www.alua.nl/products/sub, https://www.alua.nl/products/hsn, https://www.alua.nl/pages/contact, https://www.alua.nl/products/vrouwelijke-balans-sub, https://www.alua.nl/policies/refund-policy and https://www.alua.nl/policies/shipping-policy and 2 others took over 3 s to send their HTML from our server.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
12 pages of 13 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “_uxa is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
14 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 710 words of copy
The homepage carries about 710 words of visible text.
4 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Shop Intense Hydration”, “Shop Collageen” and “Shop Haar & Nagel Gummies”.
2 short forms
2 short forms (0 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Meta Pixel and Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 2 mores (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
26Opening the homepage sets 26 cookies, 2 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.
41 other companies contacted
Loading the homepage contacts 41 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 alua.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on alua.nl, including 14 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.