Website review, no card needed
loungeunderwear.com website review
Visit site (opens in a new tab)Reviewed 7 November 202626 issues · 78 checks
This review found 26 issues worth fixing on loungeunderwear.com, 8 of them high impact, across 78 checks. The most urgent: page weight: 4.1 MB in 200 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #10,777 of 108,846 reviewed websitesbeats 86%
- #6,649 of 61,763 online storesbeats 85%
- #6,455 of 56,363 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 96 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 101 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 125 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 126 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
Speed
Improve image delivery
1.4 MB6 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
4 third-party services on the page
4 third-party services load with your homepage (Snapchat, Adobe TypeKit and Shopify and others), adding 2.2 MB and 38 ms of main-thread time.
Shopify adds 0 ms
0 msShopify costs a phone 0 ms of main-thread work and 2.1 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
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.
Use efficient cache lifetimes
3 KiB2 files are served with short cache lifetimes, so returning visitors download them again (3 KiB).
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 44 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.6 s
17.6 sYour largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 18.1 s
18.1 sThe page becomes fully interactive after 18.1 s. Good is under 3.8 s.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 511 ms
511 msReal visitors wait 511 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 19 ms
19 msScripts block the page for only 19 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 200 requests
4.1 MBYour homepage downloads 4.1 MB in 200 requests on a phone: images 1.9 MB (8), other files 1.6 MB (174) and scripts 323 KiB (9). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
PartyWearHomepage3Nov7.png 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).
About 1.2 g of CO₂ per visit
1.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 2 problems
Structured data found (OnlineStore and WebSite) but with 2 problems, for example “OnlineStore: logo is not an absolute URL ("//lounge.com/cdn/shop/t/1076/assets/lounge-rectangle-log…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
26 internal links, 0 external
The homepage links to 26 pages on loungeunderwear.com and 0 external pages.
5 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Designed to make you look and feel sexy, Lounge creates comfortable underwear, always with you in mind. Shop Lounge now…”.
Title: 46 characters
Your title is a healthy 46 characters: “Lounge | Underwear & Clothing | Official Store”.
Canonical URL set
The canonical URL is https://lounge.com/.
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://lounge.com/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
30%The HTML your server sends has 80 of the 265 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://lounge.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://lounge.com/pages/lookbook-partywear, https://lounge.com/pages/lookbook-christmas-comforts and https://lounge.com/pages/daniela-for-lounge have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://lounge.com/pages/lookbook-partywear, https://lounge.com/pages/christmas-gifting, https://lounge.com/pages/lookbook-christmas-comforts and https://lounge.com/pages/daniela-for-lounge have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://lounge.com/collections/new-in, https://lounge.com/pages/lookbook-partywear, https://lounge.com/pages/christmas-gifting, https://lounge.com/pages/lookbook-christmas-comforts, https://lounge.com/collections/thongs-briefs and https://lounge.com/collections/bestsellers and 1 other have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 12 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
22 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 265 words of copy
The homepage carries about 265 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
8 calls to action
The homepage has 8 calls to action, for example “Shop Now”, “Shop Sleep” and “Shop Bottoms”.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies (measured from a US location before any click).
36 other companies contacted
Loading the homepage contacts 36 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 loungeunderwear.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 4 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Impact Com · Klaviyo Email Marketing Sms · snapchat.com · returngo.ai
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Solihull
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on loungeunderwear.com, including 9 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.