Website review, no card needed

aicapital.ai logo

aicapital.ai website review

Visit site (opens in a new tab)Reviewed 18 October 202632 issues · 70 checks

This review found 32 issues worth fixing on aicapital.ai, 14 of them high impact, across 70 checks. The most urgent: improve image delivery. 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

Full-page screenshot of aicapital.ai (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aicapital.ai at 0.5 s0.5 s
  2. aicapital.ai at 1.0 s1.0 s
  3. aicapital.ai at 1.6 s1.6 s
  4. aicapital.ai at 2.1 s2.1 s
  5. aicapital.ai at 2.6 s2.6 s
  6. aicapital.ai at 3.1 s3.1 s
  7. aicapital.ai at 3.7 s3.7 s
  8. aicapital.ai at 4.2 s4.2 s

Speed

4 to fix71
  • Improve image delivery

    3.4 s · 2.1 MB

    11 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.

  • Font display

    1.1 s

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

  • Mobile performance score: 71

    71/100

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

  • Render-blocking requests

    400 ms

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

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

  • 1 third-party service on the page

    1 third-party service load with your homepage (cdnfonts.com), adding 253 KiB and 0 ms of main-thread time.

  • Reduce unused JavaScript

    23 KiB

    About 23 KiB of JavaScript is downloaded but never used on this page.

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 71. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 52 ms

    52 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 15.0 s

    15.0 s

    Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AIC/We Empower The AI Revolution”.

  • Time to Interactive: 15.7 s

    15.7 s

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

  • 34 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Not enough real-visitor data yet

    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.

3 checks passed
  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 114 ms

    114 ms

    Scripts block the page for only 114 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

5 to fix28
  • Page weight: 7.7 MB in 54 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 54 requests on a phone: media 3.8 MB (2), images 3.5 MB (29) and fonts 252 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (573 KiB) is 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 (611 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    94 KiB

    1 image is downloaded at several times the size a phone draws it, for example our-focus.png at 1,280 px wide, shown at 390 px. Resized copies would save about 94 KiB.

  • About 2.2 g of CO₂ per visit

    2.18 g

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

Accessibility

4 to fixGoogle 9092
  • <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.

  • 10 images without alt text

    10 images have no alt text, which hurts accessibility and image search.

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

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

  • No page language

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

1 checks passed
  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 3 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 9258
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at aicapital.ai/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 14 internal links, 5 external

    The homepage links to 14 pages on aicapital.ai and 5 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://aicapital.ai/.

  • Structured data in place

    Structured data found: Organization, WebPage and Website.

  • XML sitemap found

    Your XML sitemap is reachable at https://aicapital.ai/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://aicapital.ai/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading 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 (300 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix71
  • 4 pages without a title

    https://aicapital.ai/our-team, https://aicapital.ai/our-companies, https://aicapital.ai/our-musings and https://aicapital.ai/contact-us have no <title>, so Google invents the link text in results.

  • 4 pages without a meta description

    https://aicapital.ai/our-team, https://aicapital.ai/our-companies, https://aicapital.ai/our-musings and https://aicapital.ai/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://aicapital.ai/our-team, https://aicapital.ai/our-companies, https://aicapital.ai/our-musings and https://aicapital.ai/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://aicapital.ai/contact-us has 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.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9692
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “X-Frame-Options may only be set via an HTTP header sent along with a document. It may not be set inside <meta>.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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.

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

  • No analytics detected

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

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

    The homepage carries about 295 words of visible text.

1 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Contact us”.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 aicapital.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on aicapital.ai, including 8 speed issues, 5 SEO issues and 6 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