sunkist.com website review

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

2 third-party services load with your homepage (craft.cloud and Google Fonts), adding 16.3 MB and 88 ms of main-thread time.

craft.cloud costs a phone 88 ms of main-thread work and 16.2 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.

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

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 16.3 MB in 44 requests on a phone: media 14.8 MB (7), images 1.3 MB (26) and scripts 84 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example row_3_col_1.webp at 1,920 px wide, shown at 585 px. Resized copies would save about 184 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The homepage links to 59 pages on sunkist.com and 23 external pages.

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

/ and https://sunkist.com/en-us all use the title “Welcome to the Co-op! | Sunkist Growers”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sunkist.com/en-us, https://sunkist.com/en-us/about-us, https://sunkist.com/en-us/our-citrus, https://sunkist.com/en-us/recipes, https://sunkist.com/en-us/segments and https://sunkist.com/en-us/where-to-buy and 9 others use the same meta description. A description written for each page earns more clicks.

https://sunkist.com/en-us/where-to-buy has 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.

https://sunkist.com/en-us/recipes, https://sunkist.com/en-us/where-to-buy and https://sunkist.com/en-us/our-citrus/navels took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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.

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