Website review, no card needed

lafoodbank.org logo

lafoodbank.org website review

Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 90 checks

This review found 38 issues worth fixing on lafoodbank.org, 19 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.7 s2.4 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20263.0 s
Jun 20, 20263.3 s
Jun 27, 20263.8 s
Jul 4, 20264.0 s
Jul 11, 20264.2 s
Jul 18, 20264.3 s
Jul 25, 20264.3 s
Aug 1, 20264.4 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Aug 22, 20264.3 s
Aug 29, 20263.9 s
Sep 5, 20263.8 s
Sep 12, 20263.7 s
Sep 19, 20263.6 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
238 ms161 msMay 16Oct 31170 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026174 ms
May 23, 2026174 ms
May 30, 2026174 ms
Jun 6, 2026178 ms
Jun 13, 2026185 ms
Jun 20, 2026187 ms
Jun 27, 2026192 ms
Jul 4, 2026190 ms
Jul 11, 2026194 ms
Jul 18, 2026184 ms
Jul 25, 2026177 ms
Aug 1, 2026181 ms
Aug 8, 2026189 ms
Aug 15, 2026201 ms
Aug 22, 2026211 ms
Aug 29, 2026229 ms
Sep 5, 2026220 ms
Sep 12, 2026210 ms
Sep 19, 2026197 ms
Sep 26, 2026181 ms
Oct 3, 2026179 ms
Oct 10, 2026179 ms
Oct 17, 2026175 ms
Oct 24, 2026170 ms
Oct 31, 2026170 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

Full-page screenshot of lafoodbank.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lafoodbank.org at 0.4 s0.4 s
  2. lafoodbank.org at 0.8 s0.8 s
  3. lafoodbank.org at 1.2 s1.2 s
  4. lafoodbank.org at 1.5 s1.5 s
  5. lafoodbank.org at 1.9 s1.9 s
  6. lafoodbank.org at 2.3 s2.3 s
  7. lafoodbank.org at 2.7 s2.7 s
  8. lafoodbank.org at 3.1 s3.1 s

Speed

6 to fix63
  • Use efficient cache lifetimes

    2.3 s · 1.4 MB

    22 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Render-blocking requests

    2.9 s

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

  • Improve image delivery

    450 ms · 938 KiB

    9 images could be 938 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.

  • Reduce unused JavaScript

    900 ms · 227 KiB

    About 227 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 63

    63/100

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

  • Reduce unused CSS

    750 ms · 132 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Crazy Egg, userway.org and Google Optimize and others), adding 471 KiB and 257 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 long tasks on the main thread

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 481 ms of it running JavaScript. That is comfortably low.

  • Server response: 25 ms

    25 ms

    Your server sent the HTML in 25 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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.

  • Real-user LCP: 4.5 s

    4.5 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Largest Contentful Paint: 10.5 s

    10.5 s

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

  • Time to Interactive: 10.5 s

    10.5 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Largest content (LCP) got 40% slower for real visitors

    +40%

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

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 174 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user INP: 118 ms

    118 ms

    Real visitors wait 118 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.03

    0.03

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

  • Cumulative Layout Shift: 0.033

    0.033

    The layout barely moves while loading (CLS 0.033, good is under 0.1).

  • Total Blocking Time: 9 ms

    9 ms

    Scripts block the page for only 9 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix33
  • 1 image over 500 KB

    191204-Season-For-Sharing-322.jpg weighs 800 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    662 KiB

    2 images are downloaded at several times the size a phone draws them, for example 191204-Season-For-Sharing-322.jpg at 2,200 px wide, shown at 320 px. Resized copies would save about 662 KiB.

  • Page weight: 2.8 MB in 99 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 99 requests on a phone: images 1.7 MB (26), scripts 624 KiB (30) and stylesheets 188 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (938 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.

  • 5 images below the first screen load straight away

    5 images further down the page (940 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.79 g

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

Accessibility

8 to fixGoogle 8489
  • 7 text elements with low contrast

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

  • Links look like plain text

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 elements on the page fail 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.

  • Page should contain a level-one heading (1 element)

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

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9288
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 15 links with vague text

    15 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 set, so this is minor.

  • 106 internal links, 41 external

    The homepage links to 106 pages on lafoodbank.org and 41 external pages.

7 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “The Los Angeles Regional Food Bank has provided more than one billion meals since 1973. Help us reach the next billion!”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Los Angeles Regional Food Bank”.

  • Canonical URL set

    The canonical URL is https://www.lafoodbank.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://www.lafoodbank.org/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (651 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 1 page without a meta description

    https://www.lafoodbank.org/events has 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://www.lafoodbank.org/wefeedla, whose canonical is https://www.lafoodbank.org/donate/food/wefeedla. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.lafoodbank.org/about and https://www.lafoodbank.org/about/team have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.lafoodbank.org/wefeedla, https://www.lafoodbank.org/donate/food, https://www.lafoodbank.org/donate-page/other-ways-to-give, https://www.lafoodbank.org/volunteer, https://www.lafoodbank.org/about and https://www.lafoodbank.org/about/who-we-help and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 36 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    30 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • No social proof

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

  • 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 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 471 words of copy

    The homepage carries about 471 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Learn More”, “Subscribe” and “Sign Up”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 lafoodbank.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Pantheon

Company

Employees
254
Headquarters
Los Angeles

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 lafoodbank.org, including 16 speed issues, 2 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25