pinqponq.com website review

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

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

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

8 third-party services load with your homepage (accessibilityassistant.com, Klaviyo and Clarity and others), adding 719 KiB and 1.4 s of main-thread time.

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

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

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

accessibilityassistant.com costs a phone 420 ms of main-thread work and 220 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.

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

Clarity costs a phone 291 ms of main-thread work and 28 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,613 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

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

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

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

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

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

20 elements hidden from screen readers can still receive keyboard focus.

Some list items are not inside a list.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 2 <h1> headlines (“Warenkorb” and “BLACK WEEK SALE”). One clear main headline is easier for people and search engines.

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

The homepage links to 146 pages on pinqponq.com and 4 external pages.

https://pinqponq.com/collections/schultertaschen and https://pinqponq.com/collections/rucksack-accessoires have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

The page uses urgency cues (a countdown or limited-time wording).

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