vetsak.com website review

posthog.com costs a phone 1.7 s of main-thread work and 261 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (posthog.com, sevalla.app and Klaviyo and others), adding 14.5 MB and 2.4 s of main-thread time.

Shopify costs a phone 23 ms of main-thread work and 13.1 MB 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 738 KiB of JavaScript is downloaded but never used on this page.

sevalla.app costs a phone 302 ms of main-thread work and 534 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 long tasks block the main thread while loading, the longest for 340 ms. During a long task the page ignores taps.

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

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

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

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

About 58 KiB of CSS is downloaded but never applied on this page.

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

32 KiB JavaScript is shipped twice across bundles.

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

The layout shifts by 0.196 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 18.6 MB in 461 requests on a phone: media 13.0 MB (4), scripts 2.2 MB (110) and images 1.7 MB (54). Under 2 MB keeps phones on slow connections fast.

frequency-sofa-beige-coffee-table_600x.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

9 images (663 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 5.26 g of CO₂e: 631.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

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

There are 2 <h1> headlines (“” and “The Frequency Collection”). One clear main headline is easier for people and search engines.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 119 pages on vetsak.com and 34 external pages.

https://vetsak.com/collections/frequency-collection-all and https://vetsak.com/collections/frequency-collection-sofa-sets use the same meta description. A description written for each page earns more clicks.

https://vetsak.com/products/fabric-samples has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://vetsak.com/products/fabric-samples took over 3 s to send its HTML from our server.

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

6 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 913 words of visible text.

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