Website review, no card needed
missionproduce.com website review
Visit site (opens in a new tab)Reviewed 18 November 202634 issues · 86 checks
This review found 34 issues worth fixing on missionproduce.com, 11 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.7 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 118 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 115 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 117 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 119 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 103 ms |
| Oct 24, 2026 | 103 ms |
| Oct 31, 2026 | 103 ms |
| Nov 7, 2026 | 105 ms |
| Nov 14, 2026 | 111 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
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Render-blocking requests
3.6 s56 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Improve image delivery
1.5 MB14 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
300 ms · 33 KiB33 KiB could be saved by minifying CSS.
Reduce unused JavaScript
295 KiBAbout 295 KiB of JavaScript is downloaded but never used on this page.
1,837 HTML elements
The page has 1,837 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Cookiebot, elementor.com and Google Tag Manager), adding 406 KiB and 275 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 97 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
58 KiB4 files are served with short cache lifetimes, so returning visitors download them again (58 KiB).
Minify JavaScript
55 KiB55 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 23.3 s
23.3 sThe page becomes fully interactive after 23.3 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”. Most of its time is element render delay (2.3 s).
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.216
0.216The layout shifts by 0.216 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 134 ms
134 msReal visitors wait 134 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 119 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 41 ms
41 msScripts block the page for only 41 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.7 MB in 188 requests
6.7 MBYour homepage downloads 6.7 MB in 188 requests on a phone: images 3.8 MB (50), scripts 1.7 MB (71) and fonts 812 KiB (9). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
hh-middle-4-768x1009.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.9 g of CO₂ per visit
1.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.91 g of CO₂e: 228.9 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
Certain ARIA roles must contain particular children (3 elements)
Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Mission Produce”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
68 internal links, 23 external
The homepage links to 68 pages on missionproduce.com and 23 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Mission Produce offers a year-round supply of the World's Finest Avocados™ and World's Finest Mangos™, currently servic…”.
One H1 headline
Your main headline reads: “The World's FinestAvocados & Mangos”.
Canonical URL set
The canonical URL is https://missionproduce.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://missionproduce.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://missionproduce.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (787 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://missionproduce.com/blog and https://missionproduce.com/mission-global have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://missionproduce.com/discover-the-mission-advantage, whose canonical is https://missionproduce.com/mission-advantage. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://missionproduce.com/products has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://missionproduce.com/discover-the-mission-advantage and https://missionproduce.com/about-us took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://missionproduce.com/.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 507 words of copy
The homepage carries about 507 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact Us” and “LEARN MORE”.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 missionproduce.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Hiring
- Hiring
- 9 open roles
- Job board
- careers page
- Careers page
- missionproduce.com/careers (opens in a new tab)
Company
- Employees
- 537
- Headquarters
- Oxnard
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on missionproduce.com, including 19 speed issues, 2 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.