Website review, no card needed

alumio.com logo

alumio.com website review

Visit site (opens in a new tab)Reviewed 20 October 202635 issues · 88 checks

This review found 35 issues worth fixing on alumio.com, 14 of them high impact, across 88 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.1 s3.2 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.7 s
May 16, 20264.2 s
May 23, 20264.8 s
May 30, 20264.9 s
Jun 6, 20264.6 s
Jun 13, 20264.6 s
Jun 20, 20264.0 s
Jun 27, 20263.9 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.2 s
Jul 25, 20264.2 s
Aug 1, 20264.0 s
Aug 8, 20263.6 s
Aug 15, 20263.7 s
Aug 22, 20263.8 s
Aug 29, 20263.9 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20263.9 s
Sep 26, 20263.6 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
342 ms67 msMay 2Oct 1799 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026256 ms
May 9, 2026270 ms
May 16, 2026300 ms
May 23, 2026300 ms
May 30, 2026310 ms
Jun 6, 2026255 ms
Jun 13, 2026210 ms
Jun 20, 2026193 ms
Jun 27, 2026171 ms
Jul 4, 2026159 ms
Jul 11, 2026158 ms
Jul 18, 2026169 ms
Jul 25, 2026173 ms
Aug 1, 2026171 ms
Aug 8, 2026181 ms
Aug 15, 2026166 ms
Aug 22, 2026163 ms
Aug 29, 2026158 ms
Sep 5, 2026160 ms
Sep 12, 2026162 ms
Sep 19, 2026161 ms
Sep 26, 2026152 ms
Oct 3, 2026131 ms
Oct 10, 2026108 ms
Oct 17, 202699 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 alumio.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alumio.com at 0.4 s0.4 s
  2. alumio.com at 0.8 s0.8 s
  3. alumio.com at 1.1 s1.1 s
  4. alumio.com at 1.5 s1.5 s
  5. alumio.com at 1.9 s1.9 s
  6. alumio.com at 2.3 s2.3 s
  7. alumio.com at 2.7 s2.7 s
  8. alumio.com at 3.1 s3.1 s

Speed

13 to fix37
  • Render-blocking requests

    6.2 s

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

  • Reduce unused JavaScript

    4.1 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

  • Use efficient cache lifetimes

    2.9 s · 627 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 4.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, Google Tag Manager and intellimize.co and others), adding 2.3 MB and 1.3 s of main-thread time.

  • website-files.com adds 587 ms

    587 ms

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

  • Reduce unused CSS

    600 ms · 65 KiB

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

  • 19 long tasks on the main thread

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

  • Google Tag Manager adds 289 ms

    289 ms

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

  • 2,482 HTML elements

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

  • Hubspot adds 91 ms

    91 ms

    Hubspot costs a phone 91 ms of main-thread work and 308 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.

  • Vimeo adds 54 ms

    54 ms

    Vimeo costs a phone 54 ms of main-thread work and 537 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

    15 KiB

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    10 KiB

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

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

    5 ms

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

Core Web Vitals

10 to fix67
  • 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.6 s

    3.6 s

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

  • First Contentful Paint: 12.6 s

    12.6 s

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

  • Largest Contentful Paint: 17.5 s

    17.5 s

    Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Automate, govern and scale data integrations via a central …”.

  • Time to Interactive: 21.9 s

    21.9 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Total Blocking Time: 732 ms

    732 ms

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

  • 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 TTFB: 1.6 s

    1.6 s

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

  • 5 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

4 checks passed
  • Real-user INP: 99 ms

    99 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

    -61%

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 120 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 120 requests on a phone: scripts 2.6 MB (48), fonts 356 KiB (4) and images 72 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.91 g

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

2 to fixGoogle 9797
  • 5 text elements with low contrast

    5 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 (29 elements)

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

2 checks passed
  • Every image has alt text

    All 156 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 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 9290
  • 4 H1 headlines

    There are 4 <h1> headlines (“A smarter futurestarts with smarter integrations”, “Scalable integration backbone for business critic…” and “Automate, govern and scale data integrations via …”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 139 internal links, 8 external

    The homepage links to 139 pages on alumio.com and 8 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “A cloud-native iPaaS to integrate data across ERP, e-commerce, PIM, AI, and core systems, with complete visibility, gov…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Alumio | iPaaS for business-critical integrations”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, SoftwareApplication, VideoObject, WebPage and WebSite.

  • 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://alumio-automations.alumio.com/api/v1/http-proxy/alumio-sitemap-list.

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: 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 (988 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without an H1

    https://www.alumio.com/feature-roadmap 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 71 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

3 to fixGoogle 5488
  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “[marquee] No marquee instances found on the page when initializing Marquee component [object Object]”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 585 words of visible text.

5 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “See pricing”, “Learn more” and “EDI and B2B order integration”.

  • Social proof on the page

    Social proof on the homepage: 59 testimonial or review blocks, 18 customer or partner logos, a star rating and 13 trust badges.

  • Analytics in place

    Analytics detected: HubSpot, LinkedIn Insight and Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call 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.

  • 15 cookies set on arrival

    15

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

  • 47 other companies contacted

    Loading the homepage contacts 47 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 alumio.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
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on alumio.com, including 23 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