Website review, no card needed

pourinternational.org logo

pourinternational.org website review

Visit site (opens in a new tab)Reviewed 20 November 202627 issues · 74 checks

This review found 27 issues worth fixing on pourinternational.org, 12 of them high impact, across 74 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

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

How it loaded on a phone

  1. pourinternational.org at 0.4 s0.4 s
  2. pourinternational.org at 0.8 s0.8 s
  3. pourinternational.org at 1.2 s1.2 s
  4. pourinternational.org at 1.6 s1.6 s
  5. pourinternational.org at 2.1 s2.1 s
  6. pourinternational.org at 2.5 s2.5 s
  7. pourinternational.org at 2.9 s2.9 s
  8. pourinternational.org at 3.3 s3.3 s

Speed

8 to fix35
  • Use efficient cache lifetimes

    5.6 s · 6.3 MB

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

  • Render-blocking requests

    5.3 s

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

  • Reduce unused JavaScript

    1.4 s · 2.4 MB

    About 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Stripe, Facebook and plaid.com and others), adding 1.3 MB and 648 ms of main-thread time.

  • Stripe adds 594 ms

    594 ms

    Stripe costs a phone 594 ms of main-thread work and 1.1 MB 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.

  • Reduce unused CSS

    450 ms · 102 KiB

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

  • Main-thread work: 3.8 s

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

  • Font display

    250 ms

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

  • 18 long tasks on the main thread

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

  • Improve image delivery

    200 ms · 37 KiB

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

  • Legacy JavaScript

    150 ms · 18 KiB

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

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 31 ms

    31 ms

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

Core Web Vitals

5 to fix44
  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Together, We Can Brighten Tomorrow We provide safe places w…”.

  • Time to Interactive: 47.7 s

    47.7 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Total Blocking Time: 910 ms

    910 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 8.3 MB in 313 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 313 requests on a phone: scripts 6.8 MB (216), images 675 KiB (8) and fonts 473 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (174 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.

  • About 2.4 g of CO₂ per visit

    2.36 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9895
  • All page content should be contained by landmarks (28 elements)

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

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 39 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: 39 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • Title is short (25 characters)

    Your title is only 25 characters: “Home - Pour International”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 31 internal links, 1 external

    The homepage links to 31 pages on pourinternational.org and 1 external page.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Pour International plays a vital role in bringing hope and life to kids and families who are hurting in Eswatini, Afric…”.

  • One H1 headline

    Your main headline reads: “Pour International”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.pourinternational.org/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 1 AI answer engine crawler

    1 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, ClaudeBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.pourinternational.org/donate-now and https://www.pourinternational.org/blog have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.pourinternational.org/donate-now has 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.

  • 1 page slow to respond

    https://www.pourinternational.org/programs took over 3 s to send its HTML from our server.

  • 5 internal pages checked

    We fetched 5 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 5 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 5 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

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

  • No analytics detected

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

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

    The homepage carries about 435 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

  • 1 short form

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 9 cookies set on arrival

    9

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 pourinternational.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
E-commerce
WooCommerce
Hosting
LightEdge Solutions

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on pourinternational.org, including 13 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