Website review, no card needed

advisorengine.com logo

advisorengine.com website review

Visit site (opens in a new tab)Reviewed 18 October 202637 issues · 84 checks

This review found 37 issues worth fixing on advisorengine.com, 13 of them high impact, across 84 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
5.5 s3.2 sApr 25Oct 104.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.9 s
May 2, 20263.9 s
May 9, 20263.6 s
May 16, 20263.5 s
May 23, 20263.6 s
May 30, 20264.2 s
Jun 6, 20265.3 s
Jun 13, 20265.0 s
Jun 20, 20264.6 s
Jun 27, 20264.3 s
Jul 4, 20264.1 s
Jul 11, 20264.3 s
Jul 18, 20264.2 s
Jul 25, 20264.3 s
Aug 1, 20264.1 s
Aug 8, 20264.1 s
Aug 15, 20264.4 s
Aug 22, 20264.8 s
Aug 29, 20264.8 s
Sep 5, 20264.8 s
Sep 12, 20264.5 s
Sep 19, 20264.3 s
Sep 26, 20264.3 s
Oct 3, 20264.2 s
Oct 10, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
134 ms76 msMay 2Oct 10110 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026109 ms
May 9, 202698 ms
May 16, 202683 ms
May 23, 202683 ms
May 30, 202683 ms
Jun 6, 202687 ms
Jun 13, 202688 ms
Jun 20, 2026100 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 2026109 ms
Jul 18, 202699 ms
Jul 25, 202694 ms
Aug 1, 202699 ms
Aug 8, 202696 ms
Aug 15, 2026100 ms
Aug 22, 2026106 ms
Aug 29, 2026119 ms
Sep 19, 2026127 ms
Sep 26, 2026121 ms
Oct 3, 2026118 ms
Oct 10, 2026110 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 advisorengine.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. advisorengine.com at 0.4 s0.4 s
  2. advisorengine.com at 0.8 s0.8 s
  3. advisorengine.com at 1.1 s1.1 s
  4. advisorengine.com at 1.5 s1.5 s
  5. advisorengine.com at 1.9 s1.9 s
  6. advisorengine.com at 2.3 s2.3 s
  7. advisorengine.com at 2.6 s2.6 s
  8. advisorengine.com at 3.0 s3.0 s

Speed

10 to fix52
  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    1.8 s · 786 KiB

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

  • Use efficient cache lifetimes

    1.3 s · 304 KiB

    55 files are served with short cache lifetimes, so returning visitors download them again (304 KiB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vidyard and Hubspot and others), adding 1.7 MB and 1.0 s of main-thread time.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 34). Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 650 ms

    650 ms

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

  • Legacy JavaScript

    450 ms · 35 KiB

    Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 27 KiB

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

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Vidyard adds 159 ms

    159 ms

    Vidyard costs a phone 159 ms of main-thread work and 548 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.

  • 7 long tasks on the main thread

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

  • Improve image delivery

    20 KiB

    1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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: 7 ms

    7 ms

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

Core Web Vitals

9 to fix50
  • 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: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 12.6 s

    12.6 s

    Your largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your complete wealth management platform”.

  • First Contentful Paint: 7.5 s

    7.5 s

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

  • Time to Interactive: 20.5 s

    20.5 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Total Blocking Time: 276 ms

    276 ms

    Scripts block taps and scrolling for 276 ms in total while the page loads. Good is under 200 ms.

  • 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) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 109 ms to 110 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-10, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Real-user TTFB: 712 ms

    712 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

2 to fix55
  • Page weight: 6.7 MB in 146 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 146 requests on a phone: images 4.7 MB (15), scripts 1.6 MB (50) and fonts 209 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    HP Infographic v2_2.gif weighs 1.8 MB. On a phone connection a single image that size takes seconds.

  • About 1.9 g of CO₂ per visit

    1.90 g

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

3 checks passed
  • 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

4 to fixGoogle 8993
  • ARIA attributes must conform to valid values (3 elements)

    ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical 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.

  • All page content should be contained by landmarks (31 elements)

    All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

5 to fixGoogle 8584
  • 2 H1 headlines

    There are 2 <h1> headlines (“Your complete wealth management platform” and “What our clients say”). One clear main headline is easier for people and search engines.

  • Meta description is long (193 characters)

    Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 60 internal links, 12 external

    The homepage links to 60 pages on advisorengine.com and 12 external pages.

5 checks passed
  • Title: 42 characters

    Your title is a healthy 42 characters: “Wealth Management Software | AdvisorEngine”.

  • Canonical URL set

    The canonical URL is https://www.advisorengine.com/.

  • Structured data in place

    Structured data found: Corporation, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.advisorengine.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.advisorengine.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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (619 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.advisorengine.com/wealth-management-technology/platform and https://www.advisorengine.com/wealth-management-technology/portfolio-management all use the title “AdvisorEngine | An end-to-end wealth management platform”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.advisorengine.com/action-magazine/articles has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.advisorengine.com/wealth-management-technology/platform and https://www.advisorengine.com/wealth-management-technology/portfolio-management use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 41 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 9293
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    15 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. 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.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 354 words of copy

    The homepage carries about 354 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: “REGISTER NOW >>” and “DEMO”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “REGISTER NOW >>”, “Contact Us” and “Schedule a Demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • 34 other companies contacted

    Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 advisorengine.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
HubSpot CMS
Analytics
Google Analytics | Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on advisorengine.com, including 19 speed issues, 5 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