Website review, no card needed

galialahav.com logo

galialahav.com website review

Visit site (opens in a new tab)Reviewed 20 October 202642 issues · 92 checks

This review found 42 issues worth fixing on galialahav.com, 20 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.1 s1.1 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.6 s
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20265.3 s
Jun 13, 20265.4 s
Jun 20, 20265.5 s
Jun 27, 20265.5 s
Jul 4, 20264.6 s
Jul 11, 20264.7 s
Jul 18, 20265.2 s
Jul 25, 20265.3 s
Aug 1, 20265.2 s
Aug 8, 20265.0 s
Aug 15, 20264.4 s
Aug 22, 20264.1 s
Aug 29, 20263.4 s
Sep 5, 20262.1 s
Sep 12, 20261.9 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
188 ms95 msMay 2Oct 17170 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026112 ms
May 16, 2026110 ms
May 23, 2026107 ms
May 30, 2026106 ms
Jun 6, 2026122 ms
Jun 13, 2026129 ms
Jun 20, 2026135 ms
Jun 27, 2026137 ms
Jul 4, 2026135 ms
Jul 11, 2026137 ms
Jul 18, 2026150 ms
Jul 25, 2026152 ms
Aug 1, 2026159 ms
Aug 8, 2026155 ms
Aug 15, 2026150 ms
Aug 22, 2026152 ms
Aug 29, 2026146 ms
Sep 5, 2026145 ms
Sep 12, 2026154 ms
Sep 19, 2026169 ms
Sep 26, 2026175 ms
Oct 3, 2026177 ms
Oct 10, 2026177 ms
Oct 17, 2026170 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

Full-page screenshot of galialahav.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. galialahav.com at 1.0 s1.0 s
  2. galialahav.com at 1.9 s1.9 s
  3. galialahav.com at 2.9 s2.9 s
  4. galialahav.com at 3.9 s3.9 s
  5. galialahav.com at 4.8 s4.8 s
  6. galialahav.com at 5.8 s5.8 s
  7. galialahav.com at 6.8 s6.8 s
  8. galialahav.com at 7.7 s7.7 s

Speed

14 to fix29
  • Reduce unused JavaScript

    1.9 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • audioeye-services.com adds 3.0 s

    3.0 s

    audioeye-services.com costs a phone 3.0 s of main-thread work and 297 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.

  • Use efficient cache lifetimes

    1.0 s · 568 KiB

    31 files are served with short cache lifetimes, so returning visitors download them again (568 KiB).

  • Main-thread work: 14.4 s

    A phone's processor spends 14.4 s on main-thread work while loading, 9.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Sentry adds 1.1 s

    1.1 s

    Sentry costs a phone 1.1 s of main-thread work and 95 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.

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 537 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: 29

    29/100

    Your mobile performance score is 29 (desktop: 60). 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 (audioeye-services.com, Sentry and Google Tag Manager and others), adding 8.1 MB and 6.3 s of main-thread time.

  • Improve image delivery

    900 ms · 342 KiB

    4 images could be 342 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 893 ms. During a long task the page ignores taps.

  • Vimeo adds 246 ms

    246 ms

    Vimeo costs a phone 246 ms of main-thread work and 6.0 MB 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.

  • Render-blocking requests

    800 ms

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Hotjar adds 478 ms

    478 ms

    Hotjar costs a phone 478 ms of main-thread work and 64 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,962 HTML elements

    The page has 2,962 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    240 ms · 66 KiB

    About 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 240 ms faster on a phone.

  • Minify JavaScript

    60 KiB

    60 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    46 KiB

    Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 60 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 21 ms

    21 ms

    Your server sent the HTML in 21 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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: 13.2 s

    13.2 s

    Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, use cookies and oth…”.

  • Time to Interactive: 32.4 s

    32.4 s

    The page becomes fully interactive after 32.4 s. Good is under 3.8 s.

  • Total Blocking Time: 3.1 s

    3.1 s

    Scripts block taps and scrolling for 3.1 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 10.2 s

    10.2 s

    Visually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 4.1 s

    4.1 s

    The first text or image appears after 4.1 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.5 s

    3.5 s

    Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 55% slower for real visitors

    +55%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

5 checks passed
  • Real-user INP: 164 ms

    164 ms

    Real visitors wait 164 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 501 ms

    501 ms

    Real visitors wait 501 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 50% faster for real visitors

    -50%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 10.6 MB in 298 requests

    10.6 MB

    Your homepage downloads 10.6 MB in 298 requests on a phone: other files 6.4 MB (149), scripts 3.0 MB (105) and images 961 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (71 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.

  • About 3.0 g of CO₂ per visit

    3.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.02 g of CO₂e: 362.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 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

8 to fixGoogle 9390
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 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 71 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 148 internal links, 13 external

    The homepage links to 148 pages on galialahav.com and 13 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Discover the world of Galia Lahav House of Couture. Luxury bridal gowns and exquisite wedding dresses. Check out our fl…”.

  • One H1 headline

    Your main headline reads: “Galia Lahav”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “GALIA LAHAV: Luxury Wedding Dresses | Bridal Gowns”.

  • Canonical URL set

    The canonical URL is https://www.galialahav.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.galialahav.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.galialahav.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,072 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.galialahav.com/collections/shop-online has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    6 pages of 15 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 meta description

    All 6 pages that loaded have a meta description.

  • 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 6 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://ib.adnxs.com/setuid?entity=315&code=-Wd6zD1Vftr_Dh9h3QDsrtYb6LCz8POKJr3CHTbJbR4&consent=1.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 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 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    35 of 43 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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 219 words

    The homepage has only about 219 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
  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop All”, “Shop Bridal” and “Book an appointment”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Taboola and 1 more (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 5 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.

  • 53 other companies contacted

    Loading the homepage contacts 53 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 galialahav.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on galialahav.com, including 23 speed 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25