Website review, no card needed

randalls.com logo

randalls.com website review

Visit site (opens in a new tab)Reviewed 17 November 202650 issues · 91 checks

This review found 50 issues worth fixing on randalls.com, 23 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.6 s2.9 sMay 30Nov 144.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.4 s
Jun 20, 20263.3 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.2 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.9 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20264.2 s
Sep 19, 20264.2 s
Sep 26, 20264.2 s
Oct 3, 20264.1 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.2 s
Oct 31, 20264.3 s
Nov 7, 20264.3 s
Nov 14, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
230 ms150 msMay 30Nov 14219 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026159 ms
Jun 6, 2026162 ms
Jun 13, 2026163 ms
Jun 20, 2026167 ms
Jun 27, 2026170 ms
Jul 4, 2026172 ms
Jul 11, 2026175 ms
Jul 18, 2026179 ms
Jul 25, 2026179 ms
Aug 1, 2026178 ms
Aug 8, 2026179 ms
Aug 15, 2026177 ms
Aug 22, 2026179 ms
Aug 29, 2026181 ms
Sep 5, 2026186 ms
Sep 12, 2026191 ms
Sep 19, 2026197 ms
Sep 26, 2026203 ms
Oct 3, 2026203 ms
Oct 10, 2026202 ms
Oct 17, 2026204 ms
Oct 24, 2026210 ms
Oct 31, 2026214 ms
Nov 7, 2026221 ms
Nov 14, 2026219 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of randalls.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. randalls.com at 2.8 s2.8 s
  2. randalls.com at 5.6 s5.6 s
  3. randalls.com at 8.5 s8.5 s
  4. randalls.com at 11.3 s11.3 s
  5. randalls.com at 14.1 s14.1 s
  6. randalls.com at 16.9 s16.9 s
  7. randalls.com at 19.7 s19.7 s
  8. randalls.com at 22.5 s22.5 s

Speed

12 to fix33
  • Reduce unused JavaScript

    7.3 s · 1.5 MB

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

  • Use efficient cache lifetimes

    4.0 s · 2.2 MB

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

  • Main-thread work: 26.3 s

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

  • Reduce unused CSS

    1.1 s · 185 KiB

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

  • Mobile performance score: 33

    33/100

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

  • 5,939 HTML elements

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

  • 20 long tasks on the main thread

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

  • Improve image delivery

    1.9 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Adobe Tag Manager and Optanon and others), adding 2.1 MB and 1.1 s of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Google/Doubleclick Ads adds 719 ms

    719 ms

    Google/Doubleclick Ads costs a phone 719 ms of main-thread work and 1.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.

  • Adobe Tag Manager adds 270 ms

    270 ms

    Adobe Tag Manager costs a phone 270 ms of main-thread work and 224 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.

  • Legacy JavaScript

    150 ms · 48 KiB

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 93 ms

    93 ms

    Your server sent the HTML in 93 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix0
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.7 s

    4.7 s

    Real visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest Contentful Paint: 21.5 s

    21.5 s

    Your largest element takes 21.5 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 use cookies and other technologies to o…”.

  • Speed Index: 24.9 s

    24.9 s

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

  • Total Blocking Time: 8.5 s

    8.5 s

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

  • Time to Interactive: 42.7 s

    42.7 s

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

  • Real-user CLS: 0.12

    0.12

    For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 37% slower for real visitors

    +37%

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

  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

1 checks passed
  • Cumulative Layout Shift: 0.05

    0.05

    The layout barely moves while loading (CLS 0.05, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 6.8 MB in 282 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 282 requests on a phone: scripts 3.2 MB (79), images 2.6 MB (97) and fonts 362 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • About 1.9 g of CO₂ per visit

    1.91 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8488
  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

  • 7 tap targets too small

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 3 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (4 elements).

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (4 elements).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 10074
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (166 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 287 internal links, 42 external

    The homepage links to 287 pages on randalls.com and 42 external pages.

3 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Grocery Delivery Near You - Order Groceries Online | Randalls”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.randalls.com/shop/sitemaps/sitemap-index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.randalls.com/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,072 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix73
  • 12 pages without a title

    https://www.randalls.com/erums/store/prebook, https://www.randalls.com/customer-account/account-dashboard, https://www.randalls.com/shop/purchases/buy-it-again.html, https://www.randalls.com/order-account/orders, https://www.randalls.com/schedule-and-save/manage and https://www.randalls.com/customer-account/account-settings and 6 others have no <title>, so Google invents the link text in results.

  • 13 linked pages hidden from search

    https://www.randalls.com/lp/supported-browsers.html, https://www.randalls.com/erums/store/prebook, https://www.randalls.com/customer-account/account-dashboard, https://www.randalls.com/shop/purchases/buy-it-again.html, https://www.randalls.com/order-account/orders and https://www.randalls.com/schedule-and-save/manage and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 13 pages without a meta description

    https://www.randalls.com/lp/supported-browsers.html, https://www.randalls.com/erums/store/prebook, https://www.randalls.com/customer-account/account-dashboard, https://www.randalls.com/shop/purchases/buy-it-again.html, https://www.randalls.com/order-account/orders and https://www.randalls.com/schedule-and-save/manage and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

Best practices

3 to fixGoogle 6976
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25025198&Ver=2&mid=17f4cd11-cec3-43c2-b5c9-8982410c9ce2&bo=1&sid=33225ce0e23811f1a4529b95b1077aa9&vid=33227fe0e23811f1b7f69d63ca984659&vids=1&msclkid=N&pi=918639831&lg.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Loading the font 'data:application/font-woff;charset=utf-8;base64,d09GRgABAAAAABDkAAsAAAAAG6gAAQAAAAAAAAAAAAAAAAAAAAAAA…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    207 of 241 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • No direct contact details

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

  • About 2,137 words of copy

    The homepage carries about 2,137 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now” and “Sign up”.

  • 25 calls to action

    The homepage has 25 calls to action, for example “Buy It Again”, “Manage Schedule & Save” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel, Microsoft Ads and Pinterest Tag and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies (measured from a US location before any click).

  • 39 other companies contacted

    Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at randalls.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Imperva

Company

Founded
1966
Headquarters
Houston

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on randalls.com, including 25 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25