Website review, no card needed

branchesfl.org logo

branchesfl.org website review

Visit site (opens in a new tab)Reviewed 25 October 202643 issues · 83 checks

This review found 43 issues worth fixing on branchesfl.org, 22 of them high impact, across 83 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.6 s3.5 sMay 2Sep 263.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.7 s
May 9, 20263.8 s
May 16, 20263.7 s
May 23, 20263.8 s
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20263.8 s
Jun 20, 20263.8 s
Jun 27, 20263.6 s
Jul 4, 20263.6 s
Jul 18, 20263.8 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20264.2 s
Aug 22, 20264.3 s
Aug 29, 20264.5 s
Sep 5, 20264.4 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s

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 branchesfl.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. branchesfl.org at 2.0 s2.0 s
  2. branchesfl.org at 3.9 s3.9 s
  3. branchesfl.org at 5.9 s5.9 s
  4. branchesfl.org at 7.8 s7.8 s
  5. branchesfl.org at 9.8 s9.8 s
  6. branchesfl.org at 11.8 s11.8 s
  7. branchesfl.org at 13.7 s13.7 s
  8. branchesfl.org at 15.7 s15.7 s

Speed

7 to fix35
  • Use efficient cache lifetimes

    10.6 s · 7.9 MB

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

  • Improve image delivery

    5.8 s · 5.8 MB

    20 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.

  • Reduce unused JavaScript

    2.2 s · 372 KiB

    About 372 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.5 s · 233 KiB

    About 233 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 35

    35/100

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

  • Google Tag Manager adds 442 ms

    442 ms

    Google Tag Manager costs a phone 442 ms of main-thread work and 678 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Google Fonts and Bootstrap CDN and others), adding 873 KiB and 442 ms of main-thread time.

  • Minify CSS

    150 ms · 21 KiB

    21 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Document request latency

    61 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    50 ms

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

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 76 ms

    76 ms

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

Core Web Vitals

11 to fix50
  • 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 FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 3.1 s

    3.1 s

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

  • Largest Contentful Paint: 20.3 s

    20.3 s

    Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Help Branches prepare & deliver 6,500 meals! Read more Give…”.

  • Speed Index: 18.3 s

    18.3 s

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

  • Time to Interactive: 25.5 s

    25.5 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Cumulative Layout Shift: 0.366

    0.366

    The layout shifts by 0.366 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.9 s

    3.9 s

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

  • 26 images without width and height

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

  • Total Blocking Time: 212 ms

    212 ms

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

1 checks passed
  • Real-user CLS: 0.00

    0.00

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

Images and page weight

5 to fix18
  • Page weight: 8.9 MB in 62 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 62 requests on a phone: images 7.6 MB (31), scripts 826 KiB (10) and stylesheets 259 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 4.9 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    2.6 MB

    7 images are downloaded at several times the size a phone draws them, for example annual-report-2025.png at 1,080 px wide, shown at 255 px. Resized copies would save about 2.6 MB.

  • 13 images in older formats

    13 images (6.1 MB) 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 below the first screen load straight away

    7 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.51 g

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

Accessibility

9 to fixGoogle 6883
  • 27 buttons without a name

    27 buttons have no accessible name, so screen readers announce just “button”.

  • 29 text elements with low contrast

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

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 11 links without text

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 27 automated accessibility rules passed

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

SEO

4 to fixGoogle 7771
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (19 characters)

    Your title is only 19 characters: “Homepage - Branches”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 23 links with vague text

    23 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 88 internal links, 13 external

    The homepage links to 88 pages on branchesfl.org and 13 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://branchesfl.org/.

  • Structured data in place

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

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://branchesfl.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 (1,708 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://branchesfl.org/about-us, https://branchesfl.org/leadership-team, https://branchesfl.org/our-partners, https://branchesfl.org/2gen-approach, https://branchesfl.org/careers and https://branchesfl.org/diversity-inclusion and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages slow to respond

    https://branchesfl.org/about-us, https://branchesfl.org/leadership-team, https://branchesfl.org/our-partners, https://branchesfl.org/careers, https://branchesfl.org/diversity-inclusion and https://branchesfl.org/programs and 8 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 43 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

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    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 (Not Found)”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

  • 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 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 1,667 words of copy

    The homepage carries about 1,667 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Sign Up For Our Mailing List” and “Subscribe”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 branchesfl.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

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on branchesfl.org, including 18 speed issues, 4 SEO issues and 2 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