rwgenting.com website review

About 3.1 MB 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.

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

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

243 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

91 images could be 82.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Amazon Web Services and others), adding 3.5 MB and 2.3 s of main-thread time.

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

Amazon Web Services costs a phone 368 ms of main-thread work and 1.7 MB 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,173 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

cloudfront.net costs a phone 33 ms of main-thread work and 367 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.

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

29 KiB could be saved by minifying CSS.

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

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.

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

Your largest element takes 404.3 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 428.5 s. Good is under 3.8 s.

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

The layout shifts by 0.583 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

18 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' largest content (lcp) went from 2.7 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 132.5 MB in 369 requests on a phone: images 97.9 MB (170), other files 29.8 MB (106) and scripts 4.4 MB (56). Under 2 MB keeps phones on slow connections fast.

15 images weigh 48.4 MB together. On a phone connection a single image that size takes seconds.

18 images are downloaded at several times the size a phone draws them, for example 720x720px.jpg at 3,000 px wide, shown at 319 px. Resized copies would save about 37.9 MB.

38 images (53.8 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.

33 images further down the page (50.6 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 37.56 g of CO₂e: 4506.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 dropdown has no label.

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

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

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

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

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

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

ARIA role should be appropriate for the element: 18 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 12 elements on the page fail this check, rated minor by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

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

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

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

The homepage links to 256 pages on rwgenting.com and 47 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.

There is no https://rwgenting.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.

/ and https://rwgenting.com/en.html all use the title “Homepage | Resorts World Genting”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rwgenting.com/en/mice/packages-special-events.html has no meta description, so Google writes the search snippet from whatever text it finds.

https://rwgenting.com/en/advisory/keep-your-data-safe.html, https://rwgenting.com/en/advisory/alert-on-a-syndicate.html, https://rwgenting.com/en/advisory/important-notice-20230602.html, https://rwgenting.com/en/advisory/fake-video-alert-20240815.html, https://rwgenting.com/en/advisory/ai-generated-fake-videos.html and https://rwgenting.com/en/advisory/frauds-alert.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://rwgenting.com/.

6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://analytics.tiktok.com/i18n/pixel/events.js?sdkid=DB6SB83C77U985BSN7R0&lib=ttq' violates the …”.

4 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

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.

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

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 1,010 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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