jpatchdesigns.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.4 s faster on a phone.

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

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

Squarespace costs a phone 1.2 s of main-thread work and 1.3 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.

About 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 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 5.0 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Squarespace, Google CDN and Google Maps and others), adding 4.7 MB and 2.2 s of main-thread time.

Google CDN costs a phone 665 ms of main-thread work and 736 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.

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

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 2.2 MB 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.

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 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A display of eight necklaces with diamond pendants, arrange…”.

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

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

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

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

1 image 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 5.3 MB in 104 requests on a phone: scripts 2.2 MB (62), images 2.1 MB (13) and other files 487 KiB (7). Under 2 MB keeps phones on slow connections fast.

J+Patch+Web+Banners+(2500+x+1500+px)+(1).png 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 further down the page (212 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 1.49 g of CO₂e: 178.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 5 <h1> headlines (“The J Patch Designs Story”, “Choose From Different Designs” and “Customize Your Jewelry |”). One clear main headline is easier for people and search engines.

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

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6901ea86f158a9044f6…”.

The homepage links to 38 pages on jpatchdesigns.com and 10 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.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to /rings, which answers with an error. Visitors hit a dead end and search engines drop it.

/by-category, /blog, /collections/custom-jewelry and /collections/birthstones have no meta description, so Google writes the search snippet from whatever text it finds.

/shop, /collections/custom-jewelry and /collections/birthstones have no <h1> headline, so visitors and search engines get no clear main topic.

/contact and /blog 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.

We fetched 10 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 “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/6901ea86f158a9044f61015b/19/5c5a…”.

1 link from your homepage to your own site is broken, for example https://www.jpatchdesignsbykaren.com/rings (404).

1 link to other sites is dead, for example https://jpatchdesigns.com/apps/jewelry-patch/titanium-polish-finish/rings/profiles/D/widths/7/ring_materials/T?ring_finish=POLISH&finish_type=F&size=10&feature_group=G%2CN&groove_style=N&groove_group=13-N&grooves=13-N_14KY_POLISH&sleeve=NONE (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

Opening https://jpatchdesigns.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

jpatchdesignsbykaren.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 form on the homepage, so every lead has to click through to another page first.

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 1,310 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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