Website review, no card needed
veed.io website review
Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 87 checks
This review found 34 issues worth fixing on veed.io, 13 of them high impact, across 87 checks. The most urgent: page weight: 41.3 MB in 249 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.0 s |
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 6.3 s |
| May 30, 2026 | 6.7 s |
| Jun 6, 2026 | 6.8 s |
| Jun 13, 2026 | 6.9 s |
| Jun 20, 2026 | 7.0 s |
| Jun 27, 2026 | 7.0 s |
| Jul 4, 2026 | 6.7 s |
| Jul 11, 2026 | 6.4 s |
| Jul 18, 2026 | 6.1 s |
| Jul 25, 2026 | 5.9 s |
| Aug 1, 2026 | 5.8 s |
| Aug 8, 2026 | 5.8 s |
| Aug 15, 2026 | 5.5 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.3 s |
| Sep 5, 2026 | 5.3 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 424 ms |
| May 16, 2026 | 429 ms |
| May 23, 2026 | 454 ms |
| May 30, 2026 | 483 ms |
| Jun 6, 2026 | 496 ms |
| Jun 13, 2026 | 499 ms |
| Jun 20, 2026 | 492 ms |
| Jun 27, 2026 | 483 ms |
| Jul 4, 2026 | 461 ms |
| Jul 11, 2026 | 438 ms |
| Jul 18, 2026 | 428 ms |
| Jul 25, 2026 | 419 ms |
| Aug 1, 2026 | 420 ms |
| Aug 8, 2026 | 422 ms |
| Aug 15, 2026 | 408 ms |
| Aug 22, 2026 | 403 ms |
| Aug 29, 2026 | 400 ms |
| Sep 5, 2026 | 405 ms |
| Sep 12, 2026 | 420 ms |
| Sep 19, 2026 | 423 ms |
| Sep 26, 2026 | 422 ms |
| Oct 3, 2026 | 411 ms |
| Oct 10, 2026 | 401 ms |
| Oct 17, 2026 | 395 ms |
| Oct 24, 2026 | 385 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
Speed
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
650 ms · 1.0 MB30 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.6 MB and 1.0 s of main-thread time.
Reduce unused JavaScript
300 ms · 831 KiBAbout 831 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 55). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 575 ms
575 msGoogle Tag Manager costs a phone 575 ms of main-thread work and 877 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.
Use efficient cache lifetimes
150 ms · 416 KiB27 files are served with short cache lifetimes, so returning visitors download them again (416 KiB).
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 401 ms. During a long task the page ignores taps.
2,430 HTML elements
The page has 2,430 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Legacy JavaScript
79 KiBPolyfills for old browsers add 79 KiB JavaScript that modern phones do not need.
Reduce unused CSS
19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 33 ms
33 msYour server sent the HTML in 33 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 30.6 s
30.6 sThe page becomes fully interactive after 30.6 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You bring ideas. Your clone films.”.
Total Blocking Time: 801 ms
801 msScripts block taps and scrolling for 801 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 420 ms
420 msReal visitors wait 420 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 424 ms to 385 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user TTFB: 672 ms
672 msReal visitors wait 672 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.0 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.059
0.059The layout barely moves while loading (CLS 0.059, good is under 0.1).
Images and page weight
Page weight: 41.3 MB in 249 requests
41.3 MBYour homepage downloads 41.3 MB in 249 requests on a phone: media 32.1 MB (6), images 6.5 MB (131) and scripts 2.4 MB (61). Under 2 MB keeps phones on slow connections fast.
38 images far larger than shown
833 KiB38 images are downloaded at several times the size a phone draws them, for example b391d6a9-038f-4f6c-81ab-19220dae632c.png at 400 px wide, shown at 117 px. Resized copies would save about 833 KiB.
38 images in older formats
38 images (3.5 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 11.7 g of CO₂ per visit
11.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.71 g of CO₂e: 1405.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
66 text elements with low contrast
66 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (5 elements)
Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
<svg> elements with an img or image role must have alternative text (1 element)
<svg> elements with an img or image role must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 162 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
212 internal links, 15 external
The homepage links to 212 pages on veed.io and 15 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Generate and edit in one workflow. Create talking heads, edit with AI, dub videos, and add subtitles — all in VEED. Bui…”.
One H1 headline
Your main headline reads: “You bring ideas. Your clone films.”.
Title: 58 characters
Your title is a healthy 58 characters: “VEED – AI Video Creation Platform | Idea to Video Workflow”.
Canonical URL set
The canonical URL is https://www.veed.io/.
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.veed.io/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,795 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.veed.io/llms.txt (6 KiB, 96 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.veed.io/workspaces is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without an H1
https://www.veed.io/workspaces 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 132 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.
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 a title
All 15 pages that loaded have a <title>.
Best practices
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 (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
111 of 111 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 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 481 words of copy
The homepage carries about 481 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: “Sign Up” and “Product Demo”.
8 calls to action
The homepage has 8 calls to action, for example “Eye Contact AI”, “Pricing” and “Sign Up”.
1 short form
A short form (2 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 26 customer or partner logos, a star rating and 5 trust badges.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 veed.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on veed.io, including 17 speed issues, 1 SEO issue and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.