Website review, no card needed

vikingglobal.com logo

vikingglobal.com website review

Visit site (opens in a new tab)Reviewed 3 November 202628 issues · 74 checks

This review found 28 issues worth fixing on vikingglobal.com, 11 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
2.6 s1.3 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.4 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
96 ms73 msMay 16Oct 3176 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202678 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202684 ms
Jun 20, 202684 ms
Jun 27, 202690 ms
Jul 4, 202693 ms
Jul 11, 202692 ms
Jul 18, 202692 ms
Jul 25, 202690 ms
Aug 1, 202686 ms
Aug 8, 202683 ms
Aug 15, 202684 ms
Aug 22, 202682 ms
Aug 29, 202685 ms
Sep 5, 202683 ms
Sep 12, 202677 ms
Sep 19, 202679 ms
Sep 26, 202681 ms
Oct 3, 202685 ms
Oct 10, 202687 ms
Oct 17, 202685 ms
Oct 24, 202679 ms
Oct 31, 202676 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 vikingglobal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vikingglobal.com at 0.7 s0.7 s
  2. vikingglobal.com at 1.3 s1.3 s
  3. vikingglobal.com at 2.0 s2.0 s
  4. vikingglobal.com at 2.6 s2.6 s
  5. vikingglobal.com at 3.3 s3.3 s
  6. vikingglobal.com at 3.9 s3.9 s
  7. vikingglobal.com at 4.6 s4.6 s
  8. vikingglobal.com at 5.2 s5.2 s

Speed

5 to fix60
  • Render-blocking requests

    2.3 s

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

  • Reduce unused JavaScript

    1.5 s · 284 KiB

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

  • Improve image delivery

    1.3 s · 249 KiB

    2 images could be 249 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 222 ms

    222 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Highcharts and Cloudflare CDN and others), adding 518 KiB and 307 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 48 KiB

    About 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 466 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

7 to fix100
  • 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: 9.6 s

    9.6 s

    Your largest element takes 9.6 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 and similar technologies to enhance …”. Most of its time is element render delay (5.2 s).

  • Time to Interactive: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user TTFB: 923 ms

    923 ms

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

  • 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) held steady for real visitors

    -1%

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

6 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Total Blocking Time: 145 ms

    145 ms

    Scripts block the page for only 145 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix63
  • Page weight: 12.1 MB in 59 requests

    12.1 MB

    Your homepage downloads 12.1 MB in 59 requests on a phone: media 10.7 MB (2), scripts 672 KiB (21) and images 501 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (330 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.4 g of CO₂ per visit

    3.44 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10095
  • All page content should be contained by landmarks (8 elements)

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

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is short (13 characters)

    Your title is only 13 characters: “Viking Global”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (58 characters)

    Your meta description is only 58 characters: “Inspired by opportunities. Guided by intellectual honesty.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • 35 internal links, 2 external

    The homepage links to 35 pages on vikingglobal.com and 2 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Inspired by new opportunities. Guided by intellectual honesty.”.

  • Canonical URL set

    The canonical URL is https://vikingglobal.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • 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://vikingglobal.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://vikingglobal.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.

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 (648 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 4 pages share a meta description

    https://vikingglobal.com/about-us, https://vikingglobal.com/public-equity, https://vikingglobal.com/private-equity and https://vikingglobal.com/credit-and-structured-capital use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://vikingglobal.com/europes-engagement-policy, whose canonical is https://vikingglobal.com/european-engagement-policy. 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 16 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.

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

  • 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

1 to fixGoogle 10092
  • 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”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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 328 words of copy

    The homepage carries about 328 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Learn more about us” and “Learn more about our investments”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 1 cookie set on arrival

    1

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 vikingglobal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

Hiring

Hiring
5 open roles
Teams
Investment - Private (1), Investment - Public (1), Investment - Research (1)
Job board
greenhouse

Company

Founded
1999
Headquarters
Greenwich

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on vikingglobal.com, including 12 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

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