benoy.com website review

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

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

Google Tag Manager costs a phone 324 ms of main-thread work and 302 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.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

3 third-party services load with your homepage (Google Tag Manager, Civic and Google Analytics), adding 429 KiB and 468 ms of main-thread time.

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (13 KiB).

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.

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

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

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is element render delay (2.2 s).

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

1 image further down the page (23 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.45 g of CO₂e: 54.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

There are 3 <h1> headlines (“18 Cross, Singapore”, “Wuxi MixC West completes on the shore of Lihu Lake” and “Benoy puts a stage on Dubai’s Crystal Lagoon at A…”). One clear main headline is easier for people and search engines.

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

The homepage links to 19 pages on benoy.com and 5 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/news/wuxi-mixc-west-completes-on-the-shore-of-lihu-lake and /news/benoy-puts-a-stage-on-dubais-crystal-lagoon-at-azizi-venice-boulevard all use the title “The hotel is no longer the destination. It’s the connector. | Design …”. Search engines can't tell which page to show for a search, so each competes with the others.

/news, /careers, /projects/18-cross, /services/commercial-consultancy, /services/masterplanning-strategy and /services/architecture and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/news/wuxi-mixc-west-completes-on-the-shore-of-lihu-lake and /news/benoy-puts-a-stage-on-dubais-crystal-lagoon-at-azizi-venice-boulevard use the same meta description. A description written for each page earns more clicks.

/projects/18-cross has no <h1> headline, so visitors and search engines get no clear main topic.

/projects and /contact 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.

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

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.

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 184 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.

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