vtoman.com website review

Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Facebook, Cloudflare CDN and JSDelivr CDN and others), adding 1.3 MB and 374 ms of main-thread time.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

Facebook costs a phone 333 ms of main-thread work and 270 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.

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

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

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

Shopify costs a phone 1 ms of main-thread work and 952 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.

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

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

About 83 KiB of JavaScript is downloaded but never used on this page.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

Your homepage downloads 2.4 MB in 122 requests on a phone: scripts 1.1 MB (41), images 798 KiB (29) and fonts 291 KiB (10). Under 2 MB keeps phones on slow connections fast.

2 images (118 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.

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

16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 22 characters: “Power Station | VTOMAN”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 212 pages on vtoman.com and 8 external pages.

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.

https://vtoman.com/products/vtoman-jump-1800-portable-power-station and https://vtoman.com/products/vtoman-jump-1800-v-beyond%E2%84%A2-portable-power-station-only-mex all use the title “1800 W Generator | 1800w Generator | 1800w power station | Vtoman – V…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://vtoman.com/pages/sale, https://vtoman.com/pages/ca-flash-sale, https://vtoman.com/pages/starting-battery, https://vtoman.com/collections/jump-series, https://vtoman.com/products/vtoman-jump-300-v-beyond%C2%AE-portable-power-station and https://vtoman.com/products/vtoman-jump-300-v-beyond%C2%AE-portable-power-station-with-110w-solar-panel and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://vtoman.com/products/vtoman-jump-1800-v-beyond%E2%84%A2-portable-power-station-only-mex, whose canonical is https://vtoman.com/products/vtoman-jump-1800-v-beyond%e2%84%a2-portable-power-station-only-mex. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

The homepage carries about 576 words of visible text.

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

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

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.

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