Website review, no card needed

aerchain.io logo

aerchain.io website review

Visit site (opens in a new tab)Reviewed 25 October 202637 issues · 83 checks

This review found 37 issues worth fixing on aerchain.io, 13 of them high impact, across 83 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
3.9 s1.7 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.2 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.8 s
Jun 6, 20263.2 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.7 s
Jul 4, 20262.3 s
Jul 11, 20262.5 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20263.2 s
Aug 8, 20263.4 s
Aug 15, 20263.5 s
Aug 22, 20263.4 s
Aug 29, 20263.1 s
Sep 5, 20262.8 s
Sep 12, 20263.3 s
Sep 19, 20263.5 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.2 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
351 ms134 msMay 2Oct 17180 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026171 ms
May 9, 2026159 ms
May 16, 2026159 ms
May 23, 2026173 ms
May 30, 2026181 ms
Jun 6, 2026191 ms
Jun 13, 2026184 ms
Jun 20, 2026177 ms
Jun 27, 2026174 ms
Jul 4, 2026171 ms
Jul 11, 2026169 ms
Jul 18, 2026164 ms
Jul 25, 2026167 ms
Aug 1, 2026192 ms
Aug 8, 2026205 ms
Aug 15, 2026230 ms
Aug 22, 2026216 ms
Aug 29, 2026195 ms
Sep 5, 2026192 ms
Sep 12, 2026266 ms
Sep 19, 2026290 ms
Sep 26, 2026302 ms
Oct 3, 2026326 ms
Oct 10, 2026248 ms
Oct 17, 2026180 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 aerchain.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aerchain.io at 0.7 s0.7 s
  2. aerchain.io at 1.4 s1.4 s
  3. aerchain.io at 2.1 s2.1 s
  4. aerchain.io at 2.8 s2.8 s
  5. aerchain.io at 3.5 s3.5 s
  6. aerchain.io at 4.2 s4.2 s
  7. aerchain.io at 5.0 s5.0 s
  8. aerchain.io at 5.7 s5.7 s

Speed

9 to fix37
  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 4.1 s

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

  • Use efficient cache lifetimes

    600 ms · 5.8 MB

    51 files are served with short cache lifetimes, so returning visitors download them again (5.8 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, website-files.com and lgrckt-in.com and others), adding 9.6 MB and 1.0 s of main-thread time.

  • website-files.com adds 164 ms

    164 ms

    website-files.com costs a phone 164 ms of main-thread work and 8.5 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.

  • Reduce unused JavaScript

    150 ms · 400 KiB

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

  • Google Tag Manager adds 466 ms

    466 ms

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

  • 1,811 HTML elements

    The page has 1,811 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 13 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 46 KiB

    About 46 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.

  • Improve image delivery

    146 KiB

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

  • Legacy JavaScript

    13 KiB

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

  • Phones get a much slower page than desktops

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

  • Minify CSS

    9 KiB

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

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

    6 ms

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

Core Web Vitals

13 to fix33
  • 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: 3.5 s

    3.5 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • Time to Interactive: 16.7 s

    16.7 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Cumulative Layout Shift: 0.304

    0.304

    The layout shifts by 0.304 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user INP: 271 ms

    271 ms

    Real visitors wait 271 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • Total Blocking Time: 499 ms

    499 ms

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

  • 39 images without width and height

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

  • Speed Index: 5.0 s

    5.0 s

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

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

    +16%

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

1 checks passed
  • Real-user CLS: 0.06

    0.06

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

Images and page weight

3 to fix47
  • Page weight: 9.9 MB in 170 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 170 requests on a phone: media 5.3 MB (18), images 3.0 MB (57) and scripts 1.3 MB (45). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    678eb42db0d1316f452ed648_Guided buying.svg weighs 2.3 MB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    678e4ee8f96cdf2ad3e4022b_Group%201597884279-p-500.png 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).

  • About 2.8 g of CO₂ per visit

    2.79 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.79 g of CO₂e: 335.3 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

2 to fixGoogle 9297
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 183 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

3 to fixGoogle 9291
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • 6 links with vague text

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

  • 69 internal links, 4 external

    The homepage links to 69 pages on aerchain.io and 4 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Revolutionize procurement with AI-driven automation. Aerchain simplifies sourcing, negotiations, and compliance, ensuri…”.

  • One H1 headline

    Your main headline reads: “Automate your Sourcing with Specialized AI Agents”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Aerchain: AI-Powered Procurement & Autonomous Sourcing”.

  • Canonical URL set

    The canonical URL is https://aerchain.io/.

  • 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://aerchain.io/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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://aerchain.io/llms.txt (5 KiB, 9 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 8 pages without a meta description

    https://aerchain.io/on-the-way, https://aerchain.io/soon, https://aerchain.io/multi-agent-framework, https://aerchain.io/knowledge-hub, https://aerchain.io/integrations-hub and https://aerchain.io/omnichannel-hub and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://aerchain.io/aera-ai, https://aerchain.io/products/intake-agent, https://aerchain.io/products/vendor-onboarding-agent, https://aerchain.io/products/sourcing-agent, https://aerchain.io/products/evaluation-agent and https://aerchain.io/products/negotiation-agent and 1 other 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 24 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.

  • 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 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

    The homepage carries about 817 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Demo”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Pricing Calculator”, “Book Demo” and “Learn More”.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 18 cookies set on arrival

    18

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

  • 41 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Heap

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 aerchain.io, including 22 speed issues, 3 SEO issues and 2 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