wood.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

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

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

8 third-party services load with your homepage (Google Tag Manager, apploud.cz and Clarity and others), adding 868 KiB and 586 ms of main-thread time.

259 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

1 image could be 68 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 24.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to make your browsing experience more enjoya…”.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 204 ms to 229 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 3.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 21.1 MB in 190 requests on a phone: other files 9.3 MB (35), media 8.4 MB (1) and scripts 2.5 MB (112). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 50 pages on wood.com and 22 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.

Your homepage links to https://wood.com/services, which answers with an error. Visitors hit a dead end and search engines drop it.

https://wood.com/products/funds/wood-company-residential-sub-fund and https://wood.com/products/funds/wood-company-residential-sub-fund-eur-class all use the title “WOOD & Co. Residential Subfund | Residential RE Investments | WOOD & …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://wood.com/products/funds/wood-company-residential-sub-fund and https://wood.com/products/funds/wood-company-residential-sub-fund-eur-class use the same meta description. A description written for each page earns more clicks.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

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