thepurest.ph website review

About 797 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

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

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

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

8 third-party services load with your homepage (zaapi.com, Shopify and Klaviyo and others), adding 2.5 MB and 766 ms of main-thread time.

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

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

About 101 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

zaapi.com costs a phone 409 ms of main-thread work and 682 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,505 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 123 ms of main-thread work and 1.2 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.

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

Polyfills for old browsers add 19 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.

3 KiB could be saved by minifying CSS.

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.

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

For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

6 images 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' largest content (lcp) went from 6.1 s to 7.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.8 MB in 398 requests on a phone: scripts 2.1 MB (135), images 2.0 MB (79) and other files 1.0 MB (151). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (130 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Structured data found (OnlineStore, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://thepurest.co)”.

Your <h1> is empty.

The homepage links to 214 pages on thepurest.ph and 19 external pages.

https://thepurest.ph/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://thepurest.ph/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://thepurest.ph/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://thepurest.ph/policies/terms-of-service, https://thepurest.ph/policies/privacy-policy and https://thepurest.ph/policies/shipping-policy use the same meta description. A description written for each page earns more clicks.

https://thepurest.ph/collections/all, https://thepurest.ph/pages/contact, https://thepurest.ph/customer_authentication/redirect, https://thepurest.ph/pages/loyalty-program, https://thepurest.ph/products/11-11-special-bundle and https://thepurest.ph/products/11-11-early-access-flash-deal-1-111 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 923 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 26 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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.