Website review, no card needed

eupe.com.my logo

eupe.com.my website review

Visit site (opens in a new tab)Reviewed 22 October 202630 issues · 79 checks

This review found 30 issues worth fixing on eupe.com.my, 11 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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.3 s1.8 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.0 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
104 ms89 msMay 2Oct 1796 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202694 ms
May 9, 202694 ms
May 16, 202696 ms
May 23, 202699 ms
May 30, 2026102 ms
Jun 6, 202696 ms
Jun 13, 202692 ms
Jun 20, 202693 ms
Jun 27, 202691 ms
Jul 4, 202694 ms
Jul 11, 202693 ms
Jul 18, 202693 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202695 ms
Aug 29, 202697 ms
Sep 5, 202697 ms
Sep 12, 202697 ms
Sep 19, 202694 ms
Sep 26, 202694 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202696 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 eupe.com.my (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eupe.com.my at 0.6 s0.6 s
  2. eupe.com.my at 1.1 s1.1 s
  3. eupe.com.my at 1.7 s1.7 s
  4. eupe.com.my at 2.2 s2.2 s
  5. eupe.com.my at 2.8 s2.8 s
  6. eupe.com.my at 3.4 s3.4 s
  7. eupe.com.my at 3.9 s3.9 s
  8. eupe.com.my at 4.5 s4.5 s

Speed

6 to fix57
  • Render-blocking requests

    3.8 s

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

  • Improve image delivery

    7.2 MB

    13 images could be 7.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 386 KiB

    About 386 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused CSS

    600 ms · 65 KiB

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

  • Google Tag Manager adds 378 ms

    378 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, AddToAny and Cloudflare and others), adding 499 KiB and 393 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. 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 129 ms. During a long task the page ignores taps.

  • Font display

    100 ms

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

  • Minify JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    5 KiB

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

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 9.4 s

    9.4 s

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

  • Time to Interactive: 21.9 s

    21.9 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Total Blocking Time: 67 ms

    67 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 11.4 MB in 47 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 47 requests on a phone: images 9.6 MB (22), scripts 1.1 MB (10) and fonts 579 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (3.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 3.2 g of CO₂ per visit

    3.22 g

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

2 checks passed
  • 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

2 to fixGoogle 9397
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 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 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 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 10078
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (175 characters)

    Your meta description is 175 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.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 48 internal links, 2 external

    The homepage links to 48 pages on eupe.com.my and 2 external pages.

4 checks passed
  • Title: 48 characters

    Your title is a healthy 48 characters: “Trust Innovation Value - Eupe Corporation Berhad”.

  • Canonical URL set

    The canonical URL is https://eupe.com.my/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://eupe.com.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://eupe.com.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,300 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix65
  • 1 page points its canonical at the homepage

    https://eupe.com.my/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 5 linked pages hidden from search

    https://eupe.com.my/community-event/propertyguru-asia-property-awards-2024, https://eupe.com.my/community-event/propertyguru-asia-awards-malaysia-2024, https://eupe.com.my/community-event/fiabci-world-prix-dexcellence-awards-2024, https://eupe.com.my/community-event/fiabci-malaysia-property-awards-2023 and https://eupe.com.my/community-event/propertyguru-asia-property-awards-grand-final-2023 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://eupe.com.my/home all use the title “Trust Innovation Value - Eupe Corporation Berhad”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://eupe.com.my/eupe-perspectives, https://eupe.com.my/our-awards and https://eupe.com.my/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://eupe.com.my/home, https://eupe.com.my/community-event/propertyguru-asia-property-awards-2024, https://eupe.com.my/community-event/propertyguru-asia-awards-malaysia-2024, https://eupe.com.my/community-event/fiabci-world-prix-dexcellence-awards-2024, https://eupe.com.my/community-event/fiabci-malaysia-property-awards-2023 and https://eupe.com.my/community-event/propertyguru-asia-property-awards-grand-final-2023 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 11 small tap targets

    11 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

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

2 to fix70
  • 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 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 form on the homepage

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

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

    The homepage carries about 1,286 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 eupe.com.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
Drupal
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on eupe.com.my, including 11 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