keppel.com website review

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

10 images could be 5.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

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

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

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

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

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

Your homepage downloads 24.1 MB in 56 requests on a phone: images 23.6 MB (27), scripts 462 KiB (13) and fonts 56 KiB (2). Under 2 MB keeps phones on slow connections fast.

8 images weigh 22.4 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example vvs-keppel-sakracogen-walking-252-12mar-hi-.jpg at 5,823 px wide, shown at 390 px. Resized copies would save about 13.8 MB.

10 images (23.0 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.

6 images further down the page (18.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 86 characters, so Google will cut it off around 60: “Keppel - Global asset manager and operator creating solutions for a sustainable future”.

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

There are 5 <h1> headlines (“$106bn”, “$28.2bn” and “$47.3bn”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.keppel.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at keppel.com/robots.txt, the first file search crawlers ask for.

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

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

The homepage links to 12 pages on keppel.com 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.

The HTML your server sends has 261 of the 627 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.keppel.com/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.keppel.com/about-us/the-keppel-difference, https://www.keppel.com/fund-management-and-investment/infrastructure, https://www.keppel.com/fund-management-and-investment/real-estate, https://www.keppel.com/fund-management-and-investment/connectivity, https://www.keppel.com/fund-management-and-investment and https://www.keppel.com/operating-expertise and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.keppel.com/fund-management-and-investment/infrastructure, https://www.keppel.com/fund-management-and-investment/real-estate, https://www.keppel.com/fund-management-and-investment/connectivity, https://www.keppel.com/fund-management-and-investment, https://www.keppel.com/operating-expertise and https://www.keppel.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.keppel.com/media has 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 8 pages linked from your homepage and read each the way a search engine does.

5 of 16 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…”).

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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.

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