Website review, no card needed

cbd.com.my logo

cbd.com.my website review

Visit site (opens in a new tab)Reviewed 31 October 202643 issues · 84 checks

This review found 43 issues worth fixing on cbd.com.my, 18 of them high impact, across 84 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

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

How it loaded on a phone

  1. cbd.com.my at 1.6 s1.6 s
  2. cbd.com.my at 3.3 s3.3 s
  3. cbd.com.my at 4.9 s4.9 s
  4. cbd.com.my at 6.6 s6.6 s
  5. cbd.com.my at 8.2 s8.2 s
  6. cbd.com.my at 9.9 s9.9 s
  7. cbd.com.my at 11.5 s11.5 s
  8. cbd.com.my at 13.2 s13.2 s

Speed

11 to fix48
  • Use efficient cache lifetimes

    2.4 s · 10.8 MB

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

  • Font display

    1.7 s

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

  • YouTube adds 1.1 s

    1.1 s

    YouTube costs a phone 1.1 s of main-thread work and 1.9 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.

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 5.3 s

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

  • Improve image delivery

    450 ms · 3.8 MB

    20 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused JavaScript

    900 ms · 1.3 MB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.4 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    600 ms · 253 KiB

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

  • Render-blocking requests

    800 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 800 ms.

  • 2,523 HTML elements

    The page has 2,523 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix48
  • Time to Interactive: 23.6 s

    23.6 s

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

  • Speed Index: 13.3 s

    13.3 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Be Our Business Partner Have you been in real estate busine…”. Most of its time is resource load delay (6.5 s).

  • Total Blocking Time: 704 ms

    704 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

3 to fix50
  • Page weight: 13.4 MB in 188 requests

    13.4 MB

    Your homepage downloads 13.4 MB in 188 requests on a phone: images 10.5 MB (143), scripts 2.2 MB (16) and fonts 281 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (744 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.

  • 6 images far larger than shown

    100 KiB

    6 images are downloaded at several times the size a phone draws them, for example 2020-05-07-04_43_48-Property-prices-expected-to-decline-by-a at 300 px wide, shown at 98 px. Resized copies would save about 100 KiB.

  • About 3.8 g of CO₂ per visit

    3.81 g

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

1 checks passed
  • Images load when needed

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

Accessibility

11 to fixGoogle 7786
  • 8 text elements with low contrast

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

  • 2 tap targets too small

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 141 links without text

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

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

    All page content should be contained by landmarks: 16 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 136 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

7 to fixGoogle 9274
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Home - CBD Properties - Find Local And International Properties Now!”.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Be Our Business Partner”, “CBD” and “CBD”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • No XML sitemap

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

  • No robots.txt

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • 417 internal links, 20 external

    The homepage links to 417 pages on cbd.com.my and 20 external pages.

3 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Real estate business done the right way. Market Research & Evaluation, Concept Development Retail Layout & Tenant Mix P…”.

  • Canonical URL set

    The canonical URL is https://www.cbd.com.my/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 11 pages without a meta description

    https://www.cbd.com.my/management-team, https://www.cbd.com.my/cbd-in-the-media, https://www.cbd.com.my/cbd-retail, https://www.cbd.com.my/cbd-industrial-services, https://www.cbd.com.my/projects-launching-roadshow and https://www.cbd.com.my/corporateoffice and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages with very little text

    https://www.cbd.com.my/award-recognition, https://www.cbd.com.my/cbd-in-the-media, https://www.cbd.com.my/cbd-industrial-services, https://www.cbd.com.my/projects-launching-roadshow and https://www.cbd.com.my/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.

  • 9 pages slow to respond

    https://www.cbd.com.my/about-us, https://www.cbd.com.my/management-team, https://www.cbd.com.my/award-recognition, https://www.cbd.com.my/cbd-in-the-media, https://www.cbd.com.my/cbd-retail and https://www.cbd.com.my/auctions and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 small tap targets

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

  • 2 JavaScript errors while loading

    2 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 (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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.

  • No social proof

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

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

  • About 2,040 words of copy

    The homepage carries about 2,040 words of visible text.

4 checks passed
  • 2 calls to action

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

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 1 of them by other companies (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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 cbd.com.my, 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
Exa Bytes Network Sdn.Bhd.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on cbd.com.my, including 15 speed issues, 7 SEO issues and 2 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