Website review, no card needed
undersummers.com website review
Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 76 checks
This review found 30 issues worth fixing on undersummers.com, 9 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
79C- #41,534 of 92,260 reviewed websitesbeats 50%
- #25,846 of 48,961 online storesbeats 41%
- #24,650 of 44,142 Shopify storesbeats 38%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 158 ms |
| May 30, 2026 | 156 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 148 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 159 ms |
| Sep 12, 2026 | 157 ms |
| Sep 19, 2026 | 157 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 181 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 188 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.5 s · 389 KiBAbout 389 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, iovation and Accessibe Accessibility Overlay and others), adding 948 KiB and 1.2 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 388 ms
388 msGoogle Tag Manager costs a phone 388 ms of main-thread work and 342 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 265 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 45 KiBAbout 45 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.
Use efficient cache lifetimes
150 ms · 33 KiB10 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
87 KiB2 images could be 87 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
50 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.
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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.1 s
9.1 sYour largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Total Blocking Time: 702 ms
702 msScripts block taps and scrolling for 702 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 158 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.6 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 770 ms
770 msReal visitors wait 770 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.5 MB in 198 requests
2.5 MBYour homepage downloads 2.5 MB in 198 requests on a phone: scripts 1.0 MB (52), other files 853 KiB (124) and images 331 KiB (9). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Black_and_White_Bold_Minimalist_Carousel_Instagram_Post_1.pn 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 0.7 g of CO₂ per visit
0.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 83.6 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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (287 characters)
Your meta description is 287 characters; Google truncates after about 160, so the end of your pitch is cut.
40 internal links, 0 external
The homepage links to 40 pages on undersummers.com and 0 external pages.
5 checks passed
Title: 57 characters
Your title is a healthy 57 characters: “Undersummers | Protecting Thighs From Chafe Under Dresses”.
Canonical URL set
The canonical URL is https://undersummers.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://undersummers.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (448 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://undersummers.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://undersummers.com/products/fusion-moisture-wicking-anti-chafing-shortlette-slipshort-9-ecru-cream and https://undersummers.com/products/womens-boxer-brief-with-1-waist-pocket-5-plus-size-3, which answer with an error. Visitors hit a dead end and search engines drop them.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://undersummers.com/collections/all-products/products/neutral-color-slip-short-1, whose canonical is https://undersummers.com/products/neutral-color-slip-short-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://undersummers.com/collections/last-chance-almost-gone-undersummers-sale-items and https://undersummers.com/collections/seasonal-sale 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 27 found) and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 13 pages 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 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187104054&tm=gtm002&Ver=2&mid=c079226d-d2b4-4ef7-b1c6-9511aa496f9a&bo=1&sid=b8566170dcc011f18c83235ba2a1612a&vid=b8568480dcc011f1b7ab27a92b048829&vids=1&msclkid=N>m_.
4 small tap targets
4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 357 words of copy
The homepage carries about 357 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop All Shortlettes”, “Quick buy” and “SHOP WAREHOUSE SALE”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 40 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 2 of them by other companies (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.
25 other companies contacted
Loading the homepage contacts 25 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 undersummers.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Kaching Cart · Free Shipping Bar · stamped.io · govx.com · getredo.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
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Conroe
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on undersummers.com, including 10 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.