Website review, no card needed

tmone.com.my logo

tmone.com.my website review

Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 66 checks

This review found 33 issues worth fixing on tmone.com.my, 14 of them high impact, across 66 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.1 s970 msMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.4 s
Aug 8, 20262.3 s
Aug 15, 20262.1 s
Aug 22, 20261.7 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
142 ms114 msMay 9Oct 24127 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026139 ms
May 16, 2026137 ms
May 23, 2026129 ms
May 30, 2026128 ms
Jun 6, 2026117 ms
Jun 13, 2026122 ms
Jun 20, 2026122 ms
Jun 27, 2026135 ms
Jul 4, 2026134 ms
Jul 11, 2026128 ms
Jul 18, 2026127 ms
Jul 25, 2026122 ms
Aug 1, 2026123 ms
Aug 8, 2026133 ms
Aug 15, 2026126 ms
Aug 22, 2026122 ms
Aug 29, 2026127 ms
Sep 5, 2026122 ms
Sep 12, 2026127 ms
Sep 19, 2026128 ms
Sep 26, 2026123 ms
Oct 3, 2026123 ms
Oct 10, 2026125 ms
Oct 17, 2026126 ms
Oct 24, 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 tmone.com.my (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tmone.com.my at 2.4 s2.4 s
  2. tmone.com.my at 4.8 s4.8 s
  3. tmone.com.my at 7.2 s7.2 s
  4. tmone.com.my at 9.7 s9.7 s
  5. tmone.com.my at 12.1 s12.1 s
  6. tmone.com.my at 14.5 s14.5 s
  7. tmone.com.my at 16.9 s16.9 s
  8. tmone.com.my at 19.3 s19.3 s

Speed

8 to fix36
  • Use efficient cache lifetimes

    2.5 s · 4.3 MB

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

  • Reduce unused JavaScript

    2.5 s · 328 KiB

    About 328 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 36

    36/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Outbrain and LinkedIn Ads and others), adding 780 KiB and 597 ms of main-thread time.

  • Improve image delivery

    668 KiB

    6 images could be 668 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 550 ms

    550 ms

    Google Tag Manager costs a phone 550 ms of main-thread work and 680 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.

  • 1,976 HTML elements

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

  • Reduce unused CSS

    150 ms · 33 KiB

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

  • 6 long tasks on the main thread

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

  • 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: 1.8 s

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

  • Server response: 226 ms

    226 ms

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

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.

  • Real-user CLS: 0.33

    0.33

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

  • Largest Contentful Paint: 14.6 s

    14.6 s

    Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Smart Fleet Management System Limited Time 10% Discount GAI…”.

  • Speed Index: 25.3 s

    25.3 s

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

  • Time to Interactive: 22.8 s

    22.8 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Cumulative Layout Shift: 0.307

    0.307

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

  • Total Blocking Time: 244 ms

    244 ms

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -8%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 153 ms

    153 ms

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 382 ms

    382 ms

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

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

    -49%

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

Images and page weight

1 to fix33
  • Page weight: 5.1 MB in 109 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 109 requests on a phone: images 3.9 MB (52), scripts 932 KiB (22) and fonts 163 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.46 g

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

Accessibility

4 to fixGoogle 8880
  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 text elements with low contrast

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

  • ARIA progressbar elements do not have accessible names.

    ARIA progressbar elements do not have accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 5 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7780
  • Title is short (25 characters)

    Your title is only 25 characters: “TM One - Your Next Is Now”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 31 H1 headlines

    There are 31 <h1> headlines (“Building Digital Trust in the AI and Quantum Era:…”, “Here’s How Malaysia is Stepping Up Our ESG Efforts” and “Lebih Daripada Ketersambungan: Bagaimana SchoolNe…”). One clear main headline is easier for people and search engines.

  • 21 links with vague text

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

  • Meta description is long (198 characters)

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

  • 19 links crawlers can't follow

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

  • 149 internal links, 11 external

    The homepage links to 149 pages on tmone.com.my and 11 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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.tmone.com.my/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

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

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

Google 92100
  • Browser-reported issues

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • A 82-field form

    Your longest form asks for 82 fields (42 required). Every extra field lowers completion.

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

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

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

  • Urgency cues

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

2 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us”, “Learn More” and “Start”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 tmone.com.my, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on tmone.com.my, including 17 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