portier.co website review

hcaptcha.com costs a phone 3.2 s of main-thread work and 4.4 MB 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.

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

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Google CDN and gotolstoy.com and others), adding 86.6 MB and 4.3 s of main-thread time.

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

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

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Google CDN costs a phone 310 ms of main-thread work and 743 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.

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

gotolstoy.com costs a phone 202 ms of main-thread work and 918 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.

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

18 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Your homepage downloads 102.5 MB in 283 requests on a phone: media 92.0 MB (13), scripts 4.7 MB (94) and images 2.7 MB (60). Under 2 MB keeps phones on slow connections fast.

HOMEPAGE_SPLIT_LEFT_2500X2500_1.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).

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

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

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

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

13 form fields have no label, so screen readers announce an empty box and autofill guesses.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 21 characters: “portier | portier USA”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“portier USA” and “XANDER WHITE”). One clear main headline is easier for people and search engines.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 183 pages on portier.co and 10 external pages.

Your homepage links to https://portier.co/collections/baby-carriers-houndstooth, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

https://portier.co/collections/forme and https://portier.co/collections/clothing all use the title “Forme | portier USA”. Search engines can't tell which page to show for a search, so each competes with the others.

https://portier.co/customer_authentication/redirect, https://portier.co/collections/all-products, https://portier.co/collections/accessories, https://portier.co/collections/bags, https://portier.co/collections/gifting and https://portier.co/collections/new-arrivals and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://portier.co/collections/forme and https://portier.co/collections/clothing use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://portier.co/collections/clothing, whose canonical is https://portier.co/collections/forme. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://portier.co/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

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

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