shop-pitaya.com website review

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

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

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

8 third-party services load with your homepage (pitaya.dk, Klaviyo and Facebook and others), adding 1.2 MB and 724 ms of main-thread time.

10 images could be 454 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

Klaviyo costs a phone 160 ms of main-thread work and 353 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.

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

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

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

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

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

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

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 16.7 s. Good is under 3.8 s.

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 “Pitaya news banner mobile”.

Real visitors wait 222 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 111 ms to 139 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 3.5 MB in 186 requests on a phone: scripts 1.4 MB (81), images 1.1 MB (22) and other files 801 KiB (68). Under 2 MB keeps phones on slow connections fast.

1 image (78 KiB) is 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 1.00 g of CO₂e: 119.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 20 elements on the page fail this check, rated serious by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

There are 3 <h1> headlines (“PITAYA”, “PITAYA” and “PITAYA”). One clear main headline is easier for people and search engines.

Structured data found (Brand and Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//pitayacph.com/cdn/shop/t/152/assets/logo-dark.png?v=1…”.

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

The homepage links to 230 pages on shop-pitaya.com and 22 external pages.

https://pitayacph.com/collections/new-styles, https://pitayacph.com/collections/most-wanted, https://pitayacph.com/collections/nora-pants, https://pitayacph.com/pages/faq, https://pitayacph.com/pages/contact and https://pitayacph.com/collections/trending and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://pitayacph.com/collections/new-styles, https://pitayacph.com/collections/most-wanted, https://pitayacph.com/collections/nora-pants, https://pitayacph.com/products/velvet-makeup-bag-small-dark-brown, https://pitayacph.com/products/small-makeup-bag-beige-dark-brown-hearts and https://pitayacph.com/products/tote-bag-black-dots and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://pitayacph.com/collections/most-wanted, https://pitayacph.com/collections/nora-pants and https://pitayacph.com/collections/trending have 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://pitayacph.com/collections/new-styles, https://pitayacph.com/pages/faq and https://pitayacph.com/collections/trending took over 3 s to send their HTML from our server.

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

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

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.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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 581 words of visible text.

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