studyjewelrynotes.com website review

3 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.8 s faster on a phone.

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

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

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

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

43 KiB could be saved by minifying JavaScript.

rebuyengine.com costs a phone 113 ms of main-thread work and 300 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.

8 third-party services load with your homepage (rebuyengine.com, applovin.com and Klaviyo and others), adding 684 KiB and 323 ms of main-thread time.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying CSS.

Your largest element takes 20.1 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 22.1 s. Good is under 3.8 s.

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

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

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

JewelryMakingGIF1-ezgif.com-optimize.gif weighs 4.0 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 4.5 MB in 184 requests on a phone: images 2.8 MB (9), other files 833 KiB (104) and scripts 742 KiB (59). Under 2 MB keeps phones on slow connections fast.

1 image (4.0 MB) 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.

images_15.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example hf_20260528_114406_66151087-67bb-4606-bd82-e442abb32456.png at 500 px wide, shown at 50 px. Resized copies would save about 55 KiB.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

<td> elements in a large <table> do not have table headers. (1 element).

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

Your title is only 13 characters: “Jewelry Notes”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “1.000+ Free Jewelry Making Guide”). 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 22 pages on studyjewelrynotes.com and 3 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/products/jewerlymakingnotes, /pages/portal-page, /pages/contact, /customer_authentication/redirect, /collections/all and /policies/contact-information and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/contact and /customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Social proof on the homepage: 1 testimonial or review block. 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.

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

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

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

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