Website review, no card needed

Eddie Bauer logo

eddiebauer.com website review

Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 83 checks

This review found 41 issues worth fixing on eddiebauer.com, 16 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Eddie Bauer

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

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

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.3 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.5 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20262.0 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.4 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
174 ms123 msMay 16Oct 31165 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026133 ms
May 30, 2026137 ms
Jun 6, 2026139 ms
Jun 13, 2026145 ms
Jun 20, 2026146 ms
Jun 27, 2026151 ms
Jul 4, 2026153 ms
Jul 11, 2026153 ms
Jul 18, 2026153 ms
Jul 25, 2026153 ms
Aug 1, 2026153 ms
Aug 8, 2026154 ms
Aug 15, 2026159 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026162 ms
Sep 12, 2026163 ms
Sep 19, 2026163 ms
Sep 26, 2026163 ms
Oct 3, 2026163 ms
Oct 10, 2026163 ms
Oct 17, 2026164 ms
Oct 24, 2026168 ms
Oct 31, 2026165 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 eddiebauer.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eddiebauer.com at 1.0 s1.0 s
  2. eddiebauer.com at 2.0 s2.0 s
  3. eddiebauer.com at 2.9 s2.9 s
  4. eddiebauer.com at 3.9 s3.9 s
  5. eddiebauer.com at 4.9 s4.9 s
  6. eddiebauer.com at 5.9 s5.9 s
  7. eddiebauer.com at 6.8 s6.8 s
  8. eddiebauer.com at 7.8 s7.8 s

Speed

14 to fix29
  • Reduce unused JavaScript

    2.4 s · 908 KiB

    About 908 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 632 KiB

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

  • Signyfyd adds 1.2 s

    1.2 s

    Signyfyd costs a phone 1.2 s of main-thread work and 240 KiB 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.

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 9.7 s

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

  • 3,983 HTML elements

    The page has 3,983 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 (Signyfyd, Klaviyo and Noibu and others), adding 2.1 MB and 2.9 s of main-thread time.

  • Improve image delivery

    100 ms · 1.9 MB

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

  • Render-blocking requests

    600 ms

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

  • 20 long tasks on the main thread

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

  • Klaviyo adds 370 ms

    370 ms

    Klaviyo costs a phone 370 ms of main-thread work and 610 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.

  • Google Tag Manager adds 335 ms

    335 ms

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

  • Noibu adds 346 ms

    346 ms

    Noibu costs a phone 346 ms of main-thread work and 162 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.

  • Shopify adds 282 ms

    282 ms

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

  • Legacy JavaScript

    150 ms · 66 KiB

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

  • Reduce unused CSS

    150 ms · 46 KiB

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

  • Font display

    50 ms

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

  • Duplicated JavaScript

    25 KiB

    25 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

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

1 checks passed
  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 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: 15.9 s

    15.9 s

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

  • Time to Interactive: 24.8 s

    24.8 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user CLS: 0.17

    0.17

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

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

    +27%

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

  • Largest content (LCP) got 56% slower for real visitors

    +56%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.161

    0.161

    The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.

4 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 688 ms

    688 ms

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

Images and page weight

2 to fix50
  • Page weight: 6.7 MB in 449 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 449 requests on a phone: images 2.8 MB (104), scripts 2.5 MB (161) and other files 992 KiB (141). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    1.4 MB

    8 images are downloaded at several times the size a phone draws them, for example 261103_4box_Sweaters_2x_6b97c417-f7a3-4557-a383-ab12226382bc at 1,300 px wide, shown at 163 px. Resized copies would save about 1.4 MB.

  • 2 images in older formats

    2 images (84 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.

  • About 1.9 g of CO₂ per visit

    1.89 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

1 to fixGoogle 9999
  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Eddie Bauer: Outdoor Apparel, Outerwear & Gear | Free Shipping $99+”.

  • Meta description is long (182 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.eddiebauer.com/search?q={search_term_string}")”.

  • One H1 headline

    Your <h1> is empty.

  • 352 internal links, 2 external

    The homepage links to 352 pages on eddiebauer.com and 2 external pages.

4 checks passed
  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.eddiebauer.com/sitemap.xml.

AI search readiness

100
4 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, sameAs (social profiles) and description; logo and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.eddiebauer.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 8 pages without a meta description

    https://www.eddiebauer.com/customer_authentication/redirect, https://www.eddiebauer.com/collections/holiday-gift-guide, https://www.eddiebauer.com/collections/cozy, https://www.eddiebauer.com/collections/fleece, https://www.eddiebauer.com/collections/flannel and https://www.eddiebauer.com/collections/holiday-sweaters and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.eddiebauer.com/customer_authentication/redirect, https://www.eddiebauer.com/collections/holiday-gift-guide, https://www.eddiebauer.com/collections/womens-all, https://www.eddiebauer.com/collections/mens-all, https://www.eddiebauer.com/collections/new-arrivals and https://www.eddiebauer.com/collections/best-sellers and 3 others have 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 121 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://i.liadm.com/s/89602?shd_id=XMXkXW0r5E7oDsrlZWam&account_id=4gqgby-g9.myshopify.com.

  • 10 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “ApiService#sendApiRequest: Error sending loop_optimization_assignment to https://shopify-events.loopreturns.com/: TypeE…”.

  • 1 distorted image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 direct contact details

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 342 words of copy

    The homepage carries about 342 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign In / Sign Up” and “SHOP NOW”.

  • 50 calls to action

    The homepage has 50 calls to action, for example “SIGN UP NOW”, “Sign In / Sign Up” and “SHOP GIFT GUIDE”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 7 trackers load before any consent

    7

    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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 33 cookies set on arrival

    33

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

  • 59 other companies contacted

    Loading the homepage contacts 59 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 eddiebauer.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Employees
10,000
Founded
1920
Headquarters
Bellevue

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on eddiebauer.com, including 24 speed issues, 4 SEO issues and 2 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