shopgoodwill.com website review

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

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

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

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

8 third-party services load with your homepage (intergient.com, rokt-api.com and confiant-integrations.net and others), adding 2.0 MB and 1.4 s of main-thread time.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.

intergient.com costs a phone 282 ms of main-thread work and 469 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.

rokt-api.com costs a phone 252 ms of main-thread work and 364 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 263 ms. During a long task the page ignores taps.

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

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

About 62 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.

11 KiB could be saved by minifying CSS.

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

Desktop scores 60 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

5 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “14K GOLD ROPE CHAIN NECKLACE 221G 18 READY TO WEAR”.

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

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

51 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 228 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.5 MB in 201 requests on a phone: scripts 2.5 MB (61), images 1.5 MB (67) and fonts 160 KiB (5). Under 2 MB keeps phones on slow connections fast.

c10a48df-53ce-4d17-9992-5576ccfe437dsley_1007t1.jpeg 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).

7 images further down the page (825 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example GoodwillBooks_ShopGoodwill_Logo.png at 2,158 px wide, shown at 181 px. Resized copies would save about 67 KiB.

1 image (71 KiB) is 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.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

120 links have no real href, so search engines can't follow them.

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

Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 36 pages on shopgoodwill.com and 9 external pages.

The HTML your server sends has 125 of the 398 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your Organization JSON-LD is missing name, 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.

There is no https://shopgoodwill.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.

/ and https://shopgoodwill.com/home all use the title “Online Thrift Store For Unique & Vintage Finds | ShopGoodwill.com”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://shopgoodwill.com/all-categories has no meta description, so Google writes the search snippet from whatever text it finds.

https://shopgoodwill.com/home, https://shopgoodwill.com/categories/gallery, https://shopgoodwill.com/shopgoodwill/personal-information, https://shopgoodwill.com/shopgoodwill/open-orders, https://shopgoodwill.com/shopgoodwill/shipped-orders and https://shopgoodwill.com/shopgoodwill/inprogress-auctions and 8 others use the same meta description. A description written for each page earns more clicks.

https://shopgoodwill.com/categories/gallery, https://shopgoodwill.com/shopgoodwill/personal-information, https://shopgoodwill.com/shopgoodwill/open-orders, https://shopgoodwill.com/shopgoodwill/shipped-orders, https://shopgoodwill.com/shopgoodwill/inprogress-auctions and https://shopgoodwill.com/shopgoodwill/closed-auctions and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://shopgoodwill.com/home, https://shopgoodwill.com/categories/gallery, https://shopgoodwill.com/categories/hot50 and https://shopgoodwill.com/listing/recommended 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 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

10 images failed to load on a phone, for example https://ids4.ad.gt/api/v1/ip_match?id=AU1D-0100-001791763503-F2IQKU8D-HZTM.

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Tag Manager, The Trade Desk and Xandr (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 14 cookies, 1 of them by other companies (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 63 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.