Website review, no card needed
etuhome.eu website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 89 checks
This review found 43 issues worth fixing on etuhome.eu, 16 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
3.5 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Avoid multiple page redirects
3.8 sThe page goes through 2 redirects before it starts loading, costing about 3.8 s. Link and advertise the final URL directly.
Use efficient cache lifetimes
1.1 s · 401 KiB19 files are served with short cache lifetimes, so returning visitors download them again (401 KiB).
etuhome.com adds 1.0 s
1.0 setuhome.com costs a phone 1.0 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,191 HTML elements
The page has 3,191 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 (etuhome.com, Google Tag Manager and Shopify and others), adding 5.1 MB and 2.0 s of main-thread time.
Improve image delivery
600 ms · 732 KiB10 images could be 732 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
800 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 526 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 116 KiBAbout 116 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.
Shopify adds 221 ms
221 msShopify costs a phone 221 ms of main-thread work and 929 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.
Google Tag Manager adds 264 ms
264 msGoogle Tag Manager costs a phone 264 ms of main-thread work and 353 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.
rebuyengine.com adds 114 ms
114 msrebuyengine.com costs a phone 114 ms of main-thread work and 301 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.
Legacy JavaScript
150 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
150 ms · 38 KiB38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Document request latency
100 msThe HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.
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 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.5 s
22.5 sYour largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 32.4 s
32.4 sThe page becomes fully interactive after 32.4 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 913 ms
913 msScripts block taps and scrolling for 913 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 737 ms
737 msReal visitors wait 737 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 343 requests
6.0 MBYour homepage downloads 6.0 MB in 343 requests on a phone: scripts 3.5 MB (161), images 1.0 MB (12) and other files 864 KiB (145). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 205.2 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
Images must have alternative text (24 elements)
Images must have alternative text: 24 elements on the page fail this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (24 elements)
ARIA role should be appropriate for the element: 24 elements on the page fail this check, rated minor by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“etuHome” and “Example Product Title”). One clear main headline is easier for people and search engines.
Meta description is long (214 characters)
Your meta description is 214 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
49 internal links, 8 external
The homepage links to 49 pages on etuhome.eu and 8 external pages.
5 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “etúHOME: The Inspired European Kitchen”.
Canonical URL set
The canonical URL is https://etuhome.eu/.
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://etuhome.eu/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
57%The HTML your server sends has 243 of the 430 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
3 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.
llms.txt published
The site publishes https://etuhome.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://etuhome.eu/collections/serveware, https://etuhome.eu/blogs/news, https://etuhome.eu/policies/terms-of-service, https://etuhome.eu/policies/refund-policy and https://etuhome.eu/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://etuhome.eu/pages/maintenance-care, whose canonical is https://etuhome.eu/pages/product-maintenance-and-care. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 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
37 of 37 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 430 words of copy
The homepage carries about 430 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP BLACK FRIDAY” and “Hostess Gifts SHOP NOW”.
1 call to action
The homepage has 1 call to action, for example “Subscribe”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
42 cookies set on arrival
42Opening the homepage sets 42 cookies, 7 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.
52 other companies contacted
Loading the homepage contacts 52 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 etuhome.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
klaviyo.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
- jQuery
- 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 43 issues on etuhome.eu, including 21 speed issues, 5 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.