Website review, no card needed

velloxgroup.com logo

velloxgroup.com website review

Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 70 checks

This review found 33 issues worth fixing on velloxgroup.com, 17 of them high impact, across 70 checks. The most urgent: use efficient cache lifetimes. 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
4.7 s2.7 sMay 2Oct 173.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.5 s
May 9, 20263.5 s
May 16, 20263.2 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.2 s
Jul 11, 20263.4 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.8 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.6 s
Sep 5, 20263.2 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
139 ms80 msMay 2Oct 17106 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026102 ms
May 9, 202687 ms
May 16, 202687 ms
May 23, 202687 ms
May 30, 202691 ms
Jun 6, 202697 ms
Jun 13, 2026101 ms
Jun 20, 2026104 ms
Jun 27, 2026104 ms
Jul 4, 2026106 ms
Jul 11, 202697 ms
Jul 18, 202696 ms
Jul 25, 202695 ms
Aug 1, 202697 ms
Aug 8, 2026127 ms
Aug 15, 2026123 ms
Aug 22, 2026132 ms
Aug 29, 2026129 ms
Sep 5, 2026114 ms
Sep 12, 2026128 ms
Sep 19, 2026117 ms
Sep 26, 2026120 ms
Oct 3, 2026115 ms
Oct 10, 2026110 ms
Oct 17, 2026106 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 velloxgroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. velloxgroup.com at 0.5 s0.5 s
  2. velloxgroup.com at 1.1 s1.1 s
  3. velloxgroup.com at 1.6 s1.6 s
  4. velloxgroup.com at 2.1 s2.1 s
  5. velloxgroup.com at 2.6 s2.6 s
  6. velloxgroup.com at 3.2 s3.2 s
  7. velloxgroup.com at 3.7 s3.7 s
  8. velloxgroup.com at 4.2 s4.2 s

Speed

7 to fix40
  • Use efficient cache lifetimes

    2.0 s · 12.5 MB

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

  • Reduce unused JavaScript

    3.6 s · 687 KiB

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

  • Render-blocking requests

    1.7 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.7 s.

  • Mobile performance score: 40

    40/100

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

  • Main-thread work: 4.9 s

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

  • 13 long tasks on the main thread

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

  • Google Tag Manager adds 327 ms

    327 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and usemessages.com and others), adding 660 KiB and 476 ms of main-thread time.

  • Improve image delivery

    80 KiB

    6 images could be 80 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.

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

    20 ms

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

Core Web Vitals

9 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 TTFB: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 40.3 s

    40.3 s

    Your largest element takes 40.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Unifying Aviation Ops, Dispatch, Maintenance, Safety & Flee…”.

  • Speed Index: 20.3 s

    20.3 s

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

  • Time to Interactive: 44.3 s

    44.3 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

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

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

    +14%

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

4 checks passed
  • Real-user INP: 106 ms

    106 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Largest content (LCP) got 25% faster for real visitors

    -25%

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

  • Cumulative Layout Shift: 0.063

    0.063

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

Images and page weight

5 to fix18
  • Page weight: 21.8 MB in 101 requests

    21.8 MB

    Your homepage downloads 21.8 MB in 101 requests on a phone: images 20.0 MB (39), scripts 1.6 MB (24) and fonts 139 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 17.8 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    519 KiB

    2 images are downloaded at several times the size a phone draws them, for example CTA_2_d8d234b15e.png at 1,440 px wide, shown at 390 px. Resized copies would save about 519 KiB.

  • 11 images below the first screen load straight away

    11 images further down the page (19.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (1.0 MB) are 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.

  • About 6.2 g of CO₂ per visit

    6.17 g

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

Accessibility

2 to fixGoogle 9697
  • 2 text elements with low contrast

    2 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (5 elements).

2 checks passed
  • Every image has alt text

    All 29 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9284
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Trusted solutions for safe, efficient and compliant operations | Vellox Group”.

  • Meta description is long (192 characters)

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

  • Only 2 internal links

    The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 5 links with vague text

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

6 checks passed
  • One H1 headline

    Your main headline reads: “Unifying Aviation Ops, Dispatch, Maintenance, Safety & Fleet Tracking in One System”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness, WebPage and WebSite.

  • 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.velloxgroup.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

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

    The homepage carries about 431 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: “Schedule a Demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • 27 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Gatsby
Analytics
Google Analytics | Google Tag Manager
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on velloxgroup.com, including 16 speed issues, 4 SEO issues and 4 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