Website review, no card needed

vivo-us.com logo

vivo-us.com website review

Visit site (opens in a new tab)Reviewed 22 October 202635 issues · 83 checks

This review found 35 issues worth fixing on vivo-us.com, 10 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
1.4 s1.2 sMay 2Oct 171.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
126 ms91 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026118 ms
May 9, 2026116 ms
May 16, 2026117 ms
May 23, 2026116 ms
May 30, 2026111 ms
Jun 6, 2026105 ms
Jun 13, 2026104 ms
Jun 20, 202698 ms
Jun 27, 202697 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202696 ms
Aug 22, 202698 ms
Aug 29, 2026103 ms
Sep 5, 2026104 ms
Sep 12, 2026106 ms
Sep 19, 2026113 ms
Sep 26, 2026118 ms
Oct 3, 2026121 ms
Oct 10, 2026122 ms
Oct 17, 2026120 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 vivo-us.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vivo-us.com at 0.7 s0.7 s
  2. vivo-us.com at 1.4 s1.4 s
  3. vivo-us.com at 2.2 s2.2 s
  4. vivo-us.com at 2.9 s2.9 s
  5. vivo-us.com at 3.6 s3.6 s
  6. vivo-us.com at 4.3 s4.3 s
  7. vivo-us.com at 5.0 s5.0 s
  8. vivo-us.com at 5.8 s5.8 s

Speed

8 to fix65
  • Render-blocking requests

    1.1 s

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

  • 5,635 HTML elements

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

  • Main-thread work: 4.2 s

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 75 KiB

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

  • Reduce unused CSS

    300 ms · 33 KiB

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

  • Klaviyo adds 140 ms

    140 ms

    Klaviyo costs a phone 140 ms of main-thread work and 381 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.

  • Shopify adds 39 ms

    39 ms

    Shopify costs a phone 39 ms of main-thread work and 303 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 (Klaviyo, Shopify and Cloudflare CDN and others), adding 886 KiB and 200 ms of main-thread time.

  • Improve image delivery

    150 ms · 134 KiB

    5 images could be 134 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.

  • Use efficient cache lifetimes

    150 ms · 51 KiB

    13 files are served with short cache lifetimes, so returning visitors download them again (51 KiB).

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    18 KiB

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

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 13.7 s

    13.7 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

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

    160 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 706 ms

    706 ms

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

  • Cumulative Layout Shift: 0.014

    0.014

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

  • Total Blocking Time: 30 ms

    30 ms

    Scripts block the page for only 30 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 291 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 291 requests on a phone: images 893 KiB (52), scripts 781 KiB (97) and other files 759 KiB (114). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.84 g

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

6 to fixGoogle 9192
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 20 links without text

    20 visible links have no text or label, so screen readers cannot say where they go.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

6 to fixGoogle 9274
  • Title is long (115 characters)

    Your title is 115 characters, so Google will cut it off around 60: “VIVO - Desks, Monitor Mounting, and More Home & Office Solutions – VIVO - desk solutions,…”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“VIVO - desk solutions, screen mounting, and more …”, “TV Mounts” and “1B Solid Top Series - Single Motor Electric Desk …”). One clear main headline is easier for people and search engines.

  • Meta description is long (283 characters)

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

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unterminated string in JSON at position 4273 (line 93 column)”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 268 internal links, 4 external

    The homepage links to 268 pages on vivo-us.com and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://vivo-us.com/.

  • 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://vivo-us.com/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,687 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://vivo-us.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 1 page without a meta description

    https://vivo-us.com/pages/support has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://vivo-us.com/collections/l-shape-standing-desks and https://vivo-us.com/collections/u-shape-standing-desks use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://vivo-us.com/pages/support, https://vivo-us.com/collections/most-popular-standing-desks, https://vivo-us.com/collections/manual-standing-desks, https://vivo-us.com/collections/l-shape-standing-desks, https://vivo-us.com/collections/u-shape-standing-desks and https://vivo-us.com/collections/desks-for-small-spaces and 9 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 (of 88 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Identifier 'SearchDrawer' has already been declared”.

2 checks passed
  • Tap targets are thumb-sized

    22 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 43 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.

  • Only about 200 words

    The homepage has only about 200 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “contact page”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “contact page”, “Shop all Desks” and “Shop all Mounting”.

  • 12 short forms

    12 short forms (3 fields at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 3 cookies set on arrival

    3

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

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 vivo-us.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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on vivo-us.com, including 12 speed issues, 6 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