Website review, no card needed

humanappeal.org.uk logo

humanappeal.org.uk website review

Visit site (opens in a new tab)Reviewed 26 October 202647 issues · 101 checks

This review found 47 issues worth fixing on humanappeal.org.uk, 18 of them high impact, across 101 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.3 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.6 s
May 23, 20262.8 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
233 ms170 msMay 9Oct 24177 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026195 ms
May 16, 2026181 ms
May 23, 2026194 ms
May 30, 2026187 ms
Jun 6, 2026188 ms
Jun 13, 2026193 ms
Jun 20, 2026185 ms
Jun 27, 2026210 ms
Jul 4, 2026216 ms
Jul 11, 2026219 ms
Jul 18, 2026221 ms
Jul 25, 2026224 ms
Aug 1, 2026220 ms
Aug 8, 2026223 ms
Aug 15, 2026226 ms
Aug 22, 2026226 ms
Aug 29, 2026221 ms
Sep 5, 2026212 ms
Sep 12, 2026203 ms
Sep 19, 2026195 ms
Sep 26, 2026195 ms
Oct 3, 2026195 ms
Oct 10, 2026194 ms
Oct 17, 2026188 ms
Oct 24, 2026177 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 humanappeal.org.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. humanappeal.org.uk at 0.7 s0.7 s
  2. humanappeal.org.uk at 1.5 s1.5 s
  3. humanappeal.org.uk at 2.2 s2.2 s
  4. humanappeal.org.uk at 3.0 s3.0 s
  5. humanappeal.org.uk at 3.7 s3.7 s
  6. humanappeal.org.uk at 4.4 s4.4 s
  7. humanappeal.org.uk at 5.2 s5.2 s
  8. humanappeal.org.uk at 5.9 s5.9 s

Speed

12 to fix46
  • Use efficient cache lifetimes

    4.5 s · 1.3 MB

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

  • Improve image delivery

    2.3 s · 935 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 5.8 s

    A phone's processor spends 5.8 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    600 ms · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, reddit and Google CDN and others), adding 2.1 MB and 1.5 s of main-thread time.

  • Reduce unused CSS

    750 ms · 298 KiB

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

  • YouTube adds 405 ms

    405 ms

    YouTube costs a phone 405 ms of main-thread work and 979 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.

  • reddit adds 383 ms

    383 ms

    reddit costs a phone 383 ms of main-thread work and 26 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 286 ms

    286 ms

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

  • 2,764 HTML elements

    The page has 2,764 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 19 long tasks on the main thread

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

  • Legacy JavaScript

    51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need.

  • Font display

    50 ms

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

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • 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: 9 ms

    9 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gaza Appeal: 100% of Your Donation Reaches Families in Need”.

  • Time to Interactive: 37.2 s

    37.2 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • Total Blocking Time: 678 ms

    678 ms

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

  • Real-user INP: 206 ms

    206 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 31 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 590 ms

    590 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix35
  • Page weight: 8.2 MB in 193 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 193 requests on a phone: scripts 3.3 MB (63), images 2.8 MB (46) and other files 1.3 MB (61). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    bitmap.png weighs 560 KiB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (1.0 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.

  • 1 image far larger than shown

    92 KiB

    1 image is downloaded at several times the size a phone draws it, for example investors-in-people-silver.png at 1,200 px wide, shown at 183 px. Resized copies would save about 92 KiB.

  • 3 images below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.32 g

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

Accessibility

11 to fixGoogle 8287
  • Unlabelled dropdowns

    5 dropdowns have no label.

  • 9 text elements with low contrast

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

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

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

  • 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 (66 elements)

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

  • 31 form fields without a label

    31 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 7 links with vague text

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

  • 151 internal links, 25 external

    The homepage links to 151 pages on humanappeal.org.uk and 25 external pages.

8 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Human Appeal is a non-profit with Islamic values. Donate now to help us combat poverty, social injustice and natural di…”.

  • One H1 headline

    Your main headline reads: “Home”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Human Appeal UK | Faith-Based Charity with Islamic Values”.

  • Canonical URL set

    The canonical URL is https://humanappeal.org.uk/.

  • Structured data in place

    Structured data found: WebPage.

  • 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://humanappeal.org.uk/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://humanappeal.org.uk/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 (3,089 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

6 to fixGoogle 5068
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97175627&tm=gtm002&Ver=2&mid=cd47ffac-bd9c-4874-898d-b5c4069b1989&bo=2&sid=b05c2ec0d15f11f18651a34f04573858&vid=b05c4ab0d15f11f1ad110d0bf32a4ca8&vids=1&msclkid=N&pi=91.

  • 24 small tap targets

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

  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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 analytics detected

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

  • A 25-field form

    Your longest form asks for 25 fields (0 required). Every extra field lowers completion.

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

  • About 1,751 words of copy

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

  • Urgency cues

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Join our family”, “Contact us” and “Register an account”.

  • Social proof on the page

    Social proof on the homepage: 29 testimonial or review blocks and 1 customer or partner logo.

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Hotjar, Klaviyo and Meta Pixel and 5 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.

  • 39 cookies set on arrival

    39

    Opening the homepage sets 39 cookies, 1 of them by other companies (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.

  • 47 other companies contacted

    Loading the homepage contacts 47 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 humanappeal.org.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Cloudflare

Company

Employees
771
Founded
1991
Headquarters
Manchester

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on humanappeal.org.uk, including 20 speed issues, 1 SEO issue 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