Website review, no card needed

ntuc.org.sg logo

ntuc.org.sg website review

Visit site (opens in a new tab)Reviewed 26 October 202647 issues · 89 checks

This review found 47 issues worth fixing on ntuc.org.sg, 18 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
1.8 s1.4 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
134 ms116 msMay 9Oct 24123 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026123 ms
May 16, 2026123 ms
May 23, 2026124 ms
May 30, 2026127 ms
Jun 6, 2026129 ms
Jun 13, 2026129 ms
Jun 20, 2026128 ms
Jun 27, 2026127 ms
Jul 4, 2026128 ms
Jul 11, 2026129 ms
Jul 18, 2026131 ms
Jul 25, 2026132 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026126 ms
Aug 22, 2026124 ms
Aug 29, 2026121 ms
Sep 5, 2026119 ms
Sep 12, 2026118 ms
Sep 19, 2026120 ms
Sep 26, 2026120 ms
Oct 3, 2026120 ms
Oct 10, 2026120 ms
Oct 17, 2026121 ms
Oct 24, 2026123 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 ntuc.org.sg (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ntuc.org.sg at 0.9 s0.9 s
  2. ntuc.org.sg at 1.8 s1.8 s
  3. ntuc.org.sg at 2.6 s2.6 s
  4. ntuc.org.sg at 3.5 s3.5 s
  5. ntuc.org.sg at 4.4 s4.4 s
  6. ntuc.org.sg at 5.3 s5.3 s
  7. ntuc.org.sg at 6.1 s6.1 s
  8. ntuc.org.sg at 7.0 s7.0 s

Speed

12 to fix46
  • Use efficient cache lifetimes

    6.7 s · 2.5 MB

    62 files are served with short cache lifetimes, so returning visitors download them again (2.5 MB).

  • Reduce unused JavaScript

    3.8 s · 1.5 MB

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

  • Render-blocking requests

    4.0 s

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

  • Reduce unused CSS

    2.5 s · 564 KiB

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

  • Mobile performance score: 46

    46/100

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

  • Improve image delivery

    10.0 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and LinkedIn Ads and others), adding 13.7 MB and 1.1 s of main-thread time.

  • sitecorecontenthub.cloud adds 0 ms

    0 ms

    sitecorecontenthub.cloud costs a phone 0 ms of main-thread work and 12.0 MB 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 724 ms

    724 ms

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

    20 ms · 382 KiB

    382 KiB could be saved by minifying JavaScript.

  • Facebook adds 314 ms

    314 ms

    Facebook costs a phone 314 ms of main-thread work and 478 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.

  • Main-thread work: 2.4 s

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Document request latency

    56 KiB

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

  • Minify CSS

    8 KiB

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

1 checks passed
  • Server response: 419 ms

    419 ms

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

Core Web Vitals

7 to fix100
  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 22.2 s

    22.2 s

    Your largest element takes 22.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “6 Main_Hero_Masthead 798x532_cost-of-living-02.png”.

  • Time to Interactive: 25.2 s

    25.2 s

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

  • Speed Index: 11.0 s

    11.0 s

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

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

    +20%

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

  • Total Blocking Time: 412 ms

    412 ms

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

7 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.0 s

    2.0 s

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

  • Real-user INP: 101 ms

    101 ms

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 641 ms

    641 ms

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

  • 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

5 to fix18
  • Page weight: 16.0 MB in 128 requests

    16.0 MB

    Your homepage downloads 16.0 MB in 128 requests on a phone: images 12.2 MB (44), scripts 2.8 MB (53) and stylesheets 614 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

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

  • 14 images far larger than shown

    5.5 MB

    14 images are downloaded at several times the size a phone draws them, for example 5cc229a925a54c50a02b89d7ad7dc394 at 1,663 px wide, shown at 358 px. Resized copies would save about 5.5 MB.

  • 22 images in older formats

    22 images (12.0 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.

  • 15 images below the first screen load straight away

    15 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.5 g of CO₂ per visit

    4.54 g

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

Accessibility

8 to fixGoogle 6683
  • Certain ARIA roles must contain particular children (4 elements)

    Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 15 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.

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

  • 5 links without text

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

1 checks passed
  • 27 automated accessibility rules passed

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

SEO

6 to fixGoogle 7765
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “NTUC Singapore | Championing Workers' Rights at Every Stage of Life”.

  • Structured data has 2 problems

    Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “Organization: missing name”.

  • No social preview image

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

  • 4 links with vague text

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

  • 92 internal links, 7 external

    The homepage links to 92 pages on ntuc.org.sg and 7 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.ntuc.org.sg/uportal/.

  • 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.ntuc.org.sg/uportal/searchsitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing name, 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.ntuc.org.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 (901 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.ntuc.org.sg/uportal/E-Services is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 pages without a meta description

    https://www.ntuc.org.sg/uportal/about-us, https://www.ntuc.org.sg/uportal/about-us/affiliated-unions, https://www.ntuc.org.sg/uportal/resource-hub, https://www.ntuc.org.sg/uportal/help-centre, https://www.ntuc.org.sg/uportal/about-us/careers-at-ntuc and https://www.ntuc.org.sg/uportal/E-Services and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.ntuc.org.sg/uportal/about-us/careers-at-ntuc, https://www.ntuc.org.sg/uportal/programmes, https://www.ntuc.org.sg/uportal/how-we-help/develop-your-career, https://www.ntuc.org.sg/uportal/how-we-help/protect-your-work-rights, https://www.ntuc.org.sg/uportal/how-we-help/care-for-your-family-and-health and https://www.ntuc.org.sg/uportal/how-we-help/manage-your-cost-of-living and 3 others 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 59 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.

  • 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 a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Swiper library is not loaded.”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

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

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

    The homepage carries about 865 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Singtel-Star-Buy-Offers”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact us”, “Learn more” and “Singtel-Star-Buy-Offers”.

  • Analytics in place

    Analytics detected: Google Tag Manager and LinkedIn Insight.

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

  • 8 cookies set on arrival

    8

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

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

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 ntuc.org.sg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Azure

Company

Founded
1961
Headquarters
Downtown Core

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on ntuc.org.sg, including 19 speed issues, 6 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