Website review, no card needed

harborcapital.com logo

harborcapital.com website review

Visit site (opens in a new tab)Reviewed 31 October 202630 issues · 84 checks

This review found 30 issues worth fixing on harborcapital.com, 9 of them high impact, across 84 checks. The most urgent: mobile performance score: 47. 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
9.7 s964 msMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20268.7 s
May 16, 20268.3 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.3 s
Jun 27, 20263.5 s
Jul 4, 20263.8 s
Jul 11, 20264.1 s
Jul 18, 20264.4 s
Jul 25, 20264.5 s
Aug 1, 20264.6 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Aug 22, 20264.3 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20263.5 s
Sep 19, 20263.1 s
Sep 26, 20262.7 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
231 ms129 msMay 9Oct 24141 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026219 ms
May 16, 2026180 ms
May 23, 2026153 ms
May 30, 2026168 ms
Jun 6, 2026185 ms
Jun 13, 2026180 ms
Jun 20, 2026184 ms
Jun 27, 2026187 ms
Jul 4, 2026177 ms
Jul 11, 2026188 ms
Jul 18, 2026182 ms
Jul 25, 2026171 ms
Aug 1, 2026182 ms
Aug 8, 2026181 ms
Aug 15, 2026183 ms
Aug 22, 2026182 ms
Aug 29, 2026155 ms
Sep 5, 2026146 ms
Sep 12, 2026143 ms
Sep 19, 2026154 ms
Sep 26, 2026167 ms
Oct 3, 2026169 ms
Oct 10, 2026152 ms
Oct 17, 2026145 ms
Oct 24, 2026141 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 harborcapital.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. harborcapital.com at 0.4 s0.4 s
  2. harborcapital.com at 0.8 s0.8 s
  3. harborcapital.com at 1.2 s1.2 s
  4. harborcapital.com at 1.6 s1.6 s
  5. harborcapital.com at 2.1 s2.1 s
  6. harborcapital.com at 2.5 s2.5 s
  7. harborcapital.com at 2.9 s2.9 s
  8. harborcapital.com at 3.3 s3.3 s

Speed

8 to fix47
  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    750 ms · 986 KiB

    About 986 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Wistia and TikTok and others), adding 1.5 MB and 843 ms of main-thread time.

  • Reduce unused CSS

    440 ms · 85 KiB

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

  • Google Tag Manager adds 419 ms

    419 ms

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

  • Render-blocking requests

    400 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 400 ms.

  • Main-thread work: 3.3 s

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

  • Wistia adds 229 ms

    229 ms

    Wistia costs a phone 229 ms of main-thread work and 499 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.

  • Improve image delivery

    177 KiB

    8 images could be 177 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    169 KiB

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    32 KiB

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

  • Duplicated JavaScript

    20 KiB

    20 KiB JavaScript is shipped twice across bundles.

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

    56 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 22.6 s

    22.6 s

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

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For 40 years, our goal has been to help advisors invest bet…”.

  • Total Blocking Time: 459 ms

    459 ms

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Tap response (INP) got 28% faster for real visitors

    -28%

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

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

    -77%

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

3 to fix60
  • Page weight: 4.4 MB in 180 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 180 requests on a phone: scripts 2.5 MB (74), other files 1,000 KiB (61) and images 391 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Article_-_AI_Winners_and_Losers.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    56 KiB

    1 image is downloaded at several times the size a phone draws it, for example icon-infographic-calendar.66217cf2.svg at 1,024 px wide, shown at 12 px. Resized copies would save about 56 KiB.

  • 2 images in older formats

    2 images (112 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.

  • 1 image below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.24 g

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

Accessibility

6 to fixGoogle 9492
  • 22 text elements with low contrast

    22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is short (28 characters)

    Your title is only 28 characters: “Active ETFs | Harbor Capital”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 links with vague text

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

  • 76 internal links, 4 external

    The homepage links to 76 pages on harborcapital.com and 4 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “A 50+ year history of selecting and investing in active ETFs and mutual funds with an emphasis on competitive pricing a…”.

  • One H1 headline

    Your main headline reads: “Active Management - Built for Changing Markets”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, WebPage 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.harborcapital.com/sitemap-index.xml.

AI search readiness

100
4 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 description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.harborcapital.com/llms.txt (30 KiB, 233 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.harborcapital.com/current has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 51 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 to fixGoogle 9687
  • 9 small tap targets

    9 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 883 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More” and “Close contact form”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Learn More”, “Request a Call” and “Close contact form”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 10 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 5 mores (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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 43 other companies contacted

    Loading the homepage contacts 43 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 harborcapital.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
Gatsby
Analytics
Google Tag Manager
Hosting
Netlify

Company

Employees
241

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on harborcapital.com, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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