jazzniao.com website review

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

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

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

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

6 third-party services load with your homepage (Privy, Clarity and Bootstrap CDN and others), adding 553 KiB and 1.4 s of main-thread time.

Privy costs a phone 939 ms of main-thread work and 345 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

Clarity costs a phone 431 ms of main-thread work and 29 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.

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

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

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

About 34 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.

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.

Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “*By completing this form you are signing up to receive our …”. Most of its time is resource load delay (8.6 s).

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image is downloaded at several times the size a phone draws it, for example foter.webp at 1,600 px wide, shown at 360 px. Resized copies would save about 47 KiB.

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

2 images further down the page (109 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

5 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

There are 2 <h1> headlines (“Jazzniao” and “Ice Maker (Buy 2 Get 1 Free）”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 35 pages on jazzniao.com and 0 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://www.jazzniao.com/collections/all, https://www.jazzniao.com/collections/frontpage, https://www.jazzniao.com/collections/houseware and https://www.jazzniao.com/collections/kitchen have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jazzniao.com/pages/why-choose-us and https://www.jazzniao.com/pages/test 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.

https://www.jazzniao.com/pages/returns-refunds-policy and https://www.jazzniao.com/pages/terms-of-logistics took over 3 s to send their HTML from our server.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

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

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

The homepage has only about 79 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads 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.

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