ciff.org website review

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

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Matomo and others), adding 340 KiB and 459 ms of main-thread time.

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

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

8 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “As an independent global philanthropy, we work with partner…”.

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

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

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

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

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

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

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

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

Your homepage downloads 5.6 MB in 55 requests on a phone: media 2.4 MB (1), images 2.3 MB (23) and fonts 449 KiB (9). Under 2 MB keeps phones on slow connections fast.

11 images (496 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.

2 images are downloaded at several times the size a phone draws them, for example India-502x502.jpg at 390 px wide, shown at 54 px. Resized copies would save about 94 KiB.

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

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

All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.

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

There are 4 <h1> headlines (“Together, we can create a world where all childre…”, “Strengthening health and nutrition” and “Supporting opportunity and choice for women and g…”). One clear main headline is easier for people and search engines.

The homepage links to 70 pages on ciff.org and 7 external pages.

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.

/careers has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 915 words of visible text.

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

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

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.

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