unidef.org website review

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

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

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

Your mobile performance score is 35 (desktop: 85). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

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

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

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

The page has 1,753 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 352 ms of main-thread time.

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

About 26 KiB of CSS is downloaded but never applied on this page.

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

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.

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

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

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

Your largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HomeBg”. Most of its time is resource load delay (6.2 s).

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

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

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

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.

6 images (497 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.

1 image further down the page (165 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

24 buttons have no accessible name, so screen readers announce just “button”.

8 elements hidden from screen readers can still receive keyboard focus.

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

4 links inside paragraphs rely on colour alone to stand out.

1 tap target is too small or too close together to hit reliably with a finger.

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

Heading levels should only increase by one: 4 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://unidef.org/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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

A phone browser shows 1,123 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://unidef.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.

Large scripts ship without source maps.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,123 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 2 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.