Website review, no card needed

visiontechusa.com logo

visiontechusa.com website review

Visit site (opens in a new tab)Reviewed 27 October 202649 issues · 88 checks

This review found 49 issues worth fixing on visiontechusa.com, 19 of them high impact, across 88 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
2.7 s1.7 sAug 22Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.3 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
140 ms107 msAug 22Oct 17111 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026128 ms
Aug 29, 2026136 ms
Sep 5, 2026132 ms
Sep 12, 2026133 ms
Sep 19, 2026133 ms
Sep 26, 2026119 ms
Oct 3, 2026119 ms
Oct 10, 2026111 ms
Oct 17, 2026111 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 visiontechusa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. visiontechusa.com at 1.1 s1.1 s
  2. visiontechusa.com at 2.3 s2.3 s
  3. visiontechusa.com at 3.4 s3.4 s
  4. visiontechusa.com at 4.6 s4.6 s
  5. visiontechusa.com at 5.7 s5.7 s
  6. visiontechusa.com at 6.8 s6.8 s
  7. visiontechusa.com at 8.0 s8.0 s
  8. visiontechusa.com at 9.1 s9.1 s

Speed

12 to fix44
  • Render-blocking requests

    7.1 s

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

  • Reduce unused JavaScript

    3.9 s · 572 KiB

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

  • Use efficient cache lifetimes

    3.0 s · 590 KiB

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

  • Improve image delivery

    1.4 s · 677 KiB

    9 images could be 677 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Minify JavaScript

    1.1 s · 96 KiB

    96 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 44

    44/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and ShareThis and others), adding 953 KiB and 875 ms of main-thread time.

  • Google Tag Manager adds 452 ms

    452 ms

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

  • Font display

    450 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).

  • Legacy JavaScript

    350 ms · 26 KiB

    Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Main-thread work: 2.2 s

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

  • 1,810 HTML elements

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    49 KiB

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

1 checks passed
  • Server response: 123 ms

    123 ms

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

Core Web Vitals

6 to fix54
  • Largest Contentful Paint: 26.6 s

    26.6 s

    Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW FSA KFX i30 - ASYMMETRY OF PERFECTI…”.

  • Speed Index: 16.1 s

    16.1 s

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

  • Time to Interactive: 26.9 s

    26.9 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Total Blocking Time: 445 ms

    445 ms

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

  • 12 images without width and height

    12 images have no width and height attributes, so the layout jumps as each one loads.

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

3 checks passed
  • Tap response (INP) got 16% faster for real visitors

    -16%

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

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

    -19%

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

  • Cumulative Layout Shift: 0.058

    0.058

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

Images and page weight

1 to fix70
  • Page weight: 4.3 MB in 404 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 404 requests on a phone: images 2.6 MB (298), scripts 1.6 MB (58) and fonts 72 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (392 KiB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.23 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 8284
  • 246 images without alt text

    246 images have no alt text, which hurts accessibility and image search.

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

8 to fixGoogle 8370
  • 257 links crawlers can't follow

    257 links have no real href, so search engines can't follow them.

  • Title is short (16 characters)

    Your title is only 16 characters: “Full Speed Ahead”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 H1 headlines

    There are 6 <h1> headlines (“NEW FSA KFX i30 - ASYMMETRY OF PERFECTION”, “DOUBLE PODIUM IN VAL DI SOLE” and “FSA X FISCHBACH AT CERRO ABAJO STUTTGART”). One clear main headline is easier for people and search engines.

  • Meta description is long (379 characters)

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

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at visiontechusa.com/robots.txt, the first file search crawlers ask for.

  • 3 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 50 internal links, 108 external

    The homepage links to 50 pages on visiontechusa.com and 108 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://visiontechusa.com/en.

  • XML sitemap found

    Your XML sitemap is reachable at https://visiontechusa.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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 13 pages share 2 titles

    /, https://visiontechusa.com/en, https://visiontechusa.com/zhs, https://visiontechusa.com/zht, https://visiontechusa.com/it and https://visiontechusa.com/fr and 3 others all use the title “Full Speed Ahead”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://visiontechusa.com/en/discipline/mtb, https://visiontechusa.com/en/discipline/road, https://visiontechusa.com/en/discipline/e-bike and https://visiontechusa.com/en/discipline/gravel have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://visiontechusa.com/en, https://visiontechusa.com/zhs, https://visiontechusa.com/zht, https://visiontechusa.com/en/find-store and https://visiontechusa.com/en/technology use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 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 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

3 to fixGoogle 6988
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://visiontechusa.com' has been blocke…”.

  • 22 distorted images

    22 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    25 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

    The homepage carries about 529 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “SHOP TERM” and “Subscribe”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 visiontechusa.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
Drupal
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Equinix

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on visiontechusa.com, including 18 speed issues, 8 SEO issues 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

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