randco.com website review

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

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

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

8 third-party services load with your homepage (rebuyengine.com, Klaviyo and Clarity and others), adding 2.4 MB and 1.4 s of main-thread time.

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

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

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

5 images could be 492 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.

rebuyengine.com costs a phone 337 ms of main-thread work and 753 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.

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

Shopify costs a phone 162 ms of main-thread work and 797 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 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

12 KiB JavaScript is shipped twice across bundles.

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.

2 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

6 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-31, real Chrome visitors' tap response (inp) went from 125 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 20.1 MB in 591 requests on a phone: media 14.0 MB (4), scripts 2.3 MB (171) and other files 1.7 MB (333). Under 2 MB keeps phones on slow connections fast.

2 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.

2 images (4.6 MB) 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.

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 94 pages on randco.com and 16 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/holiday-kits-2026 and /customer_authentication/redirect 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 /pages/loyalty-program, whose canonical is /pages/rewards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/r-color, /pages/hair-quiz and /customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/hair-quiz and /pages/salon-locator 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 67 found) and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.randco.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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.

The homepage carries about 608 words of visible text.

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 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 24 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 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.