Website review, no card needed
2harvest.org website review
Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 94 checks
This review found 38 issues worth fixing on 2harvest.org, 12 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 209 ms |
| May 23, 2026 | 209 ms |
| May 30, 2026 | 206 ms |
| Jun 6, 2026 | 211 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 209 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 211 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 220 ms |
| Aug 22, 2026 | 233 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 243 ms |
| Sep 12, 2026 | 238 ms |
| Sep 19, 2026 | 228 ms |
| Sep 26, 2026 | 211 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 206 ms |
| Oct 24, 2026 | 219 ms |
| Oct 31, 2026 | 218 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.9 s · 903 KiBAbout 903 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 675 KiB36 files are served with short cache lifetimes, so returning visitors download them again (675 KiB).
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Tealium and others), adding 2.7 MB and 1.6 s of main-thread time.
Google Tag Manager adds 926 ms
926 msGoogle Tag Manager costs a phone 926 ms of main-thread work and 1.4 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.
Improve image delivery
450 ms · 549 KiB9 images could be 549 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.
Legacy JavaScript
300 ms · 59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Facebook adds 306 ms
306 msFacebook costs a phone 306 ms of main-thread work and 451 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
FontAwesome CDN adds 50 ms
50 msFontAwesome CDN costs a phone 50 ms of main-thread work and 430 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 178 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 2 KiB2 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two Children holding apples in front of refridgerator displ…”.
Time to Interactive: 27.8 s
27.8 sThe page becomes fully interactive after 27.8 s. Good is under 3.8 s.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 554 ms
554 msScripts block taps and scrolling for 554 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 209 ms to 218 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 504 ms
504 msReal visitors wait 504 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 190 requests
4.1 MBYour homepage downloads 4.1 MB in 190 requests on a phone: scripts 3.0 MB (63), images 677 KiB (49) and fonts 398 KiB (7). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (626 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.
7 images far larger than shown
210 KiB7 images are downloaded at several times the size a phone draws them, for example CM6A0177.jpg at 800 px wide, shown at 203 px. Resized copies would save about 210 KiB.
1 image below the first screen load straight away
1 image further down the page (64 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (78 characters)
Your title is 78 characters, so Google will cut it off around 60: “Second Harvest Heartland | Local Minnesota, Wisconsin food bank | 2harvest.org”.
Meta description is long (364 characters)
Your meta description is 364 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
57 internal links, 24 external
The homepage links to 57 pages on 2harvest.org and 24 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Everyone Deserves to Eat”.
Canonical URL set
The canonical URL is https://www.2harvest.org/.
Structured data in place
Structured data found: LocalBusiness.
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://2harvest.org/sitemap.xml.
AI search readiness
robots.txt blocks 2 AI answer engine crawlers
2 of 6Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No llms.txt
There is no https://www.2harvest.org/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.
Opted out of AI training for 3 crawlers
robots.txt blocks GPTBot, ClaudeBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
2 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,000 words), so crawlers that don't run JavaScript still read it.
Other pages
13 pages without a meta description
https://www.2harvest.org/find-food/snap, https://www.2harvest.org/find-food/csfpnaps, https://www.2harvest.org/find-food/summer-meals-kids, https://www.2harvest.org/find-food/hunger-anyone, https://www.2harvest.org/about-us and https://www.2harvest.org/about-us/our-impact and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://www.2harvest.org/ways-to-give took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
6 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.
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://bat.bing.com/action/0?ti=5306756&tm=gtm002&Ver=2&mid=ac0be0c2-391a-439d-b876-57c9b3edcb8e&bo=1&sid=73af1ee0d70c11f182f9a3e2878792a1&vid=73af5730d70c11f1b8959dccb61d099b&vids=1&msclkid=N&pi=918.
4 small tap targets
4 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 841 words of copy
The homepage carries about 841 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
6 calls to action
The homepage has 6 calls to action, for example “LEARN MORE”, “Sign Up” and “Contact, Hours & Location”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 73 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies (measured from a US location before any click).
No consent tool detected
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.
50 other companies contacted
Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 2harvest.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on 2harvest.org, including 17 speed issues and 4 SEO issues. 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.