Website review, no card needed
sarahpotempa.com website review
Visit site (opens in a new tab)Reviewed 11 November 202634 issues · 76 checks
This review found 34 issues worth fixing on sarahpotempa.com, 9 of them high impact, across 76 checks. The most urgent: page weight: 18.4 MB in 678 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 161 ms |
| May 30, 2026 | 162 ms |
| Jun 6, 2026 | 163 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 157 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 129 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 133 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 135 ms |
| Oct 31, 2026 | 137 ms |
| Nov 7, 2026 | 142 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
1.7 s
3.5 s
5.2 s
7.0 s
8.7 s
10.4 s
12.2 s
13.9 s
Speed
Main-thread work: 14.1 s
A phone's processor spends 14.1 s on main-thread work while loading, 6.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and getpurpledot.com and others), adding 4.0 MB and 3.3 s of main-thread time.
Shopify adds 834 ms
834 msShopify costs a phone 834 ms of main-thread work and 1.5 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.
Google Tag Manager adds 863 ms
863 msGoogle Tag Manager costs a phone 863 ms of main-thread work and 1.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.
getpurpledot.com adds 525 ms
525 msgetpurpledot.com costs a phone 525 ms of main-thread work and 158 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.
Accessibe Accessibility Overlay adds 389 ms
389 msAccessibe Accessibility Overlay costs a phone 389 ms of main-thread work and 251 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.
1,872 HTML elements
The page has 1,872 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
fwcdn3.com adds 149 ms
149 msfwcdn3.com costs a phone 149 ms of main-thread work and 370 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.
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: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 22.8 s
22.8 sVisually, the page fills in at 22.8 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 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 TTFB: 352 ms
352 msReal visitors wait 352 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 161 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 18.4 MB in 678 requests
18.4 MBYour homepage downloads 18.4 MB in 678 requests on a phone: scripts 6.5 MB (254), media 6.3 MB (5) and images 3.7 MB (66). Under 2 MB keeps phones on slow connections fast.
9 images far larger than shown
755 KiB9 images are downloaded at several times the size a phone draws them, for example preslee-lp-scrunchie-braid-pool-1080x1080.jpg at 1,080 px wide, shown at 240 px. Resized copies would save about 755 KiB.
An image on the first screen is lazy-loaded
preslee-lp-preslee-b1-smile-1-1080x1350.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 below the first screen load straight away
2 images further down the page (282 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.2 g of CO₂ per visit
5.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.20 g of CO₂e: 624.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 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.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (82 characters)
Your title is 82 characters, so Google will cut it off around 60: “Patented Rotating Curling Irons. Allure BEST OF BEAUTY Winner – The Beachwaver Co.”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“The Beachwaver Co.” and “The Beachwaver Co.”). One clear main headline is easier for people and search engines.
Meta description is long (297 characters)
Your meta description is 297 characters; Google truncates after about 160, so the end of your pitch is cut.
183 internal links, 7 external
The homepage links to 183 pages on sarahpotempa.com and 7 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://beachwaver.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://beachwaver.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.
No llms.txt
There is no https://beachwaver.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.
2 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 (735 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://beachwaver.com/collections/shop-all-products has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
6 checks passed
Linked pages load
3 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 3 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
13 of 14 tappable elements near the top are at least 24 px.
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 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 455 words of copy
The homepage carries about 455 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
30 calls to action
The homepage has 30 calls to action, for example “Shop Open submenu”, “Shop” and “Shop All”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar and TikTok Pixel.
Privacy and tracking
15 trackers load before any consent
15Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 10 mores (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.
47 cookies set on arrival
47Opening the homepage sets 47 cookies, 3 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.
105 other companies contacted
Loading the homepage contacts 105 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 sarahpotempa.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 24 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Klaviyo Email Marketing Sms · Tapcart Mobile App · Aimerce First Party Pixel · Triplewhale · Savedby Package Protection · Klickly Connector · Firework Shoppable Video Ugc · Mntn · Attentive · Region Restrictions · Zipifypages · Applovin Shop Integration · Upcart · Aftersell · Trustz · amazonaws.com · rechargecdn.com · retention.com · snapchat.com · attn.tv · automizely.com · adroll.com · instant.one
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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Union
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on sarahpotempa.com, including 13 speed issues, 4 SEO issues and 3 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.