porefavor.com website review

8 third-party services load with your homepage (Google Tag Manager, ContentSquare and upstackified.com and others), adding 1.4 MB and 1.1 s of main-thread time.

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

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

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

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

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

Google Tag Manager costs a phone 274 ms of main-thread work and 355 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.8 MB in 328 requests on a phone: scripts 1.7 MB (109), other files 933 KiB (149) and images 868 KiB (23). Under 2 MB keeps phones on slow connections fast.

3 images (2.5 MB) are 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.

6 images further down the page (184 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.08 g of CO₂e: 129.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 element hidden from screen readers can still receive keyboard focus.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Your title is 85 characters, so Google will cut it off around 60: “Acne Supplement: Treats The Root Cause of Acne, Pimples & Blackheads – PORE FAVOR USA”.

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

3 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 38 pages on porefavor.com and 4 external pages.

https://www.porefavor.com/en-us and / all use the title “Acne Supplement: Treats The Root Cause of Acne, Pimples & Blackheads …”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.porefavor.com/en-us/collections/topicals, https://www.porefavor.com/en-us/collections/sale and https://www.porefavor.com/en-us/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.porefavor.com/en-us/products/clear-skin-supplement and https://www.porefavor.com/products/clear-skin-supplement use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.porefavor.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/, https://www.porefavor.com/en-us/products/clear-skin-supplement, https://www.porefavor.com/en-us/products/face-wash, https://www.porefavor.com/en-us/products/probiotic-moisturiser, https://www.porefavor.com/en-us/products/collagen and https://www.porefavor.com/en-us/pages/reviews and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/, https://www.porefavor.com/en-us/products/clear-skin-supplement, https://www.porefavor.com/en-us/products/face-wash, https://www.porefavor.com/en-us/products/probiotic-moisturiser, https://www.porefavor.com/en-us/products/collagen and https://www.porefavor.com/en-us/pages/reviews and 9 others 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 20 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97151904&Ver=2&mid=0b1ab4e6-7447-429e-897e-ecaeb24b8750&bo=1&sid=3117d600dc1611f18665a7bcacd29682&vid=3117f880dc1611f1ae0cf9d3584228d3&vids=1&msclkid=N&pi=918639831&lg.

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'top')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

The homepage carries about 682 words of visible text.

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