secondgearwnc.com website review

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

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

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

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

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

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

6 third-party services load with your homepage (Shopify, enormapps.com and nfcube.com and others), adding 551 KiB and 195 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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

Visually, the page fills in at 3.5 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 112 ms to 116 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 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.2 MB in 185 requests on a phone: images 743 KiB (24), other files 653 KiB (69) and scripts 588 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Your title is 84 characters, so Google will cut it off around 60: “Second Gear - Asheville's Outdoor Adventure Gear Consignment Store – Second Gear WNC”.

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

Your <h1> is empty.

The homepage links to 325 pages on secondgearwnc.com and 13 external pages.

https://secondgearwnc.com/products/crocs-clogs-whitechristmas-mens-9-1311b has no meta description, so Google writes the search snippet from whatever text it finds.

https://secondgearwnc.com/pages/nonprofit-program, https://secondgearwnc.com/pages/consignment-faqs, https://secondgearwnc.com/pages/discount-programs, https://secondgearwnc.com/pages/contact-us, https://secondgearwnc.com/pages/jobs and https://secondgearwnc.com/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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