amchar.com website review

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

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

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

Your mobile performance score is 52 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and coreware.com and others), adding 3.3 MB and 539 ms of main-thread time.

86 KiB could be saved by minifying JavaScript.

17 images could be 479 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.

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

coreware.com costs a phone 58 ms of main-thread work and 2.6 MB 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.

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

5 KiB could be saved by minifying CSS.

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

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

Desktop scores 79 but mobile only 52. 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.

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 first text or image appears after 8.9 s on a phone. Good is under 1.8 s.

Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Closeout + Overstock Sale”.

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

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

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

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

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

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

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

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

Your homepage downloads 3.4 MB in 62 requests on a phone: images 1.5 MB (28), scripts 950 KiB (15) and fonts 743 KiB (5). Under 2 MB keeps phones on slow connections fast.

10 images (753 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.

4 images are downloaded at several times the size a phone draws them, for example image-full-12187-c5392c65a85d446f553421dfd7ebc2ad.jpg at 1,600 px wide, shown at 360 px. Resized copies would save about 206 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

7 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 only 23 characters: “Home | AmChar Wholesale”. Between 30 and 65 characters leaves room to say what you do and for whom.

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.

There is no robots.txt at amchar.com/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 116 pages on amchar.com and 5 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 /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 /home all use the title “Home | AmChar Wholesale”. Search engines can't tell which page to show for a search, so each competes with the others.

/about-us, /contact-us, /shopping-cart, /my-wish-list, /manufacturer-rebates and /become-a-dealer and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/home has no <h1> headline, so visitors and search engines get no clear main topic.

/manufacturer-rebates, /dealer-locator and /home 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 82 found) and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

Chrome logged issues while loading the page (“Content security policy”).

http://amchar.com does not redirect to https, so some visitors land on the insecure version.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

amchar.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

amchar.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 has only about 109 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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