Website review, no card needed
elaha.nl website review
Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 76 checks
This review found 33 issues worth fixing on elaha.nl, 8 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
88B- #5,239 of 108,955 reviewed websitesbeats 93%
- #2,908 of 61,775 online storesbeats 93%
- #2,825 of 56,370 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 962 ms |
| Sep 5, 2026 | 959 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 962 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 89 ms |
| Sep 26, 2026 | 90 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 87 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
Render-blocking requests
1.4 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Reduce unused JavaScript
869 KiBAbout 869 KiB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, bestfreecdn.com and nice-team.net and others), adding 1.1 MB and 647 ms of main-thread time.
Shopify adds 444 ms
444 msShopify costs a phone 444 ms of main-thread work and 557 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.
Improve image delivery
386 KiB11 images could be 386 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 923 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
301 KiB11 files are served with short cache lifetimes, so returning visitors download them again (301 KiB).
2,336 HTML elements
The page has 2,336 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Reduce unused CSS
131 KiBAbout 131 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
84 KiB84 KiB could be saved by minifying JavaScript.
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 CSS
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Server response: 43 ms
43 msYour server sent the HTML in 43 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 10.8 s
10.8 sThe page becomes fully interactive after 10.8 s. Good is under 3.8 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 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
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 80 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.5 s
0.5 sReal visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 152 ms
152 msScripts block the page for only 152 ms while loading. Good is under 200 ms.
Largest Contentful Paint: 1.8 s
1.8 sYour largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “HERFSTCOLLECTIE 2026”.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 214 requests
5.4 MBYour homepage downloads 5.4 MB in 214 requests on a phone: media 2.2 MB (1), scripts 1.1 MB (48) and other files 1.1 MB (129). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
ARIA toggle fields must have an accessible name (48 elements)
ARIA toggle fields must have an accessible name: 48 elements on the page fail this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 5 mores 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: “Elaha”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
48 internal links, 0 external
The homepage links to 48 pages on elaha.nl and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Elaha”.
Canonical URL set
The canonical URL is https://elaha.nl/.
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://elaha.nl/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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://elaha.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and https://elaha.nl/apps/parcelpanel all use the title “Elaha”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://elaha.nl/collections/volledige-collectie, https://elaha.nl/collections/jassen, https://elaha.nl/collections/long-sleeves, https://elaha.nl/collections/setjes, https://elaha.nl/collections/zwemkleding and https://elaha.nl/collections/jurken and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://elaha.nl/collections/new-in/products/short-sleeve-belt-dress, whose canonical is https://elaha.nl/products/short-sleeve-belt-dress. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://elaha.nl/collections/volledige-collectie, https://elaha.nl/collections/jassen, https://elaha.nl/collections/long-sleeves, https://elaha.nl/collections/setjes, https://elaha.nl/collections/zwemkleding and https://elaha.nl/collections/jurken and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://elaha.nl/apps/parcelpanel has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
20 of 22 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.
Thin social proof
Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 146 words
The homepage has only about 146 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “CONTACT”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
17 other companies contacted
Loading the homepage contacts 17 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 elaha.nl, 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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Optis Color Swatch · Snap Cart Drawer · Mintt Tiktok Feed · Hoppy Popups · Bundler Bundles App · nfcube.com · bestfreecdn.com
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
- 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 33 issues on elaha.nl, including 11 speed issues, 3 SEO issues and 5 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.