jenshansen.com website review

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

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

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and vercel.app and others), adding 4.4 MB and 3.2 s of main-thread time.

46 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

About 1.5 MB of JavaScript is downloaded but never used on this page.

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

Signyfyd costs a phone 973 ms of main-thread work and 281 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.

vercel.app costs a phone 435 ms of main-thread work and 2.1 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.

Google Tag Manager costs a phone 447 ms of main-thread work and 512 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.

sitestaffdigital.com costs a phone 395 ms of main-thread work and 565 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.

route.com costs a phone 315 ms of main-thread work and 542 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.

154 KiB could be saved by minifying JavaScript.

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

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

33 KiB could be saved by minifying CSS.

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.

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 page becomes fully interactive after 43.6 s. Good is under 3.8 s.

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

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

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

For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.

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

The layout shifts by 0.107 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 6.7 MB in 386 requests on a phone: scripts 5.3 MB (168), other files 767 KiB (130) and images 280 KiB (29). Under 2 MB keeps phones on slow connections fast.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 298 pages on jenshansen.com and 19 external pages.

There is no https://www.jenshansen.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.jenshansen.com/pages/payment-options, https://www.jenshansen.com/collections/makers-of-the-worlds-most-famous-ring, https://www.jenshansen.com/collections/movie-rings, https://www.jenshansen.com/collections/elvish-wedding-and-engagement-rings and https://www.jenshansen.com/collections/character-rings have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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.

The homepage carries about 895 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 44 cookies, 6 of them by other companies (measured from a US location before any click).

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