jtv.com website review

The page goes through 1 redirect before it starts loading, costing about 17.4 s. Link and advertise the final URL directly.

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

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

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

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

5 third-party services load with your homepage (LongTail Ad Solutions, Optanon and Tealium and others), adding 378 KiB and 59 ms of main-thread time.

About 11 KiB of CSS is downloaded but never applied on this page.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

Your largest element takes 26.5 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

Real visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 196 ms to 226 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 28.3 MB in 231 requests on a phone: images 24.0 MB (103), scripts 1.9 MB (61) and media 1.7 MB (6). Under 2 MB keeps phones on slow connections fast.

4 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.

6 images (10.9 MB) are 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.

3 images are downloaded at several times the size a phone draws them, for example one-half-content-block-holiday-lifestyle-jtvgiftbox-black.pn at 1,450 px wide, shown at 350 px. Resized copies would save about 105 KiB.

5 images further down the page (132 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 8.03 g of CO₂e: 963.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

12 links inside paragraphs rely on colour alone to stand out.

Some list items are not inside a list.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“30% OFF OR MORE” and “JTV Jewelry: Discover your Jewelry Love!”). One clear main headline is easier for people and search engines.

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

The homepage links to 768 pages on jtv.com and 7 external pages.

There is no https://www.jtv.com/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.

https://www.jtv.com/category/shop/best-sellers/_/N-1301993795 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.jtv.com/category/jewelry/gems-en-vogue/_/N-3960851931, https://www.jtv.com/category/jewelry/judith-ripka/_/N-1992601452, https://www.jtv.com/category/jewelry/lisa-mason-bella-luce/_/N-1181844395, https://www.jtv.com/category/jewelry/moissanite/moissanite-fire/_/N-4013277231 and https://www.jtv.com/category/brands/off-park/_/N-519377976 took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5060758&Ver=2&mid=7cb5b883-bb53-4d0f-bea6-6bbacc9c0b89&bo=1&sid=5b1ac4b0c5b811f1910dd5c0456d66f8&vid=5b1af610c5b811f186b8416b3382fdaf&vids=1&msclkid=N&pi=918639831&lg=.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

Social proof on the homepage: 1 trust badge. 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 shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,140 words of visible text.

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

Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 53 cookies (measured from a US location before any click).

Loading the homepage contacts 68 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.