Website review, no card needed

mhglobal.com logo

mhglobal.com website review

Visit site (opens in a new tab)Reviewed 23 October 202652 issues · 91 checks

This review found 52 issues worth fixing on mhglobal.com, 25 of them high impact, across 91 checks. The most urgent: improve image delivery. 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.5 s2.6 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.0 s
Aug 1, 20262.9 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.3 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.2 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
202 ms121 msMay 2Oct 17140 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026148 ms
May 9, 2026146 ms
May 16, 2026144 ms
May 23, 2026149 ms
May 30, 2026150 ms
Jun 6, 2026150 ms
Jun 13, 2026161 ms
Jun 20, 2026160 ms
Jun 27, 2026171 ms
Jul 4, 2026182 ms
Jul 11, 2026188 ms
Jul 18, 2026193 ms
Jul 25, 2026179 ms
Aug 1, 2026166 ms
Aug 8, 2026142 ms
Aug 15, 2026136 ms
Aug 22, 2026131 ms
Aug 29, 2026133 ms
Sep 5, 2026130 ms
Sep 12, 2026137 ms
Sep 19, 2026142 ms
Sep 26, 2026139 ms
Oct 3, 2026139 ms
Oct 10, 2026138 ms
Oct 17, 2026140 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 mhglobal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mhglobal.com at 1.5 s1.5 s
  2. mhglobal.com at 3.0 s3.0 s
  3. mhglobal.com at 4.4 s4.4 s
  4. mhglobal.com at 5.9 s5.9 s
  5. mhglobal.com at 7.4 s7.4 s
  6. mhglobal.com at 8.9 s8.9 s
  7. mhglobal.com at 10.3 s10.3 s
  8. mhglobal.com at 11.8 s11.8 s

Speed

15 to fix29
  • Improve image delivery

    34.5 s · 9.9 MB

    21 images could be 9.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 34.5 s faster on a phone.

  • Reduce unused JavaScript

    6.5 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 6.5 s faster on a phone.

  • Font display

    1.8 s

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

  • Render-blocking requests

    1.6 s

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 1.2 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: 29

    29/100

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

  • 7,155 HTML elements

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

  • Main-thread work: 6.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, jotform.com and TikTok and others), adding 1.9 MB and 2.2 s of main-thread time.

  • Document request latency

    700 ms · 907 KiB

    The HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused CSS

    739 KiB

    About 739 KiB of CSS is downloaded but never applied on this page.

  • Reduce initial server response time

    683 ms

    Reduce initial server response time. Google estimates savings of 683 ms on a phone.

  • jotform.com adds 481 ms

    481 ms

    jotform.com costs a phone 481 ms of main-thread work and 351 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 on the main thread

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

  • Server response: 783 ms

    783 ms

    Your server takes 783 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Use efficient cache lifetimes

    129 KiB

    34 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).

  • Legacy JavaScript

    48 KiB

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

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.

  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 86.0 s

    86.0 s

    Your largest element takes 86.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Blog”.

  • Speed Index: 38.8 s

    38.8 s

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

  • Time to Interactive: 103.0 s

    103.0 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) got 15% slower for real visitors

    +15%

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

3 checks passed
  • Real-user INP: 140 ms

    140 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix18
  • Page weight: 20.2 MB in 127 requests

    20.2 MB

    Your homepage downloads 20.2 MB in 127 requests on a phone: images 16.0 MB (63), scripts 2.4 MB (34) and HTML 1.3 MB (3). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 5.6 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    2.0 MB

    12 images are downloaded at several times the size a phone draws them, for example 1400x700_Apparels-1400x700.png at 1,400 px wide, shown at 429 px. Resized copies would save about 2.0 MB.

  • 25 images in older formats

    25 images (8.1 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.

  • 5 images below the first screen load straight away

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

  • About 5.7 g of CO₂ per visit

    5.73 g

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

Accessibility

7 to fixGoogle 8290
  • 3 buttons without a name

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

  • 69 text elements with low contrast

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

  • 3 tap targets too small

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • 16 links without text

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

  • 2 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 444 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

7 to fixGoogle 8364
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

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

  • 200 links crawlers can't follow

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (183 characters)

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

  • Structured data has 1 problem

    Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

  • No XML sitemap

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

  • 533 internal links, 11 external

    The homepage links to 533 pages on mhglobal.com and 11 external pages.

2 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Premium Gift Malaysia | Corporate Gift Supplier Kuala Lumpur”.

  • Open Graph tags complete

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

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Organization data is thin (3 of 6 facts)

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

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

2 to fix90
  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://mhglobal.com/awards/3d-printed-custom-awards, whose canonical is https://mhglobal.com/3d-printed-custom-awards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://mhglobal.com/campaign-election-essentials-malaysia, https://mhglobal.com/custom-printing-packaging, https://mhglobal.com/awards, https://mhglobal.com/awards/3d-printed-custom-awards, https://mhglobal.com/CORPORATE-APPARELS and https://mhglobal.com/CORPORATE-APPARELS/corporate-uniform-malaysia and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages slow to respond

    https://mhglobal.com/campaign-election-essentials-malaysia, https://mhglobal.com/custom-printing-packaging, https://mhglobal.com/awards, https://mhglobal.com/awards/3d-printed-custom-awards, https://mhglobal.com/CORPORATE-APPARELS and https://mhglobal.com/CORPORATE-APPARELS/corporate-uniform-malaysia and 5 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 195 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

    7 of 34 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 “Invalid or unexpected token”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • About 2,457 words of copy

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

7 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “CONTACT US : 03-2280 2177” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, LinkedIn Insight and TikTok Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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, LinkedIn Insight 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.

  • 16 cookies set on arrival

    16

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 mhglobal.com, 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 52 issues on mhglobal.com, including 24 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