woodenwick.com website review

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

52 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Hubspot and others), adding 2.0 MB and 1.5 s of main-thread time.

4 images could be 741 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 506 ms of main-thread work and 708 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 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

48 KiB could be saved by minifying JavaScript.

Shopify costs a phone 340 ms of main-thread work and 732 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.

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

19 long tasks block the main thread while loading, the longest for 204 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).

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 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Smell More.Sell More. ”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 13.2 MB in 481 requests on a phone: media 5.8 MB (2), scripts 3.4 MB (158) and images 1.8 MB (62). Under 2 MB keeps phones on slow connections fast.

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

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

5 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 2 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 on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 426 pages on woodenwick.com and 23 external pages.

There is no https://makesy.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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://makesy.com/pages/explore, whose canonical is https://makesy.com/pages/learn-about-makesy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://makesy.com/pages/makesy-perks, https://makesy.com/pages/contact-makesy, https://makesy.com/collections/fall-collection, https://makesy.com/pages/explore, https://makesy.com/pages/swym-wishlist and https://makesy.com/collections/fragrance-oils and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56356674&Ver=2&mid=ae852658-9bd7-48e7-9d49-e54849870622&bo=1&sid=b2ad6150d99411f18214c5de46aed579&vid=b2ada040d99411f198b171b35a2c8111&vids=1&msclkid=N&pi=918639831&lg.

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

6 errors were logged to the browser console while the page loaded, for example “document.addEventListener(...) is not a function”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

5 images are served at too low a resolution for sharp phone screens.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 757 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 43 cookies (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 75 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.