Website review, no card needed
addavox.com website review
Visit site (opens in a new tab)Reviewed 3 November 202617 issues · 61 checks
This review found 17 issues worth fixing on addavox.com, 2 of them high impact, across 61 checks. The most urgent: avoid multiple page redirects. 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
91AClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Avoid multiple page redirects
1.4 sThe page goes through 1 redirect before it starts loading, costing about 1.4 s. Link and advertise the final URL directly.
Render-blocking requests
450 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.
Use efficient cache lifetimes
300 ms · 67 KiB13 files are served with short cache lifetimes, so returning visitors download them again (67 KiB).
Improve image delivery
150 ms · 50 KiB2 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.
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.
3 checks passed
Mobile performance score: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 138 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
6 checks passed
Largest Contentful Paint: 2.1 s
2.1 sYour largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Every language. Their own voice. Localize your video into o…”.
Time to Interactive: 2.1 s
2.1 sThe page is fully interactive after 2.1 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Speed Index: 1.1 s
1.1 sVisually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 24 ms
24 msScripts block the page for only 24 ms while loading. Good is under 200 ms.
Images and page weight
About 0.09 g of CO₂ per visit
0.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.09 g of CO₂e: 10.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 325 KiB in 28 requests
325 KiBYour homepage downloads 325 KiB in 28 requests on a phone: images 104 KiB (8), fonts 96 KiB (2) and scripts 62 KiB (14). That is a lean page.
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
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “AI Video Dubbing in 150+ Languages in the Speaker's Voice | Addavox”.
41 internal links, 6 external
The homepage links to 41 pages on addavox.com and 6 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Localize video into 150+ languages with AI that keeps the speaker's own voice, the original score and the rhythm of the…”.
One H1 headline
Your main headline reads: “Every language. Their own voice.”.
Canonical URL set
The canonical URL is https://addavox.com/en/index.html.
Structured data in place
Structured data found: Organization, WebApplication 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://addavox.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (887 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://addavox.com/llms.txt (5 KiB, 25 links), a plain-text guide to the site for AI tools.
Other pages
8 linked pages hidden from search
https://addavox.com/how-it-works.html, https://addavox.com/capabilities.html, https://addavox.com/ai-dubbing-for-lsps.html, https://addavox.com/ai-dubbing-for-translation-technology.html, https://addavox.com/pricing.html and https://addavox.com/api.html and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
8 pages share a title
https://addavox.com/how-it-works.html, https://addavox.com/capabilities.html, https://addavox.com/ai-dubbing-for-lsps.html, https://addavox.com/ai-dubbing-for-translation-technology.html, https://addavox.com/pricing.html and https://addavox.com/api.html and 2 others all use the title “Addavox”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://addavox.com/how-it-works.html, https://addavox.com/capabilities.html, https://addavox.com/ai-dubbing-for-lsps.html, https://addavox.com/ai-dubbing-for-translation-technology.html, https://addavox.com/pricing.html and https://addavox.com/api.html and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://addavox.com/how-it-works.html, https://addavox.com/capabilities.html, https://addavox.com/ai-dubbing-for-lsps.html, https://addavox.com/ai-dubbing-for-translation-technology.html, https://addavox.com/pricing.html and https://addavox.com/api.html and 2 others have 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 and read each the way a search engine does.
3 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 title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “rtlLanguages.includes is not a function”.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 701 words of copy
The homepage carries about 701 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start localizing”.
7 calls to action
The homepage has 7 calls to action, for example “Pricing”, “Start localizing” and “Get Started”.
Privacy and tracking
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.
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 addavox.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
- Tailwind CSS
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on addavox.com, including 3 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.