willowbythesea.com website review

The page goes through 2 redirects before it starts loading, costing about 32.7 s. Link and advertise the final URL directly.

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

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

22 images could be 636 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

About 120 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, gotolstoy.com and Yotpo and others), adding 3.7 MB and 2.5 s of main-thread time.

31 KiB could be saved by minifying JavaScript.

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

gotolstoy.com costs a phone 439 ms of main-thread work and 342 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 costs a phone 448 ms of main-thread work and 164 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.

The HTML itself could arrive about 450 ms sooner: redirects, a slow server response or missing compression delay everything after it.

rebuyengine.com costs a phone 342 ms of main-thread work and 1.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.

Yotpo costs a phone 376 ms of main-thread work and 546 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.

Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

PayPal costs a phone 306 ms of main-thread work and 392 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

6 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 54.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 25.9 MB in 543 requests on a phone: media 14.5 MB (3), images 5.1 MB (89) and scripts 3.9 MB (204). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 7.34 g of CO₂e: 880.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

14 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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. (16 elements).

Your title is only 17 characters: “Willow By The Sea”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 84 pages on willowbythesea.com and 7 external pages.

Your homepage links to https://willowbythesea.com/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

https://willowbythesea.com/blogs/stories has no meta description, so Google writes the search snippet from whatever text it finds.

https://willowbythesea.com/pages/choose-your-ritual, https://willowbythesea.com/pages/our-story, https://willowbythesea.com/blogs/stories and https://willowbythesea.com/collections have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 336 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.

Opening the homepage sets 19 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.