pstrstudio.com website review

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

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

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

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

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

8 third-party services load with your homepage (Klaviyo, JSDelivr CDN and Shopify and others), adding 549 KiB and 223 ms of main-thread time.

About 52 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Polyfills for old browsers add 38 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 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image 47914389176658”.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 127 ms to 147 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 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 267 requests on a phone: images 2.5 MB (86), media 1.2 MB (1) and scripts 699 KiB (113). Under 2 MB keeps phones on slow connections fast.

0_Bestselling.jpg 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).

By the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 180.7 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: 28 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has 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.

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

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

There are 2 <h1> headlines (“PSTR studio” and “Black Friday”). One clear main headline is easier for people and search engines.

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

The homepage links to 489 pages on pstrstudio.com and 1 external page.

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.

https://www.pstrstudio.com/blogs/artists and https://www.pstrstudio.com/collections/minimalistic-graphic-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pstrstudio.com/products/eniko-eged-i-prefer-cowgirls, https://www.pstrstudio.com/products/maria-murphy-dont-want-to-go-to-work, https://www.pstrstudio.com/products/marion-one-one-three, https://www.pstrstudio.com/collections/frontpage, https://www.pstrstudio.com/products/phthalo-ruth-moo-tini and https://www.pstrstudio.com/collections/new-arrivals-1 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,429 words of visible text.

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