totalproduce.com website review

YouTube costs a phone 3.5 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 11.0 s on main-thread work while loading, 7.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

5 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.2 MB and 3.6 s of main-thread time.

2 images could be 482 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

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

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

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

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.

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 visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (2.7 s).

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

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

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

1 image is downloaded at several times the size a phone draws it, for example 294a0657-1-sm-extended-2136x1172.jpg at 2,136 px wide, shown at 366 px. Resized copies would save about 346 KiB.

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

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is 66 characters, so Google will cut it off around 60: “Total Produce | One of the World's Largest Fresh Produce Providers”.

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

Your meta description is only 32 characters: “Local at heart, global by nature”. 70 to 160 characters is enough to sell the click.

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

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 5 pages on totalproduce.com and 15 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.

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

We fetched 1 page linked from your homepage and read each the way a search engine does.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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

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 form on the homepage, so every lead has to click through to another page first.

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.

Before a visitor clicks anything, the page loads Google Ads (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 1 cookie, 1 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.