Website review, no card needed

swoveralls.com logo

swoveralls.com website review

Visit site (opens in a new tab)Reviewed 19 November 202637 issues · 86 checks

This review found 37 issues worth fixing on swoveralls.com, 13 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  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
1.4 s1.1 sMay 30Nov 141.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Nov 14, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
198 ms154 msMay 30Nov 14173 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026159 ms
Jun 6, 2026162 ms
Jun 13, 2026165 ms
Jun 20, 2026170 ms
Jun 27, 2026171 ms
Jul 4, 2026173 ms
Jul 11, 2026179 ms
Jul 18, 2026180 ms
Jul 25, 2026183 ms
Aug 1, 2026183 ms
Aug 8, 2026179 ms
Aug 15, 2026178 ms
Aug 22, 2026174 ms
Aug 29, 2026176 ms
Sep 5, 2026177 ms
Sep 12, 2026179 ms
Sep 19, 2026180 ms
Sep 26, 2026186 ms
Oct 3, 2026188 ms
Oct 10, 2026189 ms
Oct 17, 2026193 ms
Oct 24, 2026192 ms
Oct 31, 2026187 ms
Nov 7, 2026183 ms
Nov 14, 2026173 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 swoveralls.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. swoveralls.com at 1.0 s1.0 s
  2. swoveralls.com at 2.0 s2.0 s
  3. swoveralls.com at 3.1 s3.1 s
  4. swoveralls.com at 4.1 s4.1 s
  5. swoveralls.com at 5.1 s5.1 s
  6. swoveralls.com at 6.1 s6.1 s
  7. swoveralls.com at 7.1 s7.1 s
  8. swoveralls.com at 8.2 s8.2 s

Speed

14 to fix39
  • Use efficient cache lifetimes

    1.9 s · 700 KiB

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 6.3 s

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

  • 5,236 HTML elements

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

  • Reduce unused JavaScript

    900 ms · 1.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 3.7 MB and 1.5 s of main-thread time.

  • Shopify adds 580 ms

    580 ms

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

  • Reduce unused CSS

    300 ms · 140 KiB

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

  • Minify JavaScript

    300 ms · 139 KiB

    139 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 275 ms

    275 ms

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

  • 16 long tasks on the main thread

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

  • commslayer.com adds 165 ms

    165 ms

    commslayer.com costs a phone 165 ms of main-thread work and 1.4 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.

  • Klaviyo adds 234 ms

    234 ms

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

  • getripple.ai adds 29 ms

    29 ms

    getripple.ai costs a phone 29 ms of main-thread work and 442 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.

  • Improve image delivery

    188 KiB

    11 images could be 188 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    150 ms · 29 KiB

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

  • Render-blocking requests

    150 ms

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

  • Minify CSS

    9 KiB

    9 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

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 21 ms

    21 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 15.5 s

    15.5 s

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

  • Time to Interactive: 32.5 s

    32.5 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Total Blocking Time: 783 ms

    783 ms

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 170 ms

    170 ms

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

  • 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 FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 484 ms

    484 ms

    Real visitors wait 484 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

1 to fix70
  • Page weight: 6.5 MB in 456 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 456 requests on a phone: scripts 3.8 MB (150), images 1.1 MB (55) and other files 1.1 MB (198). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.83 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 10095
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Document should not have more than one main landmark (1 element)

    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)

    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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 109 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Swoveralls | Original Sweatpant Overalls | Comfiest Overalls on Earth”.

  • Meta description is long (312 characters)

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

  • 184 internal links, 12 external

    The homepage links to 184 pages on swoveralls.com and 12 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Introducing the boobies collection”.

  • Canonical URL set

    The canonical URL is https://swoveralls.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://swoveralls.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 (1,414 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 1 page without a meta description

    https://swoveralls.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://swoveralls.com/customer_authentication/redirect 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 44 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    4 pages 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.

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fixGoogle 7776
  • 2 broken images

    2 images failed to load on a phone, for example https://swoveralls.com/.

  • Deprecated browser APIs

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

  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    69 of 72 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

  • 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 947 words of copy

    The homepage carries about 947 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: “NEW arrivals just dropped. Shop now” and “Shop Now”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “NEW arrivals just dropped. Shop now”, “Shop All” and “Contact Us”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, a star rating and 5 trust badges.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads 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.

  • 13 cookies set on arrival

    13

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

  • No consent tool detected

    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.

  • 51 other companies contacted

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

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

Apps on your store

Your storefront loads 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Impact Com · Corso · Klaviyo Email Marketing Sms · Pp6n8ml66 Opensend · Smart Seo · Elevar Conversion Tracking · Klickly Connector · Ripple Ai Email Design · Triplewhale · Applovin Shop Integration · Aftersell · Gdpr Backpack · Rivo Loyalty Rewards Referrals · Click Context · retention.com · getripple.ai · onetext.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on swoveralls.com, including 19 speed issues, 2 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