Website review, no card needed

alam.edu.my logo

alam.edu.my website review

Visit site (opens in a new tab)Reviewed 18 October 202645 issues · 92 checks

This review found 45 issues worth fixing on alam.edu.my, 18 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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.9 s1.7 sApr 25Oct 102.5 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.8 s
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.2 s
Sep 19, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
222 ms181 msApr 25Oct 10191 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026217 ms
May 2, 2026216 ms
May 9, 2026215 ms
May 16, 2026207 ms
May 23, 2026204 ms
May 30, 2026202 ms
Jun 6, 2026205 ms
Jun 13, 2026209 ms
Jun 20, 2026209 ms
Jun 27, 2026207 ms
Jul 4, 2026205 ms
Jul 11, 2026203 ms
Jul 18, 2026197 ms
Jul 25, 2026194 ms
Aug 1, 2026186 ms
Aug 8, 2026188 ms
Aug 15, 2026195 ms
Aug 22, 2026197 ms
Aug 29, 2026204 ms
Sep 5, 2026198 ms
Sep 12, 2026200 ms
Sep 19, 2026197 ms
Sep 26, 2026195 ms
Oct 3, 2026195 ms
Oct 10, 2026191 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 alam.edu.my (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alam.edu.my at 1.4 s1.4 s
  2. alam.edu.my at 2.8 s2.8 s
  3. alam.edu.my at 4.2 s4.2 s
  4. alam.edu.my at 5.6 s5.6 s
  5. alam.edu.my at 7.0 s7.0 s
  6. alam.edu.my at 8.4 s8.4 s
  7. alam.edu.my at 9.8 s9.8 s
  8. alam.edu.my at 11.2 s11.2 s

Speed

11 to fix35
  • Reduce unused JavaScript

    6.3 s · 817 KiB

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

  • Use efficient cache lifetimes

    3.4 s · 878 KiB

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

  • Render-blocking requests

    3.8 s

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

  • Font display

    3.0 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 7.3 s

    A phone's processor spends 7.3 s on main-thread work while loading, 3.3 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 CDN, Google Tag Manager and Facebook and others), adding 1.9 MB and 1.6 s of main-thread time.

  • Reduce unused CSS

    750 ms · 163 KiB

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

  • Google CDN adds 477 ms

    477 ms

    Google CDN costs a phone 477 ms of main-thread work and 733 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.

  • Google Tag Manager adds 405 ms

    405 ms

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

    300 ms · 43 KiB

    43 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 53 KiB

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

  • 17 long tasks on the main thread

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

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

  • Improve image delivery

    12 KiB

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

  • 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: 476 ms

    476 ms

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

Core Web Vitals

12 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: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 28.8 s

    28.8 s

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

  • Speed Index: 18.9 s

    18.9 s

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

  • Time to Interactive: 29.0 s

    29.0 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

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

  • Real-user INP: 228 ms

    228 ms

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

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

    +39%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 2 images without width and height

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

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

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

    -11%

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

  • Cumulative Layout Shift: 0.034

    0.034

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 160 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 160 requests on a phone: scripts 2.1 MB (52), images 1.8 MB (25) and fonts 541 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.45 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 7790
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 7 text elements with low contrast

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

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

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

  • No main landmark

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

  • Zoom is disabled

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

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

  • 17 links without text

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

  • 8 form fields without a label

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

  • 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 20 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

5 to fixGoogle 9273
  • No H1 headline

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

  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Maritime Education - Shaping Maritime Professionals | Akademi Laut Malaysia”.

  • Meta description is long (227 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 89 internal links, 20 external

    The homepage links to 89 pages on alam.edu.my and 20 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

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

  • 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.alam.edu.my/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.alam.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 (739 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 10 pages without a meta description

    https://www.alam.edu.my/programmes, https://www.alam.edu.my/programmes/cadetship-diploma, https://www.alam.edu.my/courses/diploma-in-nautical-studies, https://www.alam.edu.my/courses/diploma-in-maritime-transportation-and-logistics, https://www.alam.edu.my/courses/diploma-in-maritime-business-administration and https://www.alam.edu.my/courses/diploma-in-maritime-management and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.alam.edu.my/courses/diploma-in-marine-engineering, https://www.alam.edu.my/courses/dmet and https://www.alam.edu.my/courses/catering-rating use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.alam.edu.my/programmes/cadetship-diploma, whose canonical is https://www.alam.edu.my/courses/cadetship-diploma. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages slow to respond

    https://www.alam.edu.my/programmes/cadetship-diploma, https://www.alam.edu.my/courses/dmet, https://www.alam.edu.my/courses/diploma-in-maritime-transportation-and-logistics and https://www.alam.edu.my/courses/diploma-in-maritime-business-administration took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

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

Best practices

2 to fixGoogle 9687
  • 22 small tap targets

    22 of 53 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 “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • A 8-field form

    Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

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

    The homepage carries about 688 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: “ENQUIRE NOW” and “APPLY NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Apply Now”, “Enquire now” and “LEARN MORE”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 7 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Hotjar.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies (measured from a US location before any click).

  • 33 other companies contacted

    Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 alam.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
jQuery
Analytics
Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on alam.edu.my, including 23 speed issues, 5 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