pull-in.com website review

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

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

Your mobile performance score is 71 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (Yotpo, Klaviyo and consentframework.com and others), adding 1.2 MB and 544 ms of main-thread time.

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

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

Yotpo costs a phone 313 ms of main-thread work and 590 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 130 ms of main-thread work and 323 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 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

27 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.4 MB in 281 requests on a phone: images 1.7 MB (28), scripts 1.5 MB (85) and other files 909 KiB (148). Under 2 MB keeps phones on slow connections fast.

mathildemetairie.FW26-HOMME-PARK-KAKI_TSH-RELAXBDARKY_DNG-CL 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 1.26 g of CO₂e: 150.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.pull-in.com/cdn/shop/files/pullin-logo-svg.svg?v=…”.

The homepage links to 173 pages on pull-in.com and 26 external pages.

/en-us/pages/lookbook/homme-fall-26 and /en-us/pages/look-category/homme-fall-26 all use the title “Homme - Fall '26 | PULLIN”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en-us/pages/store-locator, /en-us/pages/our-stores, /en-us/blogs/journal, /en-us/pages/faq and /en-us/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /collections/derniere-chance, whose canonical is /en-us/collections/last-chance. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en-us/pages/lookbook/homme-fall-26, /en-us/pages/look-category/homme-fall-26, /en-us/pages/lookbook/femme-fall-26 and /en-us/pages/look-category/femme-fall-26 have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 35 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.”).

5 errors were logged to the browser console while the page loaded, for example “L'API Shopify Customer Event n'est pas disponible.”.

Large scripts ship without source maps.

3 links from your homepage to your own site are broken, for example https://www.pull-in.com/en-us/collections/sweatshirts-and-jackets (500).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

Opening https://pull-in.com goes through 2 redirects before the homepage loads.

2 links go through two or more redirects, for example https://www.pull-in.com/en-us/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

pull-in.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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.

Your longest form asks for 104 fields (0 required). Every extra field lowers completion.

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

The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.

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 page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 23 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.