northatlanticcapital.com website review

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

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

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

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

5 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 1.9 MB and 1.4 s of main-thread time.

YouTube costs a phone 739 ms of main-thread work and 1.1 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.

Google CDN costs a phone 634 ms of main-thread work and 736 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.

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

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

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

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “North Atlantic Capital Logo”.

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

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

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

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

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.

Your homepage downloads 3.2 MB in 112 requests on a phone: scripts 2.0 MB (81), images 521 KiB (8) and other files 357 KiB (10). Under 2 MB keeps phones on slow connections fast.

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

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

30 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 72 characters, so Google will cut it off around 60: “Portland, Maine Growth Capital, Structured Debt | North Atlantic Capital”.

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

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

The homepage links to 28 pages on northatlanticcapital.com and 5 external pages.

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.

There is no https://www.northatlanticcapital.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.

https://www.northatlanticcapital.com/team/david-coit, https://www.northatlanticcapital.com/team/michael-nitka-stifel and https://www.northatlanticcapital.com/team/victor-nesi all use the title “Team: David Coit, Managing Director | North Atlantic Capital”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.northatlanticcapital.com/history, https://www.northatlanticcapital.com/portfolio, https://www.northatlanticcapital.com/category/company-news and https://www.northatlanticcapital.com/category/portfolio-news have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.northatlanticcapital.com/team/david-coit, https://www.northatlanticcapital.com/team/michael-nitka-stifel and https://www.northatlanticcapital.com/team/victor-nesi use the same meta description. A description written for each page earns more clicks.

https://www.northatlanticcapital.com/team, https://www.northatlanticcapital.com/team/david-coit, https://www.northatlanticcapital.com/team/mark-morrissette, https://www.northatlanticcapital.com/team/michael-nitka-stifel, https://www.northatlanticcapital.com/team/victor-nesi and https://www.northatlanticcapital.com/team/jason-gorey-2 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 192 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

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.

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