jameryao.com website review

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

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

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

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

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

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

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

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

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

3 third-party services load with your homepage (Shopify, Google Fonts and placeholder.com), adding 161 KiB and 4 ms of main-thread time.

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

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 8.5 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.6 s. Good is under 3.8 s.

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

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

Your homepage downloads 4.6 MB in 120 requests on a phone: images 3.3 MB (21), other files 666 KiB (64) and fonts 286 KiB (6). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example ocean-waves-crashing.jpg at 4,096 px wide, shown at 390 px. Resized copies would save about 2.3 MB.

9 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 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: 20 elements on the page fail this check, rated moderate by axe-core.

33 visible links have no text or label, so screen readers cannot say where they go.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 10 characters: “Zhousensen”. 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.

33 links have no real href, so search engines can't follow them.

Your <h1> is empty.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 102 pages on jameryao.com and 3 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.

Your homepage links to https://jameryao.com/pages/wishlist, https://jameryao.com/pineapple-dangle-earrings-tropical-fruit-dangle-earrings-jewelry and https://jameryao.com/love-heart-dangle-earrings-gifts-jewelry-for-girl-drop-earrings, which answer with an error. Visitors hit a dead end and search engines drop them.

https://jameryao.com/collections/ring/products/zhousensen-sterling-silver-ring and https://jameryao.com/products/zhousensen-sterling-silver-ring all use the title “Zhousensen Sterling Silver Ring”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://jameryao.com/collections/all and https://jameryao.com/collections have no meta description, so Google writes the search snippet from whatever text it finds.

https://jameryao.com/collections/ring/products/zhousensen-sterling-silver-ring and https://jameryao.com/products/zhousensen-sterling-silver-ring use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://jameryao.com/collections/ring/products/zhousensen-sterling-silver-ring, whose canonical is https://jameryao.com/products/zhousensen-sterling-silver-ring. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://jameryao.com/.

4 of 10 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.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 13 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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