viwoods.com website review

8 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, omnisnippet1.com and Bing Ads and others), adding 2.0 MB and 1.0 s of main-thread time.

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

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

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

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

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

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

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

LoyaltyLion costs a phone 60 ms of main-thread work and 362 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 196 KiB of CSS is downloaded but never applied on this page.

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

15 KiB JavaScript is shipped twice across bundles.

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

8 KiB could be saved by minifying JavaScript.

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

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.

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

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

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Viwoods AiPaper paper tablet”. Most of its time is resource load delay (3.6 s).

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

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

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

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

Your homepage downloads 6.9 MB in 349 requests on a phone: images 3.6 MB (34), scripts 2.6 MB (186) and stylesheets 280 KiB (37). Under 2 MB keeps phones on slow connections fast.

4 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example aipaper-paper-tablet-banner-mobile-1.webp at 1,500 px wide, shown at 390 px. Resized copies would save about 1.9 MB.

6 images (6.3 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.

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

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

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

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

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

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

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

There are 5 <h1> headlines (“Paper Tablet for Focused Reading and Writing”, “AiPaper Reader Series” and “AiPaper Reader Series”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 76 pages on viwoods.com and 11 external pages.

https://viwoods.com/collections/all, https://viwoods.com/policies/shipping-policy and https://viwoods.com/pages/system-update-3-15 have no meta description, so Google writes the search snippet from whatever text it finds.

https://viwoods.com/pages/community has no <h1> headline, so visitors and search engines get no clear main topic.

https://viwoods.com/products/viwoods-stylus-pro, https://viwoods.com/products/us-ca-pre-sale-viwoods-w2-stylus-pro-tip-set, https://viwoods.com/products/viwoods-aipaper, https://viwoods.com/products/aipaper-mini and https://viwoods.com/products/viwoods-aipaper-reader-colour took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343174115&Ver=2&mid=e15c5a89-7f49-4275-916f-813ee96942ec&bo=1&sid=b5510190d8b111f1909653a7efb0103b&vid=b5512a40d8b111f18450535eae08cb83&vids=1&msclkid=N&pi=918639831&l.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Requests the notification permission on page load.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 568 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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 19 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 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.