ungeneva.org website review

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

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

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

3 third-party services load with your homepage (Google Tag Manager, unog.ch and Google Analytics), adding 1.3 MB and 960 ms of main-thread time.

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

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

About 600 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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.

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

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

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

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

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

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

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

The layout shifts by 0.143 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Play video for %AutoEntityLabel: 8ecc8122-9c4d-4d69-9509-63…”.

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

Your homepage downloads 3.1 MB in 62 requests on a phone: scripts 1.4 MB (14), images 1.2 MB (30) and fonts 444 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

2026 Annual Report hero banner_0.jpg 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).

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

1 image is downloaded at several times the size a phone draws it, for example 2026 Annual Report hero banner_0.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 174 KiB.

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

Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

1 dropdown has no label.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

The robots meta tag says “noindex, nofollow, noarchive, nosnippet, noimageindex, notr…”: Google is told not to list this page at all.

No meta description, so Google writes its own snippet from whatever text it finds.

Google's crawler is blocked from indexing this page.

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

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 80 pages on ungeneva.org and 16 external pages.

The robots meta tag says “noindex, nofollow, noarchive, nosnippet, noimageindex, notr…”, which tells Google, Bing and the AI answers built on them not to quote this page.

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.

There is no https://www.ungeneva.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.

https://www.ungeneva.org/ar, https://www.ungeneva.org/zh, https://www.ungeneva.org/fr, https://www.ungeneva.org/ru, https://www.ungeneva.org/es and https://www.ungeneva.org/en/about and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ungeneva.org/ar, https://www.ungeneva.org/zh, https://www.ungeneva.org/ru and https://www.ungeneva.org/es have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ungeneva.org/ar, https://www.ungeneva.org/zh and https://www.ungeneva.org/ru have 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.

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

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

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

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

The homepage carries about 629 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and 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 9 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.