Website review, no card needed
hausofval.com website review
Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 86 checks
This review found 30 issues worth fixing on hausofval.com, 12 of them high impact, across 86 checks. The most urgent: page weight: 5.9 MB in 368 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
89B- #3,685 of 117,615 reviewed websitesbeats 95%
- #1,903 of 66,923 online storesbeats 95%
- #1,847 of 61,018 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 956 ms |
| May 23, 2026 | 952 ms |
| May 30, 2026 | 934 ms |
| Jun 6, 2026 | 935 ms |
| Jun 13, 2026 | 928 ms |
| Jun 20, 2026 | 946 ms |
| Jun 27, 2026 | 958 ms |
| Jul 4, 2026 | 947 ms |
| Jul 11, 2026 | 968 ms |
| Jul 18, 2026 | 961 ms |
| Jul 25, 2026 | 946 ms |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| 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.0 s |
| Oct 17, 2026 | 974 ms |
| Oct 24, 2026 | 932 ms |
| Oct 31, 2026 | 906 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 95 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 105 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 215 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 103 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
How it loaded on a phone
1.0 s
2.0 s
2.9 s
3.9 s
4.9 s
5.9 s
6.8 s
7.8 s
Speed
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 914 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,529 HTML elements
The page has 3,529 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
2.0 MB20 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Shopify adds 105 ms
105 msShopify costs a phone 105 ms of main-thread work and 548 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.
3 third-party services on the page
3 third-party services load with your homepage (Privy, Shopify and shop.app), adding 781 KiB and 241 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.
Reduce unused JavaScript
116 KiBAbout 116 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
31 KiB8 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).
Reduce unused CSS
18 KiBAbout 18 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.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
2 checks passed
Mobile performance score: 91
91/100Your mobile performance score is 91. That is in Google's “good” band (90 and up).
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.5 s
9.5 sThe page becomes fully interactive after 9.5 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 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 FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 562 ms
562 msReal visitors wait 562 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.021
0.021The layout barely moves while loading (CLS 0.021, good is under 0.1).
Largest Contentful Paint: 1.4 s
1.4 sYour largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “At Haus of Val, we don't just blend fragrances; we create u…”.
Total Blocking Time: 42 ms
42 msScripts block the page for only 42 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.9 MB in 368 requests
5.9 MBYour homepage downloads 5.9 MB in 368 requests on a phone: images 3.7 MB (29), other files 944 KiB (160) and scripts 733 KiB (140). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Candy_Corn_Soap_Joins_the_Collection.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.7 g of CO₂ per visit
1.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 201.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
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 (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
61 form fields without a label
61 form fields have no label, so screen readers announce an empty box and autofill guesses.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (10 elements)
Headings should not be empty: 10 elements on the page fail this check, rated minor 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.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 73 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
235 internal links, 9 external
The homepage links to 235 pages on hausofval.com and 9 external pages.
8 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Explore Haus of Val for eco-friendly and organic products. Discover skincare, wellness, and lifestyle essentials crafte…”.
One H1 headline
Your main headline reads: “Haus of Val”.
Title: 51 characters
Your title is a healthy 51 characters: “Haus of Val | Your Go-To Store for Natural Products”.
Canonical URL set
The canonical URL is https://www.hausofval.com/.
Structured data in place
Structured data found: 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://www.hausofval.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,811 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hausofval.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://www.hausofval.com/pages/how-i-found-my-breast-cancer-and-the-healing-that-followed and https://www.hausofval.com/collections/the-oud-edit/OUD, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page points its canonical at the homepage
https://www.hausofval.com/products/aunt-vals-pics-special declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.hausofval.com/products/aunt-vals-pics-special all use the title “Haus of Val | Your Go-To Store for Natural Products”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.hausofval.com/blogs/news and https://www.hausofval.com/collections/hair-products have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.hausofval.com/pages/about has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.hausofval.com/collections/new-lines took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 82 found) and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
57 of 64 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: 19 testimonial or review blocks. 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
About 1,152 words of copy
The homepage carries about 1,152 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
26 calls to action
The homepage has 26 calls to action, for example “Gourmand Shop”, “Aunt Val's Shop” and “Contact”.
6 short forms
6 short forms (3 fields at most) are right on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Meta Pixel and TikTok 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
8 other companies contacted
Loading the homepage contacts 8 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 hausofval.com, 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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gempages Builder · privy.com · cloudfront.net · Swym Wishlist Plus
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
- Tailwind CSS
- 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 30 issues on hausofval.com, including 7 speed issues, 1 SEO issue and 3 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.