johnnydang.shop website review

Shopify costs a phone 6.2 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Shopify, vitals.app and nice-team.net and others), adding 2.1 MB and 6.7 s of main-thread time.

32 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

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

About 826 KiB of JavaScript is downloaded but never used on this page.

vitals.app costs a phone 307 ms of main-thread work and 297 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 76 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

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

44 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 24 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.

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

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

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

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

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 22.9 MB in 537 requests on a phone: media 14.4 MB (5), images 4.8 MB (51) and scripts 1.9 MB (203). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ChatGPT_Image_Mar_4_2026_05_13_24_PM.png at 389 px wide, shown at 80 px. Resized copies would save about 66 KiB.

1 image further down the page (107 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

Your canonical URL points to johnnydangandco.com, not johnnydang.shop, so Google may credit that host instead.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 94 pages on johnnydang.shop and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://johnnydang.shop/collections/chains-1 and https://johnnydang.shop/collections/chains-all all use the title “Chains – Johnny Dang & Co”. Search engines can't tell which page to show for a search, so each competes with the others.

https://johnnydang.shop/pages/about-us-1, https://johnnydang.shop/collections/pendants-1, https://johnnydang.shop/collections/chains-1, https://johnnydang.shop/collections/bracelet, https://johnnydang.shop/collections/valentines-collection and https://johnnydang.shop/collections/chains-all and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://johnnydang.shop/pages/about-us-1, https://johnnydang.shop/collections/pendants-1, https://johnnydang.shop/collections/chains-1, https://johnnydang.shop/collections/bracelet, https://johnnydang.shop/collections/valentines-collection and https://johnnydang.shop/collections/chains-all and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://johnnydang.shop/collections/chains-all has 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://johnnydang.shop/pages/about-us-1, https://johnnydang.shop/collections/chains-1, https://johnnydang.shop/collections/bracelet and https://johnnydang.shop/pages/book-appointment took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

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