upu.int website review

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

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

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

12 images could be 6.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Clarity and others), adding 1.4 MB and 818 ms of main-thread time.

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

YouTube costs a phone 445 ms of main-thread work and 980 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 Tag Manager costs a phone 305 ms of main-thread work and 318 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.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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.

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

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

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

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Universal Postal Union is a United Nations specialized …”. Most of its time is element render delay (4.3 s).

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

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

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

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

Your homepage downloads 9.1 MB in 66 requests on a phone: images 7.3 MB (17), scripts 1.3 MB (19) and fonts 177 KiB (3). Under 2 MB keeps phones on slow connections fast.

7 images weigh 5.8 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example 202610uPUDevelopmentForumHomepage4x3_EN.jpg at 1,153 px wide, shown at 358 px. Resized copies would save about 2.2 MB.

9 images (6.5 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.

4 images further down the page (2.6 MB) 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 2.57 g of CO₂e: 308.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

1 frame has no title, so screen-reader users cannot tell what it contains.

4 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

17 visible links have no text or label, so screen readers cannot say where they go.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

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

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

31 links have no real href, so search engines can't follow them.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 280 pages on upu.int and 24 external pages.

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.upu.int/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.upu.int/en/home and https://www.upu.int/en-us all use the title “Home”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.upu.int/en-us, https://www.upu.int/en/upcoming-events, https://www.upu.int/fr/accueil, https://www.upu.int/en/Universal-Postal-Union/Careers, https://www.upu.int/en/Newsletter and https://www.upu.int/en/Feedback and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.upu.int/en-us, whose canonical is https://www.upu.int/en/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.upu.int/en/news-media/blog, https://www.upu.int/en/news-media/podcast and https://www.upu.int/en/news-media/newsletter have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.upu.int/en/news-media/magazine, https://www.upu.int/en/news-media/podcast and https://www.upu.int/en/news-media/newsletter took over 3 s to send their HTML from our server.

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

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

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

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

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: 1 customer or partner logo. 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 323 words of visible text.

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