Website review, no card needed

adfinternational.org logo

adfinternational.org website review

Visit site (opens in a new tab)Reviewed 25 October 202619 issues · 81 checks

This review found 19 issues worth fixing on adfinternational.org, 7 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
6.6 s2.4 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20266.1 s
May 9, 20266.1 s
May 16, 20265.9 s
May 23, 20265.9 s
May 30, 20265.8 s
Jun 6, 20265.7 s
Jun 13, 20265.5 s
Jun 20, 20265.3 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20264.2 s
Jul 18, 20263.5 s
Jul 25, 20263.1 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
200 ms147 msMay 2Oct 17153 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026185 ms
May 9, 2026186 ms
May 16, 2026189 ms
May 23, 2026194 ms
May 30, 2026187 ms
Jun 6, 2026181 ms
Jun 13, 2026177 ms
Jun 20, 2026169 ms
Jun 27, 2026169 ms
Jul 4, 2026170 ms
Jul 11, 2026162 ms
Jul 18, 2026157 ms
Jul 25, 2026155 ms
Aug 1, 2026162 ms
Aug 8, 2026167 ms
Aug 15, 2026187 ms
Aug 22, 2026188 ms
Aug 29, 2026186 ms
Sep 5, 2026185 ms
Sep 12, 2026170 ms
Sep 19, 2026169 ms
Sep 26, 2026164 ms
Oct 3, 2026171 ms
Oct 10, 2026161 ms
Oct 17, 2026153 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 adfinternational.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adfinternational.org at 0.4 s0.4 s
  2. adfinternational.org at 0.8 s0.8 s
  3. adfinternational.org at 1.3 s1.3 s
  4. adfinternational.org at 1.7 s1.7 s
  5. adfinternational.org at 2.1 s2.1 s
  6. adfinternational.org at 2.5 s2.5 s
  7. adfinternational.org at 2.9 s2.9 s
  8. adfinternational.org at 3.3 s3.3 s

Speed

3 to fix60
  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused CSS

    450 ms · 82 KiB

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

  • Reduce unused JavaScript

    150 ms · 28 KiB

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

  • Improve image delivery

    169 KiB

    8 images could be 169 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 54 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).

  • 3 third-party services on the page

    3 third-party services load with your homepage (cloudflare.com, JSDelivr CDN and Cloudflare), adding 63 KiB and 34 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 97 but mobile only 60. 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.

  • Use efficient cache lifetimes

    4 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

7 to fix100
  • 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: 10.8 s

    10.8 s

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

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

  • Time to Interactive: 10.8 s

    10.8 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • 4 images without width and height

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

8 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 130 ms

    130 ms

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

  • 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 TTFB: 789 ms

    789 ms

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

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

    -50%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • 1 image in older formats

    1 image (46 KiB) is 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.

  • 4 images below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.51 g

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

2 checks passed
  • Page weight: 1.8 MB in 85 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 85 requests on a phone: other files 611 KiB (6), scripts 356 KiB (37) and images 307 KiB (16). That is a lean page.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9697
  • 18 text elements with low contrast

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 1 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 9293
  • Meta description is long (210 characters)

    Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 9 links with vague text

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

  • 104 internal links, 11 external

    The homepage links to 104 pages on adfinternational.org and 11 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Gender ideology: myth or fact?”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Alliance Defending Freedom - That all might be free”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

100
4 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://adfinternational.org/llms.txt (4 KiB, 26 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 3 pages share a title

    https://adfinternational.org/de, https://adfinternational.org/fr and https://adfinternational.org/es all use the title “Alliance Defending Freedom”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without an H1

    https://adfinternational.org/our-cases and https://adfinternational.org/resources have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

2 checks passed
  • Tap targets are thumb-sized

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

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

    The homepage carries about 829 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “DOWNLOAD FREE BROCHURE NOW”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Contact”, “Contact submenu” and “Contact Us”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • 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

  • 7 cookies set on arrival

    7

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

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 adfinternational.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 Tag Manager

Hiring

Hiring
3 open roles
Teams
ADFI (1), HR (1), International Operations (ADFI) (1)
Job board
greenhouse

Company

Headquarters
Vienna

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on adfinternational.org, including 10 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