Website review, no card needed
polarcapitalfunds.com website review
Visit site (opens in a new tab)Reviewed 26 October 202636 issues · 80 checks
This review found 36 issues worth fixing on polarcapitalfunds.com, 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 103 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 101 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 128 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 113 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.5 s
1.0 s
1.5 s
2.0 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Render-blocking requests
3.6 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and jQuery CDN and others), adding 1.6 MB and 1.5 s of main-thread time.
Reduce unused CSS
850 ms · 162 KiBAbout 162 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 850 ms faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 83). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
790 KiBAbout 790 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 702 ms
702 msGoogle Tag Manager costs a phone 702 ms of main-thread work and 639 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.
Google CDN adds 594 ms
594 msGoogle CDN costs a phone 594 ms of main-thread work and 734 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.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 261 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 8 KiB2 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).
Improve image delivery
79 KiB4 images could be 79 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 83 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 266 ms
266 msYour server sent the HTML in 266 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 646 ms
646 msScripts block taps and scrolling for 646 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies. By continuing to browse the site yo…”. Most of its time is element render delay (1.9 s).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 103 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.081
0.081The layout barely moves while loading (CLS 0.081, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 71 requests
3.5 MBYour homepage downloads 3.5 MB in 71 requests on a phone: scripts 1.6 MB (25), images 1.3 MB (21) and other files 354 KiB (9). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (907 KiB) 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 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.7 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“We look for investment opportunities by creating …”, “A research-driven investment management company” and “Meet the team”). One clear main headline is easier for people and search engines.
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
42 internal links, 4 external
The homepage links to 42 pages on polarcapitalfunds.com and 4 external pages.
6 checks passed
Title: 63 characters
Your title is a healthy 63 characters: “Specialist, investment-led, active fund manager | Polar Capital”.
Canonical URL set
The canonical URL is https://www.polarcapitalfunds.com/us/individual/.
Structured data in place
Structured data found: Organization and WebSite.
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.polarcapitalfunds.com/us/advisor/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.polarcapitalfunds.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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (472 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.polarcapitalfunds.com/.
6 small tap targets
6 of 14 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 “UK is not defined”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 405 words of copy
The homepage carries about 405 words of visible text.
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Register”.
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
13 other companies contacted
Loading the homepage contacts 13 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 polarcapitalfunds.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on polarcapitalfunds.com, including 16 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.