reedsms.com website review

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

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

15 images could be 993 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.1 s faster on a phone.

512 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

8 third-party services load with your homepage (route.com, Google CDN and Accessibe Accessibility Overlay and others), adding 2.3 MB and 1.2 s of main-thread time.

route.com costs a phone 743 ms of main-thread work and 1.1 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.

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

About 78 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.

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

Google CDN costs a phone 188 ms of main-thread work and 297 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.

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

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

Your largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Since 1905 Reed's has been dedicated to delivering confiden…”.

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

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

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

27 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' tap response (inp) went from 107 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.9 MB in 311 requests on a phone: scripts 2.3 MB (102), images 1.3 MB (29) and other files 957 KiB (150). Under 2 MB keeps phones on slow connections fast.

Reeds_Tecovas__Mobile_Banner.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images further down the page (68 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

Your title is only 18 characters: “Welcome to Reed's!”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

The homepage links to 251 pages on reedsms.com and 19 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://reedsms.com/collections/all-products, https://reedsms.com/collections/shoes, https://reedsms.com/collections/mens-footwear, https://reedsms.com/collections/womens-footwear, https://reedsms.com/collections/childrens-footwear and https://reedsms.com/collections/socks and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://reedsms.com/collections/all-products, https://reedsms.com/collections/shoes, https://reedsms.com/collections/mens-footwear, https://reedsms.com/collections/womens-footwear, https://reedsms.com/collections/childrens-footwear and https://reedsms.com/collections/socks and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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