Website review, no card needed
hgcapital.com website review
Visit site (opens in a new tab)Reviewed 27 October 202639 issues · 84 checks
This review found 39 issues worth fixing on hgcapital.com, 18 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 124 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 120 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 93 ms |
| Aug 8, 2026 | 93 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 121 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 121 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
Speed
Reduce unused JavaScript
13.9 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 13.9 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 268 KiB23 files are served with short cache lifetimes, so returning visitors download them again (268 KiB).
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (Vimeo, Google Tag Manager and cookiehub.eu and others), adding 33.3 MB and 735 ms of main-thread time.
Vimeo adds 606 ms
606 msVimeo costs a phone 606 ms of main-thread work and 29.8 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.
Improve image delivery
150 ms · 3.0 MB7 images could be 3.0 MB 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.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 71). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
ctfassets.net adds 0 ms
0 msctfassets.net costs a phone 0 ms of main-thread work and 3.3 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 245 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
1 checks passed
Server response: 25 ms
25 msYour server sent the HTML in 25 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.
Real-user CLS: 0.69
0.69For real visitors the layout shifts by 0.69 (75th percentile). Good is under 0.1.
First Contentful Paint: 15.1 s
15.1 sThe first text or image appears after 15.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 30.7 s
30.7 sYour largest element takes 30.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.2 s
17.2 sVisually, the page fills in at 17.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 35.0 s
35.0 sThe page becomes fully interactive after 35.0 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 124 ms to 121 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-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 177 ms
177 msReal visitors wait 177 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 491 ms
491 msReal visitors wait 491 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 127 ms
127 msScripts block the page for only 127 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 37.1 MB in 242 requests
37.1 MBYour homepage downloads 37.1 MB in 242 requests on a phone: other files 27.5 MB (140), images 3.6 MB (23) and scripts 3.0 MB (60). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
1.4 MB2 images are downloaded at several times the size a phone draws them, for example Life_thumb.PNG at 1,886 px wide, shown at 340 px. Resized copies would save about 1.4 MB.
3 images in older formats
3 images (2.5 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.
2 images below the first screen load straight away
2 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 10.5 g of CO₂ per visit
10.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.50 g of CO₂e: 1260.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Form elements must have labels (2 elements)
Form elements must have labels: 2 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Certain ARIA roles must be contained by particular parents (1 element)
Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.
Elements must only use permitted ARIA attributes (15 elements)
Elements must only use permitted ARIA attributes: 15 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
Title is short (24 characters)
Your title is only 24 characters: “Navigate the future | Hg”. 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
41 internal links, 3 external
The homepage links to 41 pages on hgcapital.com and 3 external pages.
6 checks passed
Meta description: 89 characters
Your meta description is 89 characters: “We are an AI leader in private equity, building businesses that redefine how people work.”.
One H1 headline
Your main headline reads: “Hg. Navigate the future”.
Canonical URL set
The canonical URL is https://hgcapital.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://hgcapital.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (416 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hgcapital.com/llms.txt (2 KiB, 6 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share a meta description
https://hgcapital.com/approach/responsible-investing, https://hgcapital.com/life-at-hg/diversity-and-inclusion, https://hgcapital.com/investors and https://hgcapital.com/monthly-update use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://hgcapital.com/approach/driving-ai-transformation, https://hgcapital.com/approach/responsible-investing, https://hgcapital.com/life-at-hg, https://hgcapital.com/life-at-hg/diversity-and-inclusion, https://hgcapital.com/investors and https://hgcapital.com/insights/3e-secures-majority-investment-from-hg and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://hgcapital.com/team and https://hgcapital.com/monthly-update have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
31 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: “60+ companies”. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 371 words of copy
The homepage carries about 371 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: “SUBSCRIBE T0 THE HG MONTHLY UPDATE” and “Learn more”.
3 calls to action
The homepage has 3 calls to action, for example “Subscribe T0 THE HG MONTHLY UPDATE”, “Subscribe to Hg's Monthly Updates” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and LinkedIn Insight (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, 2 of them by other companies (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.
14 other companies contacted
Loading the homepage contacts 14 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 hgcapital.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
- Next.js
- Hosting
- Netlify
Company
- Founded
- 2000
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on hgcapital.com, including 15 speed issues, 3 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.