Website review, no card needed

dmiagrp.com logo

dmiagrp.com website review

Visit site (opens in a new tab)Reviewed 29 October 202627 issues · 67 checks

This review found 27 issues worth fixing on dmiagrp.com, 9 of them high impact, across 67 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.0 s1.4 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.3 s
May 23, 20261.9 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
104 ms84 msMay 9Oct 2497 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202696 ms
May 16, 202697 ms
May 23, 202693 ms
May 30, 202691 ms
Jun 6, 202697 ms
Jun 13, 202690 ms
Jun 20, 202694 ms
Jun 27, 202689 ms
Jul 4, 202686 ms
Jul 11, 202688 ms
Jul 18, 202688 ms
Jul 25, 202692 ms
Aug 1, 202694 ms
Aug 8, 202695 ms
Aug 15, 202697 ms
Aug 22, 202696 ms
Aug 29, 202694 ms
Sep 5, 202692 ms
Sep 12, 202691 ms
Sep 19, 202698 ms
Sep 26, 202699 ms
Oct 3, 2026101 ms
Oct 10, 2026100 ms
Oct 17, 2026102 ms
Oct 24, 202697 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 dmiagrp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dmiagrp.com at 0.7 s0.7 s
  2. dmiagrp.com at 1.3 s1.3 s
  3. dmiagrp.com at 2.0 s2.0 s
  4. dmiagrp.com at 2.6 s2.6 s
  5. dmiagrp.com at 3.3 s3.3 s
  6. dmiagrp.com at 3.9 s3.9 s
  7. dmiagrp.com at 4.6 s4.6 s
  8. dmiagrp.com at 5.2 s5.2 s

Speed

9 to fix62
  • Use efficient cache lifetimes

    6.3 s · 1.3 MB

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

  • Render-blocking requests

    4.0 s

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

  • Improve image delivery

    1.5 s · 319 KiB

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

  • Reduce unused CSS

    1.1 s · 124 KiB

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

  • Mobile performance score: 62

    62/100

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

  • Minify JavaScript

    600 ms · 95 KiB

    95 KiB could be saved by minifying JavaScript.

  • Reduce unused JavaScript

    450 ms · 101 KiB

    About 101 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.

  • Font display

    450 ms

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

  • Minify CSS

    300 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Analytics and Google Fonts), adding 97 KiB and 14 ms of main-thread time.

  • Legacy JavaScript

    12 KiB

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

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 120 ms

    120 ms

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

Core Web Vitals

6 to fix100
  • 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: 9.6 s

    9.6 s

    Your largest element takes 9.6 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: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

7 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 108 ms

    108 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

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

    -29%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.38 g

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

1 checks passed
  • Page weight: 1.4 MB in 57 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 57 requests on a phone: images 705 KiB (6), scripts 346 KiB (25) and stylesheets 166 KiB (20). That is a lean page.

Accessibility

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

  • 1 link without text

    1 link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

SEO

6 to fixGoogle 8582
  • Structured data has 2 problems

    Structured data found (Article, ImageObject, Organization and Person) but with 2 problems, for example “Organization: missing name”.

  • 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.dmiagrp.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • 3 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 38 internal links, 9 external

    The homepage links to 38 pages on dmiagrp.com and 9 external pages.

4 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “KVDT 1, KVDT 2, S2PV, KTMB, RAILWAYS MALAYSIA, TEKNOLOGI RAIL DI MALAYSIA, Dhaya Maju LTAT”.

  • One H1 headline

    Your main headline reads: “Our Awards & Certifications”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “DHAYA MAJU INFRASTRUCTURE (ASIA) SDN BERHAD (385996-H)”.

  • Canonical URL set

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

AI search readiness

1 to fix69
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.dmiagrp.com/railway has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.dmiagrp.com/railway has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.dmiagrp.com/railway took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    1 page 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

Google 100100
1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 413 words of visible text.

4 checks passed
  • 2 calls to action

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

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

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 dmiagrp.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
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 27 issues on dmiagrp.com, including 15 speed issues, 6 SEO issues and 1 conversion gap. 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