jonesthegrocer.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 710 KiB and 626 ms of main-thread time.

Reduce initial server response time. Google estimates savings of 656 ms on a phone.

The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Google Tag Manager costs a phone 475 ms of main-thread work and 526 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, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Your server takes 756 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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

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

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.

Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Santa's grotto”. Most of its time is resource load delay (6.0 s).

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

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

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

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

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

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

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

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

9 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 109 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 images (472 KiB) 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.

2 images further down the page (169 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 0.42 g of CO₂e: 50.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

[aria-*] attributes do not have valid values (1 element).

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

ARIA input fields do not have accessible names (3 elements).

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

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

1 tap target is too small or too close together to hit reliably with a finger.

Elements with role="none" or role="presentation" have conflicts (1 element).

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

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

The homepage links to 202 pages on jonesthegrocer.com and 8 external pages.

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

https://www.jonesthegrocer.com/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.jonesthegrocer.com/wishlist and https://www.jonesthegrocer.com/map all use the title “Jones the Grocer”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jonesthegrocer.com/wishlist and https://www.jonesthegrocer.com/map have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://www.jonesthegrocer.com/shop-now-2021-i221, whose canonical is https://www.jonesthegrocer.com/shop-now-i221. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.jonesthegrocer.com/wishlist and https://www.jonesthegrocer.com/shop-now-2021-i221 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.jonesthegrocer.com/cookies, https://www.jonesthegrocer.com/map, https://www.jonesthegrocer.com/shop-now-2021-i221, https://www.jonesthegrocer.com/cheese-box-c470, https://www.jonesthegrocer.com/products-c1/from-our-cheese-room-c81 and https://www.jonesthegrocer.com/products-c1/charcuterie-deli-bakery-c87 and 8 others took over 3 s to send their HTML from our server.

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

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

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

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

The homepage has only about 175 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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