slip.com website review

45 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and gotolstoy.com and others), adding 3.4 MB and 1.8 s of main-thread time.

81 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

Attentive costs a phone 86 ms of main-thread work and 708 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 30 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.

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

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

Desktop scores 64 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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.

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

Your largest element takes 8.1 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 13.7 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

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

Your homepage downloads 13.1 MB in 640 requests on a phone: images 8.7 MB (345), scripts 2.8 MB (131) and other files 876 KiB (130). Under 2 MB keeps phones on slow connections fast.

SKINNY-CLAIMS_HP-BANNER_MOB.jpg 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 3.72 g of CO₂e: 446.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Headings skip levels (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 385 pages on slip.com and 91 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.

/pages/wishlist, /collections/holiday-2026, /collections/new-arrivals, /collections/sleep-leisure-club, /collections/cornflower and /collections/slip-x-skims and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/shipping-policy, /pages/afterpay, /pages/wishlist, /collections/holiday-2026, /collections/new-arrivals and /collections/sleep-leisure-club and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://slipsilkpillowcase.myshopify.com/cdn/shop/files/pandectes-reopen-logo.png.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

Large scripts ship without source maps.

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

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 1,115 words of visible text.

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