Website review, no card needed

cidb.gov.my logo

cidb.gov.my website review

Visit site (opens in a new tab)Reviewed 4 November 202647 issues · 93 checks

This review found 47 issues worth fixing on cidb.gov.my, 19 of them high impact, across 93 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
2.8 s2.5 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.7 s
Jun 20, 20262.8 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
609 ms384 msMay 16Oct 31474 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026555 ms
May 23, 2026575 ms
May 30, 2026583 ms
Jun 6, 2026583 ms
Jun 13, 2026558 ms
Jun 20, 2026558 ms
Jun 27, 2026546 ms
Jul 4, 2026539 ms
Jul 11, 2026542 ms
Jul 18, 2026523 ms
Jul 25, 2026513 ms
Aug 1, 2026496 ms
Aug 8, 2026489 ms
Aug 15, 2026487 ms
Aug 22, 2026483 ms
Aug 29, 2026476 ms
Sep 5, 2026459 ms
Sep 12, 2026430 ms
Sep 19, 2026416 ms
Sep 26, 2026410 ms
Oct 3, 2026416 ms
Oct 10, 2026435 ms
Oct 17, 2026445 ms
Oct 24, 2026462 ms
Oct 31, 2026474 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 cidb.gov.my (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cidb.gov.my at 1.2 s1.2 s
  2. cidb.gov.my at 2.4 s2.4 s
  3. cidb.gov.my at 3.6 s3.6 s
  4. cidb.gov.my at 4.8 s4.8 s
  5. cidb.gov.my at 6.1 s6.1 s
  6. cidb.gov.my at 7.3 s7.3 s
  7. cidb.gov.my at 8.5 s8.5 s
  8. cidb.gov.my at 9.7 s9.7 s

Speed

15 to fix32
  • Use efficient cache lifetimes

    4.3 s · 6.9 MB

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

  • Render-blocking requests

    5.5 s

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

  • Reduce unused JavaScript

    2.3 s · 1.1 MB

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

  • Reduce unused CSS

    1.2 s · 355 KiB

    About 355 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: 32

    32/100

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

  • Main-thread work: 6.8 s

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

  • 4,029 HTML elements

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

  • Improve image delivery

    500 ms · 1.7 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Facebook and TikTok and others), adding 2.6 MB and 1.3 s of main-thread time.

  • YouTube adds 453 ms

    453 ms

    YouTube costs a phone 453 ms of main-thread work and 1.3 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.

  • Legacy JavaScript

    350 ms · 51 KiB

    Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Facebook adds 330 ms

    330 ms

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

  • Font display

    300 ms

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

  • 20 long tasks on the main thread

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

  • daythree.net adds 174 ms

    174 ms

    daythree.net costs a phone 174 ms of main-thread work and 602 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.

  • Minify JavaScript

    150 ms · 32 KiB

    32 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 28 ms

    28 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user INP: 573 ms

    573 ms

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

  • Largest Contentful Paint: 17.9 s

    17.9 s

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

  • Time to Interactive: 32.7 s

    32.7 s

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

  • Speed Index: 13.0 s

    13.0 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 3.0 s

    3.0 s

    Real visitors wait 3.0 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.

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user CLS: 0.07

    0.07

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

  • Real-user TTFB: 624 ms

    624 ms

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

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

4 to fix38
  • Page weight: 16.2 MB in 333 requests

    16.2 MB

    Your homepage downloads 16.2 MB in 333 requests on a phone: images 5.8 MB (99), media 5.3 MB (1) and scripts 3.0 MB (106). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Pemakluman-Polisi-Baharu-PKK-CIDB-di-Laman-Web-Media-sosial- weighs 661 KiB. On a phone connection a single image that size takes seconds.

  • 14 images below the first screen load straight away

    14 images further down the page (504 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    38 KiB

    1 image is downloaded at several times the size a phone draws it, for example KKR-CIDB-White-ok.png at 1,380 px wide, shown at 237 px. Resized copies would save about 38 KiB.

  • 6 images in older formats

    6 images (273 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 4.6 g of CO₂ per visit

    4.59 g

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

Accessibility

10 to fixGoogle 8090
  • 60 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 13 links without text

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

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • Alternative text of images should not be repeated as text (6 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 87 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“Pendaftaran Personel Binaan” and “Pendaftaran Kontraktor”). One clear main headline is easier for people and search engines.

  • 14 links crawlers can't follow

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

  • 561 internal links, 63 external

    The homepage links to 561 pages on cidb.gov.my and 63 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “CIDB Adalah Sebuah Agensi Kerajaan Malaysia Menawarkan Pelbagai Program Untuk Industri Pembinaan Seperti Pendaftaran Pe…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “CIDB Malaysia | Lembaga Pembangunan Industri Pembinaan”.

  • Canonical URL set

    The canonical URL is https://www.cidb.gov.my/.

  • Structured data in place

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.cidb.gov.my/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.cidb.gov.my/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.

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

  • 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,826 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    / and https://www.cidb.gov.my/eng all use the title “CIDB Malaysia | Lembaga Pembangunan Industri Pembinaan”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.cidb.gov.my/e-bantuan, https://www.cidb.gov.my/latar-belakang, https://www.cidb.gov.my/fungsi, https://www.cidb.gov.my/visi-misi, https://www.cidb.gov.my/nilai-teras and https://www.cidb.gov.my/anggota-lembaga-cidb and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

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

Best practices

2 to fixGoogle 6991
  • 5 third-party cookies

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    22 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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: 32 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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,214 words of copy

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

4 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Learn more”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Matomo, TikTok Pixel and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 cidb.gov.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 | Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on cidb.gov.my, including 24 speed issues, 2 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