weldingstore.com website review

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

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

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

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

15 images could be 543 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.

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

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

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

Klaviyo costs a phone 110 ms of main-thread work and 306 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.

8 third-party services load with your homepage (Affirm, Klaviyo and Shopify and others), adding 1,022 KiB and 436 ms of main-thread time.

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

5 long tasks block the main thread while loading, the longest for 156 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

Your largest element takes 10.7 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 11.5 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 3.4 MB in 236 requests on a phone: images 1.3 MB (47), other files 834 KiB (96) and scripts 817 KiB (71). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example FC_Welding-Helmets.jpg at 390 px wide, shown at 99 px. Resized copies would save about 22 KiB.

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

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“Welding Store Welding Store”, “Business Accounts Are LIVE!” and “Business Accounts Are LIVE!”). One clear main headline is easier for people and search engines.

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

The homepage links to 575 pages on weldingstore.com and 3 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.

https://www.weldingstore.com/collections/miller-electric, https://www.weldingstore.com/collections/lincoln-electric, https://www.weldingstore.com/collections/esab, https://www.weldingstore.com/collections/hobart, https://www.weldingstore.com/collections/hypertherm and https://www.weldingstore.com/collections/smith and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://wishlist.webcontrive.com/wishlist-club/public/api/v2/setting' from origin 'https://www.weld…”.

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

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

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