Website review, no card needed

gmi.edu.my logo

gmi.edu.my website review

Visit site (opens in a new tab)Reviewed 1 November 202643 issues · 89 checks

This review found 43 issues worth fixing on gmi.edu.my, 22 of them high impact, across 89 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
6.3 s5.0 sMay 9Oct 245.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.4 s
May 16, 20265.3 s
May 23, 20265.3 s
May 30, 20265.4 s
Jun 6, 20265.4 s
Jun 13, 20265.5 s
Jun 20, 20265.8 s
Jun 27, 20266.0 s
Jul 4, 20266.1 s
Jul 11, 20265.8 s
Jul 18, 20265.6 s
Jul 25, 20265.5 s
Aug 1, 20265.2 s
Aug 8, 20265.4 s
Aug 15, 20265.3 s
Aug 22, 20265.2 s
Aug 29, 20265.2 s
Sep 5, 20265.3 s
Sep 12, 20265.3 s
Sep 19, 20265.2 s
Sep 26, 20265.3 s
Oct 3, 20265.2 s
Oct 10, 20265.1 s
Oct 17, 20265.2 s
Oct 24, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
285 ms191 msMay 9Oct 24274 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026226 ms
May 16, 2026226 ms
May 23, 2026218 ms
May 30, 2026215 ms
Jun 6, 2026217 ms
Jun 13, 2026211 ms
Jun 20, 2026214 ms
Jun 27, 2026212 ms
Jul 4, 2026220 ms
Jul 11, 2026215 ms
Jul 18, 2026212 ms
Jul 25, 2026212 ms
Aug 1, 2026202 ms
Aug 8, 2026209 ms
Aug 15, 2026218 ms
Aug 22, 2026229 ms
Aug 29, 2026240 ms
Sep 5, 2026250 ms
Sep 12, 2026252 ms
Sep 19, 2026252 ms
Sep 26, 2026257 ms
Oct 3, 2026264 ms
Oct 10, 2026266 ms
Oct 17, 2026269 ms
Oct 24, 2026274 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 gmi.edu.my (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gmi.edu.my at 1.8 s1.8 s
  2. gmi.edu.my at 3.5 s3.5 s
  3. gmi.edu.my at 5.3 s5.3 s
  4. gmi.edu.my at 7.1 s7.1 s
  5. gmi.edu.my at 8.8 s8.8 s
  6. gmi.edu.my at 10.6 s10.6 s
  7. gmi.edu.my at 12.4 s12.4 s
  8. gmi.edu.my at 14.1 s14.1 s

Speed

13 to fix38
  • Improve image delivery

    11.8 s · 7.6 MB

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

  • Reduce unused JavaScript

    5.8 s · 1.2 MB

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

  • Render-blocking requests

    4.8 s

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

  • Use efficient cache lifetimes

    1.1 s · 244 KiB

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

  • Font display

    1.1 s

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 4.9 s

    A phone's processor spends 4.9 s on main-thread work while loading, 2.4 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, Google Maps and Facebook and others), adding 2.1 MB and 1.4 s of main-thread time.

  • Google Tag Manager adds 651 ms

    651 ms

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

  • Reduce unused CSS

    300 ms · 156 KiB

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

  • Google Maps adds 250 ms

    250 ms

    Google Maps costs a phone 250 ms of main-thread work and 461 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.

  • 2,539 HTML elements

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

  • Google CDN adds 89 ms

    89 ms

    Google CDN costs a phone 89 ms of main-thread work and 348 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 208 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    29 KiB

    Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    9 KiB

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

1 checks passed
  • Server response: 225 ms

    225 ms

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

Core Web Vitals

11 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 LCP: 6.8 s

    6.8 s

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

  • Real-user FCP: 5.3 s

    5.3 s

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

  • Real-user TTFB: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 51.5 s

    51.5 s

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

    51.5 s

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

  • Speed Index: 15.3 s

    15.3 s

    Visually, the page fills in at 15.3 s (Speed Index). Good is under 3.4 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.

  • Total Blocking Time: 896 ms

    896 ms

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

  • Real-user INP: 298 ms

    298 ms

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

  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.032

    0.032

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

Images and page weight

4 to fix25
  • Page weight: 16.8 MB in 188 requests

    16.8 MB

    Your homepage downloads 16.8 MB in 188 requests on a phone: images 13.5 MB (25), scripts 2.6 MB (90) and fonts 378 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    icon-5-dark-blue-1-Photoroom-e1778638921624.png weighs 573 KiB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    729 KiB

    3 images are downloaded at several times the size a phone draws them, for example icon-5-dark-blue-1-Photoroom-e1778638921624.png at 1,070 px wide, shown at 32 px. Resized copies would save about 729 KiB.

  • 6 images in older formats

    6 images (1.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.

  • About 4.8 g of CO₂ per visit

    4.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.76 g of CO₂e: 571.4 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

5 to fixGoogle 8792
  • 12 text elements with low contrast

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

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 8580
  • No H1 headline

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

  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “GMI - German-Malaysian Institute. Best German Technology TVET Institute”.

  • 35 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 215 internal links, 59 external

    The homepage links to 215 pages on gmi.edu.my and 59 external pages.

6 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Build Your Future With Best German Technology TVET Institute. 22 Diploma & German University Pre-Preparatory Programmes…”.

  • Canonical URL set

    The canonical URL is https://www.gmi.edu.my/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gmi.edu.my/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.gmi.edu.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.

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 14 pages without a meta description

    https://www.gmi.edu.my/about, https://www.gmi.edu.my/board-of-directors, https://www.gmi.edu.my/management-team, https://www.gmi.edu.my/vision-mission, https://www.gmi.edu.my/alumni and https://www.gmi.edu.my/gmi-virtual-tour and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages slow to respond

    https://www.gmi.edu.my/about, https://www.gmi.edu.my/board-of-directors, https://www.gmi.edu.my/management-team, https://www.gmi.edu.my/vision-mission, https://www.gmi.edu.my/alumni and https://www.gmi.edu.my/pre-university-programme/german-a-level-preparatory-programme-gapp and 8 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 46 found) and read each the way a search engine does.

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

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

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

2 checks passed
  • Tap targets are thumb-sized

    44 of 45 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

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

  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

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

    The homepage carries about 471 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “APPLY NOW”, “Contact Form & Maps” and “Start Virtual Tour”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 19 cookies set on arrival

    19

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 gmi.edu.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
React
Analytics
Google Analytics | Google Tag Manager
Hosting
Extreme Broadband - Total Broadband Experience

Company

Founded
1991

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 gmi.edu.my, including 24 speed issues, 4 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