Website review, no card needed

Everlane logo

everlane.com website review

Visit site (opens in a new tab)Reviewed 3 November 202647 issues · 88 checks

This review found 47 issues worth fixing on everlane.com, 17 of them high impact, across 88 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Everlane

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Score over time2 reviews
1000Oct 28Nov 373
Show as table
DateScore over time
Oct 28, 202673
Nov 3, 202673

Since Oct 28, 2026: Accessibility +3

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.8 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
282 ms198 msMay 16Oct 31271 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026211 ms
May 23, 2026208 ms
May 30, 2026209 ms
Jun 6, 2026212 ms
Jun 13, 2026218 ms
Jun 20, 2026221 ms
Jun 27, 2026232 ms
Jul 4, 2026236 ms
Jul 11, 2026233 ms
Jul 18, 2026232 ms
Jul 25, 2026230 ms
Aug 1, 2026233 ms
Aug 8, 2026245 ms
Aug 15, 2026254 ms
Aug 22, 2026265 ms
Aug 29, 2026271 ms
Sep 5, 2026272 ms
Sep 12, 2026272 ms
Sep 19, 2026271 ms
Sep 26, 2026271 ms
Oct 3, 2026271 ms
Oct 10, 2026271 ms
Oct 17, 2026271 ms
Oct 24, 2026272 ms
Oct 31, 2026271 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of everlane.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. everlane.com at 0.4 s0.4 s
  2. everlane.com at 0.8 s0.8 s
  3. everlane.com at 1.2 s1.2 s
  4. everlane.com at 1.6 s1.6 s
  5. everlane.com at 2.0 s2.0 s
  6. everlane.com at 2.4 s2.4 s
  7. everlane.com at 2.8 s2.8 s
  8. everlane.com at 3.2 s3.2 s

Speed

17 to fix34
  • Improve image delivery

    3.3 s · 1.3 MB

    9 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

  • Reduce unused JavaScript

    2.5 s · 1.5 MB

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

  • Use efficient cache lifetimes

    2.5 s · 1.2 MB

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

  • Main-thread work: 10.6 s

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

  • Mobile performance score: 34

    34/100

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

  • 4,348 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Bugsnag and ContentSquare and others), adding 2.4 MB and 2.7 s of main-thread time.

  • Google Tag Manager adds 904 ms

    904 ms

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

  • Render-blocking requests

    800 ms

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

  • Bugsnag adds 496 ms

    496 ms

    Bugsnag costs a phone 496 ms of main-thread work and 16 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.

  • Minify JavaScript

    450 ms · 26 KiB

    26 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    350 ms · 100 KiB

    Polyfills for old browsers add 100 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 60 KiB

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

  • ContentSquare adds 290 ms

    290 ms

    ContentSquare costs a phone 290 ms of main-thread work and 187 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.

  • Facebook adds 259 ms

    259 ms

    Facebook costs a phone 259 ms of main-thread work and 311 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.

  • PayPal adds 222 ms

    222 ms

    PayPal costs a phone 222 ms of main-thread work and 393 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.

  • Minify CSS

    150 ms · 14 KiB

    14 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 26.6 s

    26.6 s

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

  • Speed Index: 15.7 s

    15.7 s

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

  • Time to Interactive: 48.0 s

    48.0 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Total Blocking Time: 998 ms

    998 ms

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

  • Real-user INP: 215 ms

    215 ms

    Real visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • 10 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 569 ms

    569 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

6 to fix29
  • Page weight: 9.6 MB in 494 requests

    9.6 MB

    Your homepage downloads 9.6 MB in 494 requests on a phone: scripts 4.0 MB (165), images 3.9 MB (50) and other files 972 KiB (230). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    HP_Hero_Desktop_Image_d1db731d-dde0-4cc5-88ea-0793c1cddb2d.j weighs 490 KiB. On a phone connection a single image that size takes seconds.

  • 7 images below the first screen load straight away

    7 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

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

  • 2 images in older formats

    2 images (604 KiB) 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.

  • 5 images far larger than shown

    403 KiB

    5 images are downloaded at several times the size a phone draws them, for example HP_Large_Tile_02_Desktop_Image_e2721a5c-57fb-4280-a7b3-79f0b at 1,440 px wide, shown at 390 px. Resized copies would save about 403 KiB.

  • About 2.7 g of CO₂ per visit

    2.71 g

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

Accessibility

2 to fixGoogle 10097
  • 20 images without alt text

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

  • 6 links without text

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

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • Title is short (8 characters)

    Your title is only 8 characters: “Everlane”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 341 internal links, 32 external

    The homepage links to 341 pages on everlane.com and 32 external pages.

6 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Shop Everlane now for modern essentials. We make the most beautiful essentials, at the best factories, without traditio…”.

  • One H1 headline

    Your main headline reads: “Logo Everlane”.

  • Canonical URL set

    The canonical URL is https://www.everlane.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.everlane.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.everlane.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,211 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.everlane.com/collections/womens-new-arrivals has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://tvspix.com/t.png?&t=1793733333580&l=tvscientific-pix-o-5b74e56b-2b3b-4512-acd6-2dcfe5d048c8&u3=https%3A%2F%2Fwww.everlane.com%2F.

  • 9 small tap targets

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

  • 4 JavaScript errors while loading

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

  • 2 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

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

  • No direct contact details

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

  • Only about 225 words

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NEW ARRIVALS” and “SHOP BEST SELLERS”.

  • 45 calls to action

    The homepage has 45 calls to action, for example “SHOP NEW ARRIVALS”, “SHOP BEST SELLERS” and “Shop Now Shop Now”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 39 cookies set on arrival

    39

    Opening the homepage sets 39 cookies (measured from a US location before any click).

  • 71 other companies contacted

    Loading the homepage contacts 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at everlane.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Hiring

Hiring
33 open roles
Teams
Retail Store Team (18), Design (2), Ecommerce (2), Finance (2)
Job board
greenhouse

Company

Founded
2010
Headquarters
San Francisco

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on everlane.com, including 27 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25