Website review, no card needed
calledtosurf.com website review
Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 76 checks
This review found 28 issues worth fixing on calledtosurf.com, 11 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
84B- #21,297 of 118,247 reviewed websitesbeats 77%
- #13,849 of 67,198 online storesbeats 73%
- #13,443 of 61,274 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 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.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 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.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 112 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 117 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 111 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 112 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.3 s · 223 KiBAbout 223 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Improve image delivery
850 ms · 2.9 MB44 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 120 KiB7 files are served with short cache lifetimes, so returning visitors download them again (120 KiB).
Legacy JavaScript
300 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,127 HTML elements
The page has 2,127 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 (Klaviyo, Shopify and tabarn.app and others), adding 719 KiB and 435 ms of main-thread time.
Render-blocking requests
150 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.
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: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.2 s
17.2 sYour largest element takes 17.2 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.0 s
18.0 sThe page becomes fully interactive after 18.0 s. Good is under 3.8 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 394 ms
394 msReal visitors wait 394 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 185 ms
185 msScripts block the page for only 185 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 176 requests
5.0 MBYour homepage downloads 5.0 MB in 176 requests on a phone: images 4.0 MB (65), scripts 662 KiB (50) and other files 148 KiB (18). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
1-Dress_mobile_GIF.gif weighs 1.2 MB. On a phone connection a single image that size takes seconds.
13 images far larger than shown
1.1 MB13 images are downloaded at several times the size a phone draws them, for example A_young_woman_wearing_a_loose_fitting_red_white_stripe_top.. at 800 px wide, shown at 149 px. Resized copies would save about 1.1 MB.
2 images in older formats
2 images (1.3 MB) 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.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.7 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
29 text elements with low contrast
29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 62 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“”, “Reset your password” and “Login”). One clear main headline is easier for people and search engines.
158 internal links, 7 external
The homepage links to 158 pages on calledtosurf.com and 7 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “For the latest in women's fashion, including dresses, tops, bottoms, swimwear, accessories, and more, be sure to shop a…”.
Title: 60 characters
Your title is a healthy 60 characters: “Women’s Clothing Boutique for All Occasions | Called to Surf”.
Canonical URL set
The canonical URL is https://calledtosurf.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://calledtosurf.com/sitemap.xml.
AI search readiness
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, 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 (743 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://calledtosurf.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://calledtosurf.com/collections/best-selling-products and https://calledtosurf.com/collections/best-sellers have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://calledtosurf.com/collections/new-arrivals, https://calledtosurf.com/collections/best-selling-products, https://calledtosurf.com/collections/dresses, https://calledtosurf.com/collections/best-sellers, https://calledtosurf.com/collections/short-dresses and https://calledtosurf.com/pages/bridesmaid and 2 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 68 found) and read each the way a search engine does.
5 checks passed
Linked pages load
12 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'textContent')”.
2 checks passed
Tap targets are thumb-sized
16 of 17 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 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 282 words of copy
The homepage carries about 282 words of visible text.
2 checks passed
18 calls to action
The homepage has 18 calls to action, for example “Sign in/ Sign up”, “Shop New” and “Shop All Dresses”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
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 calledtosurf.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
Klaviyo Email Marketing Sms · Triplewhale · Crazy Egg · Zapiet Pickup Delivery · Redo Free Return Automation · Automatic Discounts Upsells · snapchat.com · stamped.io · cloudfront.net · shareasale.com · carecart.io · gorgias.chat · nice-team.net · hextom.com · rebuyengine.com · 9gtb.com · useamp.com · pushowl.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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Provo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on calledtosurf.com, including 11 speed issues, 1 SEO issue and 4 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.