boltsandnuts.com website review

23 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

6 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 2.9 MB and 351 ms of main-thread time.

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

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

cloudfront.net costs a phone 0 ms of main-thread work and 1.7 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.

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

About 162 KiB of JavaScript is downloaded but never used on this page.

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

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

About 48 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 126 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 0.9 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, Google, Meta, TikTo…”. Most of its time is element render delay (2.5 s).

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

Your homepage downloads 5.1 MB in 265 requests on a phone: images 2.9 MB (51), scripts 930 KiB (104) and other files 691 KiB (80). Under 2 MB keeps phones on slow connections fast.

0dbef73c-580e-4388-a053-c992563b68e0.png weighs 538 KiB. On a phone connection a single image that size takes seconds.

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 142 pages on boltsandnuts.com and 20 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://boltsandnuts.com/pages/b-n-racing, https://boltsandnuts.com/pages/custom-kitting-and-packaging, https://boltsandnuts.com/pages/bulk-ordering, https://boltsandnuts.com/pages/fastener-finishing-secondary-processing, https://boltsandnuts.com/pages/influencers and https://boltsandnuts.com/pages/andy-the-bolt-guy and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://boltsandnuts.com/pages/andy-the-bolt-guy, whose canonical is https://boltsandnuts.com/pages/andytheboltguy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://boltsandnuts.com/collections and https://boltsandnuts.com/pages/influencers have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

The homepage carries about 698 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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 6 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.