Website review, no card needed

actionforhappiness.org logo

actionforhappiness.org website review

Visit site (opens in a new tab)Reviewed 20 October 202642 issues · 85 checks

This review found 42 issues worth fixing on actionforhappiness.org, 12 of them high impact, across 85 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
2.3 s1.9 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
124 ms97 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026111 ms
May 16, 2026110 ms
May 23, 2026108 ms
May 30, 2026103 ms
Jun 6, 2026101 ms
Jun 13, 2026100 ms
Jun 20, 2026102 ms
Jun 27, 2026104 ms
Jul 4, 2026110 ms
Jul 11, 2026111 ms
Jul 18, 2026109 ms
Jul 25, 2026106 ms
Aug 1, 2026106 ms
Aug 8, 2026109 ms
Aug 15, 2026109 ms
Aug 22, 2026109 ms
Aug 29, 2026106 ms
Sep 5, 2026108 ms
Sep 12, 2026112 ms
Sep 19, 2026113 ms
Sep 26, 2026114 ms
Oct 3, 2026121 ms
Oct 10, 2026121 ms
Oct 17, 2026120 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 actionforhappiness.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. actionforhappiness.org at 0.4 s0.4 s
  2. actionforhappiness.org at 0.8 s0.8 s
  3. actionforhappiness.org at 1.1 s1.1 s
  4. actionforhappiness.org at 1.5 s1.5 s
  5. actionforhappiness.org at 1.9 s1.9 s
  6. actionforhappiness.org at 2.3 s2.3 s
  7. actionforhappiness.org at 2.6 s2.6 s
  8. actionforhappiness.org at 3.0 s3.0 s

Speed

8 to fix54
  • Use efficient cache lifetimes

    8.0 s · 1.5 MB

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

  • Improve image delivery

    3.4 s · 701 KiB

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

  • Render-blocking requests

    3.9 s

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

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

  • Font display

    400 ms

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

  • Minify JavaScript

    300 ms · 55 KiB

    55 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    300 ms · 24 KiB

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

  • FontAwesome CDN adds 164 ms

    164 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (FontAwesome CDN, blackfire.io and Mixpanel and others), adding 801 KiB and 272 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 27 KiB

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

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • 5 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 185 ms

    185 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 17.4 s

    17.4 s

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

  • Time to Interactive: 17.4 s

    17.4 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Total Blocking Time: 223 ms

    223 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

8 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.0 s

    2.0 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 795 ms

    795 ms

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

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

    -12%

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

6 to fix43
  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 2.9 MB in 70 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 70 requests on a phone: images 1.5 MB (16), scripts 989 KiB (41) and fonts 404 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (1.3 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.

  • An image on the first screen is lazy-loaded

    AFH_ACTION_2026_10_OCT_20.png 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).

  • 1 image below the first screen load straight away

    1 image further down the page (631 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    252 KiB

    1 image is downloaded at several times the size a phone draws it, for example popup-part-3.png at 1,393 px wide, shown at 360 px. Resized copies would save about 252 KiB.

  • About 0.8 g of CO₂ per visit

    0.83 g

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

Accessibility

6 to fixGoogle 8590
  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • 10 text elements with low contrast

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

  • 8 images without alt text

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

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

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

  • 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
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 8586
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Let's take action to be Happier and Kinder,Togeth…” and “Join us”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 39 internal links, 12 external

    The homepage links to 39 pages on actionforhappiness.org and 12 external pages.

5 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Action for Happiness is a charity that promotes a happier and more caring society. We promote how to be happy, kindness…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Happier Kinder Together | Action for Happiness”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://actionforhappiness.org/sitemap.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://actionforhappiness.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,143 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://actionforhappiness.org/about and https://actionforhappiness.org/about-us all use the title “About Us | Action for Happiness”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://actionforhappiness.org/course, https://actionforhappiness.org/our-impact, https://actionforhappiness.org/resources, https://actionforhappiness.org/podcasts and https://actionforhappiness.org/children-young-people have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://actionforhappiness.org/about and https://actionforhappiness.org/about-us use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://actionforhappiness.org/about, whose canonical is https://actionforhappiness.org/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

  • 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 to fixGoogle 9693
  • 3 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • 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.

  • Thin social proof

    Social proof on the homepage: 22 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • A 20-field form

    Your longest form asks for 20 fields (8 required). Every extra field lowers completion.

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

  • About 654 words of copy

    The homepage carries about 654 words of visible text.

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Coaching Try our free online coaching”, “Talks Join our inspiring speakers” and “Join our movement”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Mixpanel (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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 actionforhappiness.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

Company

Employees
2

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on actionforhappiness.org, including 14 speed issues, 4 SEO issues and 5 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