Website review, no card needed
firstsentierinvestors.com website review
Visit site (opens in a new tab)Reviewed 18 November 202635 issues · 84 checks
This review found 35 issues worth fixing on firstsentierinvestors.com, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 151 ms |
| Jun 6, 2026 | 158 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 176 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 176 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 151 ms |
| Oct 24, 2026 | 158 ms |
| Oct 31, 2026 | 146 ms |
| Nov 7, 2026 | 157 ms |
| Nov 14, 2026 | 153 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
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.3 s
3.9 s
4.5 s
Speed
Reduce unused JavaScript
2.1 s · 380 KiBAbout 380 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 468 KiB16 files are served with short cache lifetimes, so returning visitors download them again (468 KiB).
Render-blocking requests
1.1 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hubspot and Optanon and others), adding 768 KiB and 540 ms of main-thread time.
Minify JavaScript
460 ms · 99 KiB99 KiB could be saved by minifying JavaScript.
Google Tag Manager adds 368 ms
368 msGoogle Tag Manager costs a phone 368 ms of main-thread work and 401 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.
Reduce unused CSS
310 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 100 KiB3 images could be 100 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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.
1 checks passed
Server response: 224 ms
224 msYour server sent the HTML in 224 ms, well inside Google's 600 ms guideline.
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.
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 151 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 152 ms
152 msReal visitors wait 152 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 759 ms
759 msReal visitors wait 759 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 54.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 89 requests
1.6 MBYour homepage downloads 1.6 MB in 89 requests on a phone: scripts 980 KiB (18), images 312 KiB (38) and fonts 169 KiB (6). That is a lean page.
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
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.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 29 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“First Sentier Investors” and “Why First Sentier Investors?”). One clear main headline is easier for people and search engines.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
37 internal links, 6 external
The homepage links to 37 pages on firstsentierinvestors.com and 6 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Since our inception in 1988, we have evolved into a global fund manager with a client base that extends across Asia, Au…”.
Title: 60 characters
Your title is a healthy 60 characters: “Research-led investment management | First Sentier Investors”.
Canonical URL set
The canonical URL is https://www.firstsentierinvestors.com/.
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://www.firstsentierinvestors.com/sitemaps/sitemap_index.xml.
AI search readiness
Most text only appears after JavaScript runs
17%A phone browser shows 3,528 words, but the HTML your server sends has only 614. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://www.firstsentierinvestors.com/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.
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
7 pages share 2 titles
https://www.firstsentierinvestors.com/nz/en/institutional/home.html, https://www.firstsentierinvestors.com/nz/en/adviser/home.html and https://www.firstsentierinvestors.com/at/en/professional-investor/home.html all use the title “Research-led active investment management | First Sentier Investors”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages share a meta description
https://www.firstsentierinvestors.com/nz/en/institutional/home.html, https://www.firstsentierinvestors.com/nz/en/adviser/home.html and https://www.firstsentierinvestors.com/hk/en/retail/home.html use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.firstsentierinvestors.com/nz/en/institutional/home.html, whose canonical is https://www.firstsentierinvestors.com/nz/en/adviser/home.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
5 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.
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 15 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.firstsentierinvestors.com/libs/cq/experience-fragments/components/xfpage/conte…”.
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
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
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 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 3,528 words of copy
The homepage carries about 3,528 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before 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 (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 5 of them by other companies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 firstsentierinvestors.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 Tag Manager
- Hosting
- Corporation Service Company
Company
- Founded
- 1988
- Headquarters
- Sydney
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on firstsentierinvestors.com, including 17 speed issues, 3 SEO issues and 3 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.