Website review, no card needed

velaris.io logo

velaris.io website review

Visit site (opens in a new tab)Reviewed 21 October 202628 issues · 76 checks

This review found 28 issues worth fixing on velaris.io, 14 of them high impact, across 76 checks. The most urgent: website-files.com adds 1.8 s. 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
2.2 s1.4 sMay 2Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.9 s
Aug 1, 20262.1 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20261.7 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.8 s
Sep 26, 20262.0 s
Oct 3, 20261.6 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
222 ms105 msMay 2Oct 17127 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026129 ms
May 9, 2026130 ms
May 16, 2026129 ms
May 23, 2026130 ms
May 30, 2026130 ms
Jun 6, 2026127 ms
Jun 13, 2026129 ms
Jun 20, 2026118 ms
Jun 27, 2026118 ms
Jul 4, 2026123 ms
Jul 11, 2026120 ms
Jul 18, 2026129 ms
Jul 25, 2026166 ms
Aug 1, 2026177 ms
Aug 8, 2026176 ms
Aug 15, 2026162 ms
Aug 22, 2026162 ms
Aug 29, 2026147 ms
Sep 5, 2026134 ms
Sep 12, 2026208 ms
Sep 19, 2026204 ms
Sep 26, 2026206 ms
Oct 3, 2026179 ms
Oct 10, 2026131 ms
Oct 17, 2026127 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 velaris.io (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. velaris.io at 0.4 s0.4 s
  2. velaris.io at 0.8 s0.8 s
  3. velaris.io at 1.1 s1.1 s
  4. velaris.io at 1.5 s1.5 s
  5. velaris.io at 1.9 s1.9 s
  6. velaris.io at 2.3 s2.3 s
  7. velaris.io at 2.6 s2.6 s
  8. velaris.io at 3.0 s3.0 s

Speed

11 to fix36
  • website-files.com adds 1.8 s

    1.8 s

    website-files.com costs a phone 1.8 s of main-thread work and 38.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.9 s

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

  • Minify JavaScript

    1.5 s · 357 KiB

    357 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 36

    36/100

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

  • 7,585 HTML elements

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

  • Main-thread work: 5.4 s

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

  • Use efficient cache lifetimes

    150 ms · 33.0 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (website-files.com, hsappstatic.net and Hubspot and others), adding 38.4 MB and 2.0 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 150 KiB

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

  • Reduce unused CSS

    450 ms · 87 KiB

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

  • 10 long tasks on the main thread

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

  • Improve image delivery

    192 KiB

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

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 16.8 s

    16.8 s

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

  • Time to Interactive: 30.9 s

    30.9 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user TTFB: 805 ms

    805 ms

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • 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 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

1 to fix70
  • Page weight: 38.5 MB in 106 requests

    38.5 MB

    Your homepage downloads 38.5 MB in 106 requests on a phone: media 32.7 MB (18), fonts 2.0 MB (6) and other files 1.9 MB (19). Under 2 MB keeps phones on slow connections fast.

  • About 10.9 g of CO₂ per visit

    10.92 g

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

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

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

2 checks passed
  • Every image has alt text

    All 88 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

1 to fixGoogle 10095
  • Meta description is long (183 characters)

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

  • 69 internal links, 1 external

    The homepage links to 69 pages on velaris.io and 1 external page.

7 checks passed
  • One H1 headline

    Your main headline reads: “AI agents that run Customer Success, built on a brain that never forgets.”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Velaris: The AI Customer Success Platform”.

  • Canonical URL set

    The canonical URL is https://www.velaris.io/.

  • Structured data in place

    Structured data found: WebPage.

  • 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.velaris.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,306 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7385
  • 2 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 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 665 words of copy

    The homepage carries about 665 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a demo”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact UsGet in touch”, “Pricing” and “Request a demo”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and HubSpot.

Privacy and tracking

  • 9 cookies set on arrival

    9

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

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts 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 velaris.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
Google Analytics | Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on velaris.io, including 19 speed issues, 1 SEO issue 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