sharperimage.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, withremark.com and Noibu and others), adding 2.1 MB and 2.1 s of main-thread time.

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

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

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

10 images could be 648 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

withremark.com costs a phone 464 ms of main-thread work and 656 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.

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

About 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 977 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 5.0 MB in 348 requests on a phone: scripts 2.7 MB (199), images 1.4 MB (28) and other files 726 KiB (91). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

4 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

Structured data found (OnlineStore and WebSite) but with 1 problem, for example “OnlineStore: logo is not an absolute URL ("//sharperimage.com/cdn/shop/files/si-logo.svg?v=17521570…”.

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

Your <h1> is empty.

The homepage links to 819 pages on sharperimage.com and 7 external pages.

https://sharperimage.com/collections/bestsellers, https://sharperimage.com/collections/electronics, https://sharperimage.com/collections/cell-phone-accessories, https://sharperimage.com/collections/chargers-power-adapters, https://sharperimage.com/collections/bluetooth-accessories and https://sharperimage.com/collections/photo-video and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 200 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=28479560&Ver=2&mid=98a26ecd-9f29-47d1-a2cc-287bc3936693&bo=1&sid=6db2c350d80d11f1b88b27b177758b86&vid=6db2d980d80d11f1be5d459e75059dff&vids=1&msclkid=N&page_location=h.

Large scripts ship without source maps.

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

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.

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

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