Website review, no card needed
sunlifemalaysia.com website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 73 checks
This review found 42 issues worth fixing on sunlifemalaysia.com, 18 of them high impact, across 73 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 148 ms |
| May 23, 2026 | 155 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 142 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 184 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 134 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 131 ms |
| Oct 10, 2026 | 132 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 132 ms |
| Oct 31, 2026 | 131 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
How it loaded on a phone
1.8 s
3.6 s
5.4 s
7.2 s
9.0 s
10.9 s
12.7 s
14.5 s
Speed
Render-blocking requests
16.6 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 16.6 s.
Reduce unused JavaScript
3.6 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Reduce unused CSS
2.6 s · 462 KiBAbout 462 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Font display
2.5 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.5 s).
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
500 ms · 5.1 MB22 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, infobip.com and Facebook and others), adding 2.0 MB and 1.3 s of main-thread time.
Google Tag Manager adds 844 ms
844 msGoogle Tag Manager costs a phone 844 ms of main-thread work and 1.1 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.
Use efficient cache lifetimes
600 ms · 213 KiB14 files are served with short cache lifetimes, so returning visitors download them again (213 KiB).
Document request latency
550 ms · 68 KiBThe HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
551 msReduce initial server response time. Google estimates savings of 551 ms on a phone.
infobip.com adds 283 ms
283 msinfobip.com costs a phone 283 ms of main-thread work and 555 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.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.3 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 269 ms. During a long task the page ignores taps.
Server response: 651 ms
651 msYour server takes 651 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
150 ms · 91 KiBPolyfills for old browsers add 91 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
190 ms · 35 KiB35 KiB could be saved by minifying CSS.
Minify JavaScript
40 ms · 42 KiB42 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.
Core Web Vitals
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 FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 17.8 s
17.8 sThe first text or image appears after 17.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 23.5 s
23.5 sYour largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 34.5 s
34.5 sVisually, the page fills in at 34.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 60.2 s
60.2 sThe page becomes fully interactive after 60.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.256
0.256The layout shifts by 0.256 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 978 ms
978 msReal visitors wait 978 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 368 ms
368 msScripts block taps and scrolling for 368 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 157 ms
157 msReal visitors wait 157 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 148 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.3 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.3 MB in 128 requests
12.3 MBYour homepage downloads 12.3 MB in 128 requests on a phone: images 6.8 MB (44), scripts 4.2 MB (37) and fonts 752 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 3.5 g of CO₂ per visit
3.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.49 g of CO₂e: 419.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
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.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
5 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (27 characters)
Your title is only 27 characters: “Sunlife | Sun Life Malaysia”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
13 links with vague text
13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
145 internal links, 36 external
The homepage links to 145 pages on sunlifemalaysia.com and 36 external pages.
4 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “We offer a comprehensive range of life insurance & Family Takaful products and services to meet your different protecti…”.
Canonical URL set
The canonical URL is https://www.sunlifemalaysia.com/.
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.sunlifemalaysia.com/sitemap.xml.
AI search readiness
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.
1 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.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 1,436 words of copy
The homepage carries about 1,436 words of visible text.
4 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Fund pricing”, “Profit Equalisation Reserve (PER)” and “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 sunlifemalaysia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Ttssb My Tm Technology Services Sdn. Bhd.
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on sunlifemalaysia.com, including 26 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.