society6.com website review

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

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

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

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

20 images could be 942 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

alia-prod.com costs a phone 290 ms of main-thread work and 349 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.

Shopify costs a phone 95 ms of main-thread work and 533 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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 26.3 s. Good is under 3.8 s.

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

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

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

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

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

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

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

Your homepage downloads 5.7 MB in 411 requests on a phone: scripts 2.2 MB (145), images 1.9 MB (47) and other files 1.1 MB (190). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 1135270c50154db8bd5c4c20c1e0b342_b3f1588f-10f4-42cc-9013-496 at 700 px wide, shown at 150 px. Resized copies would save about 115 KiB.

3 images (373 KiB) 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.

1 image further down the page (31 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.61 g of CO₂e: 193.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 elements use ARIA attributes their role does not allow, which confuses screen readers.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 486 pages on society6.com and 16 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://society6.com/pages/gift-guides and https://society6.com/collections/gift-guide all use the title “Holiday Gift Guide by Independent Artists | Society6”. Search engines can't tell which page to show for a search, so each competes with the others.

https://society6.com/pages/gift-guides and https://society6.com/collections/gift-guide use the same meta description. A description written for each page earns more clicks.

https://society6.com/collections/fall, https://society6.com/pages/gift-guides, https://society6.com/collections/holiday-decor, https://society6.com/collections/holiday-decor-traditional, https://society6.com/collections/holiday-decor-vintage and https://society6.com/collections/holiday-decor-winter-wonderland and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://society6.com/collections/gift-guide-animals has 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.

https://society6.com/collections/gift-guide-the-foodie took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://i.liadm.com/s/89602?shd_id=tLDMqhxjWz0HeI8is0Tb&account_id=s6-flat-catalog.myshopify.com.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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

1 image is served at too low a resolution for sharp phone screens.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 27 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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 28 cookies (measured from a US location before any click).

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