wwf.sg website review

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

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

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

Reduce initial server response time. Google estimates savings of 2.6 s on a phone.

5 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.4 s).

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

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

Your server takes 2.7 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Stripe and others), adding 1.6 MB and 1.6 s of main-thread time.

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

Polyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

Facebook costs a phone 341 ms of main-thread work and 267 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.

Stripe costs a phone 274 ms of main-thread work and 271 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 2,917 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

26 KiB could be saved by minifying JavaScript.

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

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

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

Desktop scores 63 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.

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 36.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 18.8 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

Your homepage downloads 6.4 MB in 158 requests on a phone: images 3.7 MB (27), scripts 2.2 MB (82) and fonts 320 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

Homepage-Banner-MYAFY26-Mobile.png 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).

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

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

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

All page content should be contained by landmarks: 13 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.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

The homepage links to 195 pages on wwf.sg and 21 external pages.

There is no https://www.wwf.sg/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.wwf.sg/climate/net-zero-carbon-stage is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.wwf.sg/our-work, https://www.wwf.sg/climate, https://www.wwf.sg/climate/net-zero-carbon-stage, https://www.wwf.sg/climate/sustainable-finance, https://www.wwf.sg/sustainability-circular-economy and https://www.wwf.sg/sustainability-circular-economy/sustainable-palm-oil and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wwf.sg/our-work, https://www.wwf.sg/climate, https://www.wwf.sg/climate/net-zero-carbon-stage, https://www.wwf.sg/climate/sustainable-finance, https://www.wwf.sg/sustainability-circular-economy and https://www.wwf.sg/sustainability-circular-economy/sustainable-palm-oil and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.wwf.sg/nature-biodiversity/illegal-wildlife-trade took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Error in function handleUserSession: TypeError: Cannot read properties of undefined (reading 'addEventListener')”.

1 image is served at too low a resolution for sharp phone screens.

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

Your longest form asks for 27 fields (26 required). Every extra field lowers completion.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 496 words of visible text.

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