lucharkitchen.com website review

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

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (Shopify, Klaviyo and shop.app and others), adding 1.4 MB and 681 ms of main-thread time.

About 303 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

Shopify costs a phone 507 ms of main-thread work and 1,002 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.

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

Klaviyo costs a phone 167 ms of main-thread work and 308 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.

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

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

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

About 24 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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

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

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

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

Your homepage downloads 3.9 MB in 444 requests on a phone: scripts 1.5 MB (199), images 1.1 MB (24) and other files 1.0 MB (184). Under 2 MB keeps phones on slow connections fast.

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

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

Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 14 characters: “LUCHAR KITCHEN”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“”, “BEST SELLER” and “Elevate Your Space with Every Detail”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 161 pages on lucharkitchen.com and 12 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://lucharkitchen.com/collections/appliance, https://lucharkitchen.com/collections/accessories, https://lucharkitchen.com/pages/gallery, https://lucharkitchen.com/pages/about, https://lucharkitchen.com/pages/contact-us and https://lucharkitchen.com/pages/q-a and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lucharkitchen.com/pages/gallery, https://lucharkitchen.com/pages/about, https://lucharkitchen.com/pages/contact-us and https://lucharkitchen.com/pages/q-a have no <h1> headline, so visitors and search engines get no clear main topic.

https://lucharkitchen.com/collections/outdoor-kitchen-appliances, https://lucharkitchen.com/collections/fridge, https://lucharkitchen.com/collections/gas-range, https://lucharkitchen.com/collections/accessories, https://lucharkitchen.com/collections/disposal-air-switch and https://lucharkitchen.com/collections/sink-garbage-disposal-flange-stopper and 1 other took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot assign to read only property 'isDropdown' of object '#<PredictiveSearch>'”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (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 11 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.