purize-filters.com website review

Shopify costs a phone 1.1 s of main-thread work and 571 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 5.7 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Shopify, tt-srv.com and Klaviyo and others), adding 1.3 MB and 1.7 s of main-thread time.

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

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

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

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

tt-srv.com costs a phone 308 ms of main-thread work and 60 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,892 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

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

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

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

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

Real visitors wait 219 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' largest content (lcp) went from 1.0 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Scripts block taps and scrolling for 538 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.

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

Your homepage downloads 12.4 MB in 297 requests on a phone: media 9.4 MB (1), scripts 1.2 MB (128) and other files 847 KiB (105). Under 2 MB keeps phones on slow connections fast.

Mobile_78fe68bf-9e08-4b4a-aafb-39525789f7aa.png 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).

1 image is downloaded at several times the size a phone draws it, for example Mobile_78fe68bf-9e08-4b4a-aafb-39525789f7aa.png at 1,500 px wide, shown at 390 px. Resized copies would save about 40 KiB.

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

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 116 pages on purize-filters.com and 7 external pages.

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.

There is no https://purize-filters.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://purize-filters.com/en/policies/shipping-policy, https://purize-filters.com/en/collections/thc-crew, https://purize-filters.com/en/collections/criminel, https://purize-filters.com/en/collections/kif-kif and https://purize-filters.com/en/collections/eko420 have no meta description, so Google writes the search snippet from whatever text it finds.

https://purize-filters.com/en/policies/shipping-policy, https://purize-filters.com/en/collections/thc-crew, https://purize-filters.com/en/collections/criminel, https://purize-filters.com/en/collections/kif-kif, https://purize-filters.com/en/collections/eko420 and https://purize-filters.com/en/collections/sale and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://purize-filters.com/en/policies/shipping-policy, https://purize-filters.com/en/collections/thc-crew, https://purize-filters.com/en/collections/criminel, https://purize-filters.com/en/collections/kif-kif, https://purize-filters.com/en/collections/eko420 and https://purize-filters.com/en/collections/sale and 1 other 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.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

Chrome logged issues while loading the page (“Cookie”).

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

Social proof on the homepage: 25 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage carries about 471 words of visible text.

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