Website review, no card needed

genting.com logo

genting.com website review

Visit site (opens in a new tab)Reviewed 19 November 202650 issues · 92 checks

This review found 50 issues worth fixing on genting.com, 20 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.2 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.2 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.1 s
Sep 12, 20263.0 s
Sep 19, 20262.8 s
Sep 26, 20262.9 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Oct 31, 20263.0 s
Nov 7, 20262.8 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
131 ms99 msMay 30Nov 14127 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026109 ms
Jun 6, 2026111 ms
Jun 13, 2026110 ms
Jun 20, 2026108 ms
Jun 27, 2026109 ms
Jul 4, 2026108 ms
Jul 11, 2026103 ms
Jul 18, 2026104 ms
Jul 25, 2026105 ms
Aug 1, 2026107 ms
Aug 8, 2026115 ms
Aug 15, 2026121 ms
Aug 22, 2026120 ms
Aug 29, 2026119 ms
Sep 5, 2026113 ms
Sep 12, 2026120 ms
Sep 19, 2026120 ms
Sep 26, 2026120 ms
Oct 3, 2026122 ms
Oct 10, 2026118 ms
Oct 17, 2026113 ms
Oct 24, 2026115 ms
Oct 31, 2026116 ms
Nov 7, 2026122 ms
Nov 14, 2026127 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of genting.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. genting.com at 1.5 s1.5 s
  2. genting.com at 3.0 s3.0 s
  3. genting.com at 4.6 s4.6 s
  4. genting.com at 6.1 s6.1 s
  5. genting.com at 7.6 s7.6 s
  6. genting.com at 9.1 s9.1 s
  7. genting.com at 10.7 s10.7 s
  8. genting.com at 12.2 s12.2 s

Speed

10 to fix56
  • Use efficient cache lifetimes

    23.4 s · 11.3 MB

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

  • Reduce unused JavaScript

    6.2 s · 1.2 MB

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

  • Render-blocking requests

    3.1 s

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

  • Font display

    3.0 s

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

  • Improve image delivery

    1.4 s · 326 KiB

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

  • Reduce unused CSS

    1.2 s · 251 KiB

    About 251 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • Document request latency

    550 ms · 68 KiB

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

  • Reduce initial server response time

    535 ms

    Reduce initial server response time. Google estimates savings of 535 ms on a phone.

  • Server response: 635 ms

    635 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Brightcove, Google Tag Manager and Cloudflare CDN and others), adding 759 KiB and 424 ms of main-thread time.

  • Minify CSS

    190 ms · 56 KiB

    56 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    13 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 538 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 39.5 s

    39.5 s

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

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 40.2 s

    40.2 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 3 images without width and height

    3 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

5 checks passed
  • Real-user INP: 127 ms

    127 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Total Blocking Time: 109 ms

    109 ms

    Scripts block the page for only 109 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 11.8 MB in 104 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 104 requests on a phone: images 8.1 MB (38), scripts 2.0 MB (41) and fonts 1.3 MB (4). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (663 KiB) 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.

  • About 3.3 g of CO₂ per visit

    3.35 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 6779
  • 5 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (8 elements)

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

  • No main landmark

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

  • 9 tap targets too small

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

  • 2 links without text

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

  • 1 form field without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7777
  • No meta description

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

  • No structured data

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

  • 7 H1 headlines

    There are 7 <h1> headlines (“GENTING COMPANIES & KEY BRANDS”, “Business Divisions” and “Highlights”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

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

  • No X (Twitter) card tag

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

  • 67 internal links, 25 external

    The homepage links to 67 pages on genting.com and 25 external pages.

4 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Genting Group - Malaysia Leading Corporation”.

  • Canonical URL set

    The canonical URL is https://www.genting.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.genting.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (754 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://www.genting.com/zh-hans all use the title “Genting Group - Malaysia Leading Corporation”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.genting.com/energy, https://www.genting.com/zh-hans, https://www.genting.com/board-of-directors, https://www.genting.com/senior-management, https://www.genting.com/corporate_information and https://www.genting.com/genting-milestone and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.genting.com/genting-milestone, whose canonical is https://www.genting.com/genting-milestones. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages slow to respond

    https://www.genting.com/zh-hans, https://www.genting.com/board-of-directors, https://www.genting.com/genting-milestone, https://www.genting.com/stock-information, https://www.genting.com/ratings and https://www.genting.com/quarterly-reports took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5085
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 176 words

    The homepage has only about 176 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Stock Quote” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at genting.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
IP World Technologies Sdn. Bhd.

Company

Employees
56,000
Founded
1965
Headquarters
Kuala Lumpur

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on genting.com, including 19 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25