Website review, no card needed
daniellalehavi.com website review
Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 85 checks
This review found 32 issues worth fixing on daniellalehavi.com, 11 of them high impact, across 85 checks. The most urgent: main-thread work: 14.4 s. 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
79C- #55,773 of 125,123 reviewed websitesbeats 50%
- #36,564 of 70,108 online storesbeats 42%
- #35,017 of 63,712 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 127 ms |
| May 30, 2026 | 126 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 126 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 148 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 136 ms |
| Nov 7, 2026 | 137 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.8 s
3.5 s
5.3 s
7.1 s
8.8 s
10.6 s
12.4 s
14.2 s
Speed
Main-thread work: 14.4 s
A phone's processor spends 14.4 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.2 s
1.2 sShopify costs a phone 1.2 s of main-thread work and 886 KiB 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: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and loox.io and others), adding 2.0 MB and 2.8 s of main-thread time.
Reduce unused JavaScript
150 ms · 719 KiBAbout 719 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
800 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Klaviyo adds 497 ms
497 msKlaviyo costs a phone 497 ms of main-thread work and 517 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.
loox.io adds 326 ms
326 msloox.io costs a phone 326 ms of main-thread work and 17 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 266 ms
266 msrebuyengine.com costs a phone 266 ms of main-thread work and 329 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.
2,508 HTML elements
The page has 2,508 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 251 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 116 KiBAbout 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
50 ms · 139 KiB20 files are served with short cache lifetimes, so returning visitors download them again (139 KiB).
Improve image delivery
50 ms · 57 KiB4 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
80 KiBPolyfills for old browsers add 80 KiB JavaScript that modern phones do not need.
Minify CSS
13 KiB13 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 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 24.2 s
24.2 sThe page becomes fully interactive after 24.2 s. Good is under 3.8 s.
Largest Contentful Paint: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 127 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 641 ms
641 msReal visitors wait 641 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 447 requests
4.7 MBYour homepage downloads 4.7 MB in 447 requests on a phone: scripts 2.2 MB (216), images 981 KiB (38) and other files 976 KiB (155). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 159.0 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
218 links without text
218 visible links have no text or label, so screen readers cannot say where they go.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 219 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (208 characters)
Your meta description is 208 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
297 internal links, 4 external
The homepage links to 297 pages on daniellalehavi.com and 4 external pages.
5 checks passed
Title: 37 characters
Your title is a healthy 37 characters: “Daniella Lehavi – Daniella Lehavi USA”.
Canonical URL set
The canonical URL is https://daniellalehavi.com/.
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://daniellalehavi.com/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 (337 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://daniellalehavi.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://daniellalehavi.com/pages/newsletter, https://daniellalehavi.com/pages/daniella-lehavi-founder, https://daniellalehavi.com/collections/new-arrival-bags-1, https://daniellalehavi.com/collections/leather-bags, https://daniellalehavi.com/pages/dani and https://daniellalehavi.com/collections/all-accessories and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://daniellalehavi.com/pages/newsletter, https://daniellalehavi.com/pages/shipping-and-returns, https://daniellalehavi.com/pages/daniella-lehavi-founder, https://daniellalehavi.com/collections/new-arrival-bags-1, https://daniellalehavi.com/collections/leather-bags and https://daniellalehavi.com/pages/dani and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://daniellalehavi.com/collections/new-arrival-bags-1, https://daniellalehavi.com/collections/leather-bags, https://daniellalehavi.com/collections/best-sellers and https://daniellalehavi.com/collections/core-2026-collection 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 57 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 JavaScript errors while loading
3 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 ()”.
2 checks passed
Tap targets are thumb-sized
208 of 213 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 167 words
The homepage has only about 167 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.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Sign Up & Get 10% Off”, “Track My Order” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 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.
36 other companies contacted
Loading the homepage contacts 36 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 daniellalehavi.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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Rebuy Personalization Engine · Inbox · C Edd Estimated Delivery Date · Ta Labels Badges · Videowise Video Commerce · Shinetrust Product Badges · Triplewhale · Swatch King · Eg Auto Add To Cart · Klaviyo Email Marketing Sms · Reelup Shoppable Videos Reels · Easylocation · Ldt Gift Wrap · Accessibility Assistant · 506.io · loox.io · rebuyengine.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
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Tel Aviv-Yafo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on daniellalehavi.com, including 15 speed issues, 4 SEO issues and 4 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.