schecterguitars.com website review

10 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.3 s faster on a phone.

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

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

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

About 444 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

YouTube costs a phone 1.2 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and SnapWidget and others), adding 2.8 MB and 2.0 s of main-thread time.

Google Tag Manager costs a phone 491 ms of main-thread work and 534 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 287 ms. During a long task the page ignores taps.

25 KiB could be saved by minifying JavaScript.

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

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

9 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.

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

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

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

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

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

Your largest element takes 90.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 24.7 s (Speed Index). Good is under 3.4 s.

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

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

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

13 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-17, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 69.9 MB in 312 requests on a phone: images 65.8 MB (226), scripts 3.0 MB (35) and stylesheets 450 KiB (15). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example USA 50th Banner History.jpg at 5,000 px wide, shown at 390 px. Resized copies would save about 5.6 MB.

5 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.

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

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

18 tap targets are too small or too close together to hit reliably with a finger.

15 elements hidden from screen readers can still receive keyboard focus.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 71 characters, so Google will cut it off around 60: “Schecter Guitars. Handmade, Custom Model Guitar Manufacturer since 1976”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No XML sitemap at https://www.schecterguitars.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 132 pages on schecterguitars.com and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.schecterguitars.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.schecterguitars.com/cookie-policy, https://www.schecterguitars.com/guitars/2026, https://www.schecterguitars.com/guitars/50th-anniversary-collection, https://www.schecterguitars.com/guitars/6-string, https://www.schecterguitars.com/guitars/7-string and https://www.schecterguitars.com/guitars/8-string and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.schecterguitars.com/cookie-policy, https://www.schecterguitars.com/guitars/2026, https://www.schecterguitars.com/guitars/50th-anniversary-collection, https://www.schecterguitars.com/guitars/6-string, https://www.schecterguitars.com/guitars/7-string and https://www.schecterguitars.com/guitars/8-string and 9 others all use the title “Shopping”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.schecterguitars.com/cookie-policy, https://www.schecterguitars.com/guitars/2026, https://www.schecterguitars.com/guitars/50th-anniversary-collection, https://www.schecterguitars.com/guitars/6-string, https://www.schecterguitars.com/guitars/7-string and https://www.schecterguitars.com/guitars/8-string and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.schecterguitars.com/cookie-policy, https://www.schecterguitars.com/guitars/2026, https://www.schecterguitars.com/guitars/50th-anniversary-collection, https://www.schecterguitars.com/guitars/6-string, https://www.schecterguitars.com/guitars/7-string and https://www.schecterguitars.com/guitars/8-string 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 110 found) and read each the way a search engine does.

15 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://765602.app.netsuite.com/core/media/media.nl?id=45271&c=765602&h=c6fad78c7c12c2db8c…”.

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.

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.

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.

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

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