Website review, no card needed

veo.com logo

veo.com website review

Visit site (opens in a new tab)Reviewed 26 October 202639 issues · 85 checks

This review found 39 issues worth fixing on veo.com, 19 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
6.2 s3.3 sMay 9Oct 243.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.6 s
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.9 s
Jun 6, 20264.1 s
Jun 13, 20264.1 s
Jun 20, 20264.4 s
Jun 27, 20264.8 s
Jul 4, 20265.5 s
Jul 11, 20265.9 s
Jul 18, 20265.9 s
Jul 25, 20265.7 s
Aug 1, 20265.2 s
Aug 8, 20265.0 s
Aug 15, 20265.1 s
Aug 22, 20265.1 s
Aug 29, 20265.1 s
Sep 5, 20265.0 s
Sep 12, 20264.8 s
Sep 19, 20264.5 s
Sep 26, 20264.3 s
Oct 3, 20263.9 s
Oct 10, 20263.8 s
Oct 17, 20263.9 s
Oct 24, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
336 ms226 msMay 9Oct 24301 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026239 ms
May 16, 2026254 ms
May 23, 2026259 ms
May 30, 2026254 ms
Jun 6, 2026257 ms
Jun 13, 2026255 ms
Jun 20, 2026269 ms
Jun 27, 2026271 ms
Jul 4, 2026291 ms
Jul 11, 2026310 ms
Jul 18, 2026308 ms
Jul 25, 2026319 ms
Aug 1, 2026300 ms
Aug 8, 2026309 ms
Aug 15, 2026323 ms
Aug 22, 2026307 ms
Aug 29, 2026295 ms
Sep 5, 2026278 ms
Sep 12, 2026265 ms
Sep 19, 2026260 ms
Sep 26, 2026269 ms
Oct 3, 2026271 ms
Oct 10, 2026282 ms
Oct 17, 2026303 ms
Oct 24, 2026301 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 veo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. veo.com at 0.9 s0.9 s
  2. veo.com at 1.8 s1.8 s
  3. veo.com at 2.7 s2.7 s
  4. veo.com at 3.6 s3.6 s
  5. veo.com at 4.5 s4.5 s
  6. veo.com at 5.4 s5.4 s
  7. veo.com at 6.3 s6.3 s
  8. veo.com at 7.2 s7.2 s

Speed

15 to fix24
  • Reduce unused JavaScript

    1.5 s · 904 KiB

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

  • Render-blocking requests

    1.9 s

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

  • website-files.com adds 1.3 s

    1.3 s

    website-files.com costs a phone 1.3 s of main-thread work and 3.3 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.

  • Main-thread work: 16.0 s

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

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 559 KiB 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.

  • Mobile performance score: 24

    24/100

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

  • 6,450 HTML elements

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    300 ms · 2.1 MB

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

  • 20 long tasks on the main thread

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

  • Cookiebot adds 662 ms

    662 ms

    Cookiebot costs a phone 662 ms of main-thread work and 40 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

    450 ms · 84 KiB

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

  • ZenDesk adds 356 ms

    356 ms

    ZenDesk costs a phone 356 ms of main-thread work and 413 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.

  • Facebook adds 344 ms

    344 ms

    Facebook costs a phone 344 ms of main-thread work and 255 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

    263 KiB

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

  • Legacy JavaScript

    84 KiB

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

    12 ms

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

Core Web Vitals

11 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 LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 10.2 s

    10.2 s

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

  • Total Blocking Time: 4.7 s

    4.7 s

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

  • Time to Interactive: 25.5 s

    25.5 s

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

  • Speed Index: 14.6 s

    14.6 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Real-user INP: 316 ms

    316 ms

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

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

    +23%

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

  • 1 image without width and height

    1 image 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-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 506 ms

    506 ms

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

  • Cumulative Layout Shift: 0.092

    0.092

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

Images and page weight

2 to fix64
  • Page weight: 5.5 MB in 184 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 184 requests on a phone: images 2.6 MB (73), scripts 2.3 MB (55) and fonts 284 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6abf95bb225d9628843392ef_match report laptop hero-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 1.6 g of CO₂ per visit

    1.56 g

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

5 to fixGoogle 9794
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (7 elements)

    ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 240 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 4 H1 headlines

    There are 4 <h1> headlines (“Your entire match, already analysed”, “Record, analyse, and livestream every match” and “Book a call with a Veo expert”). One clear main headline is easier for people and search engines.

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

  • 241 internal links, 34 external

    The homepage links to 241 pages on veo.com and 34 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Capture, analyse, and share every moment with Veo Cam 3 – the AI-powered sports camera that records matches automatical…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Veo Sports Cameras | Record, Stream and Analyse”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

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

  • llms.txt published

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

Other pages

2 to fix83
  • 1 page points its canonical at the homepage

    https://www.veo.com/old-home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.veo.com/old-home all use the title “Veo Sports Cameras | Record, Stream and Analyse”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

    6 errors were logged to the browser console while the page loaded, for example “It seems like there are multiple Superform scripts added to your page. This might be causing some conflicts. Please rem…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • A 28-field form

    Your longest form asks for 28 fields (22 required). Every extra field lowers completion.

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

    The homepage carries about 606 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a call” and “Buy now”.

  • 50 calls to action

    The homepage has 50 calls to action, for example “Buy now”, “Book a call” and “Pricing”.

  • Social proof on the page

    Social proof on the homepage: 253 testimonial or review blocks, 124 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Segment and Amplitude.

  • Direct contact links

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

Privacy and tracking

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

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

  • 52 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 veo.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
Analytics
Google Tag Manager | Segment | Amplitude

Hiring

Hiring
19 open roles
Teams
Engineering (5), Platform (3), AI (2), All teams (2)
Job board
lever

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on veo.com, including 26 speed issues, 2 SEO issues 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