Website review, no card needed

wearelee.org logo

wearelee.org website review

Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 92 checks

This review found 40 issues worth fixing on wearelee.org, 15 of them high impact, across 92 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
3.0 s1.8 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.4 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.5 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
141 ms72 msMay 9Oct 24117 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202693 ms
May 16, 202695 ms
May 23, 202695 ms
May 30, 202687 ms
Jun 6, 202686 ms
Jun 13, 202693 ms
Jun 20, 202687 ms
Jun 27, 202694 ms
Jul 4, 202683 ms
Jul 11, 202683 ms
Jul 18, 202680 ms
Jul 25, 202686 ms
Aug 1, 202689 ms
Aug 8, 202686 ms
Aug 15, 202689 ms
Aug 22, 202680 ms
Aug 29, 202684 ms
Sep 5, 202685 ms
Sep 12, 202687 ms
Sep 19, 2026103 ms
Sep 26, 2026104 ms
Oct 3, 2026107 ms
Oct 10, 2026130 ms
Oct 17, 2026133 ms
Oct 24, 2026117 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 wearelee.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wearelee.org at 0.7 s0.7 s
  2. wearelee.org at 1.4 s1.4 s
  3. wearelee.org at 2.1 s2.1 s
  4. wearelee.org at 2.8 s2.8 s
  5. wearelee.org at 3.5 s3.5 s
  6. wearelee.org at 4.2 s4.2 s
  7. wearelee.org at 4.9 s4.9 s
  8. wearelee.org at 5.6 s5.6 s

Speed

11 to fix55
  • Use efficient cache lifetimes

    33.7 s · 8.6 MB

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

  • Reduce unused JavaScript

    6.4 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

  • Render-blocking requests

    2.8 s

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

  • Improve image delivery

    500 ms · 1,012 KiB

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

  • Mobile performance score: 55

    55/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.3 MB and 688 ms of main-thread time.

  • Reduce unused CSS

    590 ms · 97 KiB

    About 97 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.

  • Google Tag Manager adds 207 ms

    207 ms

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

  • Google CDN adds 159 ms

    159 ms

    Google CDN costs a phone 159 ms of main-thread work and 382 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.

  • Cloudflare CDN adds 86 ms

    86 ms

    Cloudflare CDN costs a phone 86 ms of main-thread work and 738 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.

  • FontAwesome CDN adds 33 ms

    33 ms

    FontAwesome CDN costs a phone 33 ms of main-thread work and 335 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.

  • Legacy JavaScript

    250 ms · 63 KiB

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

  • 6 long tasks on the main thread

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 56.5 s

    56.5 s

    Your largest element takes 56.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “As a leadership development organization, LEE supports lead…”.

  • Speed Index: 17.0 s

    17.0 s

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

  • Time to Interactive: 57.1 s

    57.1 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Tap response (INP) got 33% slower for real visitors

    +33%

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

  • 73 images without width and height

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

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

    +12%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 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: 2.4 s

    2.4 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 644 ms

    644 ms

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

  • Total Blocking Time: 117 ms

    117 ms

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

  • Cumulative Layout Shift: 0.023

    0.023

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

Images and page weight

4 to fix33
  • Page weight: 10.8 MB in 139 requests

    10.8 MB

    Your homepage downloads 10.8 MB in 139 requests on a phone: images 6.4 MB (48), scripts 2.2 MB (44) and fonts 2.0 MB (6). Under 2 MB keeps phones on slow connections fast.

  • 12 images far larger than shown

    890 KiB

    12 images are downloaded at several times the size a phone draws them, for example BTClogo-scaled.png at 2,560 px wide, shown at 308 px. Resized copies would save about 890 KiB.

  • 23 images in older formats

    23 images (1.7 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.

  • 27 images below the first screen load straight away

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

  • About 3.0 g of CO₂ per visit

    3.05 g

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

Accessibility

10 to fixGoogle 7483
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 11 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 38 images without alt text

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

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

    All page content should be contained by landmarks: 14 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 4 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 8581
  • No H1 headline

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

  • Title is short (15 characters)

    Your title is only 15 characters: “LEE | Home Page”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 links with vague text

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

  • 41 internal links, 5 external

    The homepage links to 41 pages on wearelee.org and 5 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “LEE is a nonpartisan network offering coaching, connections, and training to help members expand opportunity in their c…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, ProfessionalService 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://wearelee.org/sitemaps.xml.

AI search readiness

100
  • No llms.txt

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

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: 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 (339 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://wearelee.org/category/value-proposition is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://wearelee.org/category/value-proposition has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages with very little text

    https://wearelee.org/members/grow-your-career, https://wearelee.org/members/expand-your-network, https://wearelee.org/members/take-action, https://wearelee.org/members/run-for-office and https://wearelee.org/leegal-community-toolkit have 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.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9679
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 3 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 326 words of visible text.

6 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “Join LEE” and “Learn more”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 2 trust badges and “80K+ members”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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

  • 5 trackers load before any consent

    5

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

  • 4 cookies set on arrival

    4

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 wearelee.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
React
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on wearelee.org, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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