wto.org website review

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

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

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

About 258 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

172 KiB could be saved by minifying JavaScript.

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

5 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Cloudflare and others), adding 263 KiB and 198 ms of main-thread time.

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

Polyfills for old browsers add 10 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.

3 KiB could be saved by minifying CSS.

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 10.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.

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

8 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-31, real Chrome visitors' tap response (inp) went from 175 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.1 MB in 94 requests on a phone: images 2.3 MB (14), scripts 1.2 MB (52) and other files 397 KiB (10). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

5 images (2.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.

1 image is downloaded at several times the size a phone draws it, for example A4T_Website_banners_1200x675_E_20260622092122_lg.png at 1,200 px wide, shown at 360 px. Resized copies would save about 116 KiB.

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

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

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

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

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

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

4 tap targets are too small or too close together to hit reliably with a finger.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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.

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

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

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

The homepage links to 28 pages on wto.org and 4 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.

https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_programme_e.htm and https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_session_fullpage_e.htm all use the title “WTO | Programme - Global Review of Aid for Trade 2026”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/global_review26_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_programme_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_session_fullpage_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/photos_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/cssta4t_e.htm and https://www.wto.org/english/tratop_e/devel_e/a4t_e/aid4trade_e.htm and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wto.org/english/res_e/publications_e/anrep-iframe_e.htm has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_programme_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_session_fullpage_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/photos_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/cssta4t_e.htm, https://www.wto.org/english/news_e/spno_e/spno_e.htm and https://www.wto.org/english/res_e/photo_gallery_e/photo_gallery_e.htm 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.

https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_programme_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/gr26_session_fullpage_e.htm, https://www.wto.org/english/tratop_e/devel_e/a4t_e/global_review26_e/photos_e.htm, https://www.wto.org/english/res_e/publications_e/world-trade-report-2026_e.htm, https://www.wto.org/english/thewto_e/dg_e/dg_e.htm and https://www.wto.org/english/news_e/spno_e/spno_e.htm and 2 others took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Large scripts ship without source maps.

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 has only about 159 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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