Website review, no card needed

aem.com.sg logo

aem.com.sg website review

Visit site (opens in a new tab)Reviewed 27 October 202629 issues · 80 checks

This review found 29 issues worth fixing on aem.com.sg, 11 of them high impact, across 80 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 s751 msMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 2026942 ms
May 16, 2026930 ms
May 23, 20261.0 s
May 30, 20261.1 s
Jun 6, 20261.2 s
Jun 13, 20261.4 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.3 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
102 ms79 msMay 9Oct 2486 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202682 ms
May 16, 202682 ms
May 23, 202685 ms
May 30, 202687 ms
Jun 6, 202688 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202688 ms
Jul 11, 202693 ms
Jul 18, 202699 ms
Jul 25, 202697 ms
Aug 1, 202692 ms
Aug 8, 202687 ms
Aug 15, 202683 ms
Aug 22, 202685 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202688 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202690 ms
Oct 10, 202686 ms
Oct 17, 202685 ms
Oct 24, 202686 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 aem.com.sg (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aem.com.sg at 0.5 s0.5 s
  2. aem.com.sg at 0.9 s0.9 s
  3. aem.com.sg at 1.4 s1.4 s
  4. aem.com.sg at 1.9 s1.9 s
  5. aem.com.sg at 2.3 s2.3 s
  6. aem.com.sg at 2.8 s2.8 s
  7. aem.com.sg at 3.2 s3.2 s
  8. aem.com.sg at 3.7 s3.7 s

Speed

5 to fix65
  • Render-blocking requests

    5.0 s

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

  • Reduce unused CSS

    2.0 s · 397 KiB

    About 397 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Font display

    1.0 s

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

  • Mobile performance score: 65

    65/100

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

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 385 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Hubspot and Cloudflare CDN and others), adding 780 KiB and 337 ms of main-thread time.

  • Reduce unused JavaScript

    211 KiB

    About 211 KiB of JavaScript is downloaded but never used on this page.

  • Legacy JavaScript

    150 ms · 30 KiB

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

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    122 KiB

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

  • Minify CSS

    43 KiB

    43 KiB could be saved by minifying CSS.

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

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

  • Server response: 212 ms

    212 ms

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

Core Web Vitals

8 to fix100
  • 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: 4.7 s

    4.7 s

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

  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Testing Innovation Innovative, full-stack solutions, tailor…”.

  • Time to Interactive: 9.1 s

    9.1 s

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

  • Speed Index: 6.4 s

    6.4 s

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

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

    +122%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 89 ms

    89 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Total Blocking Time: 165 ms

    165 ms

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

1 to fix70
  • Page weight: 11.6 MB in 90 requests

    11.6 MB

    Your homepage downloads 11.6 MB in 90 requests on a phone: media 8.6 MB (2), fonts 1.7 MB (5) and scripts 681 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • About 3.3 g of CO₂ per visit

    3.28 g

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

4 to fixGoogle 9395
  • 17 text elements with low contrast

    17 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 (3 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is short (13 characters)

    Your title is only 13 characters: “AEM Singapore”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 links with vague text

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

  • 54 internal links, 14 external

    The homepage links to 54 pages on aem.com.sg and 14 external pages.

7 checks passed
  • Meta description: 82 characters

    Your meta description is 82 characters: “Innovative, full-stack solutions, tailored for advanced semiconductor technologies”.

  • One H1 headline

    Your main headline reads: “Testing Innovation”.

  • Canonical URL set

    The canonical URL is https://aem.com.sg/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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://aem.com.sg/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://aem.com.sg/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 (975 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://aem.com.sg/privacy-policy and https://aem.com.sg/personal-data-policy all use the title “Privacy Policy - AEM”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://aem.com.sg/privacy-policy and https://aem.com.sg/personal-data-policy use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://aem.com.sg/personal-data-policy, whose canonical is https://aem.com.sg/privacy-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://aem.com.sg/careers, https://aem.com.sg/terms-of-use, https://aem.com.sg/privacy-policy and https://aem.com.sg/personal-data-policy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://aem.com.sg/personal-data-policy took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 500 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Learn more” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and HubSpot.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 6 cookies set on arrival

    6

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 aem.com.sg, 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 Analytics
Hosting
DigitalOcean

Company

Headquarters
Singapore

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on aem.com.sg, including 13 speed issues, 2 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