Website review, no card needed

campwander.com logo

campwander.com website review

Visit site (opens in a new tab)Reviewed 12 November 202636 issues · 79 checks

This review found 36 issues worth fixing on campwander.com, 18 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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.8 s1.4 sMay 30Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 20, 20261.5 s
Jul 4, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
130 ms103 msMay 30Oct 17108 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026106 ms
Aug 8, 2026127 ms
Aug 15, 2026121 ms
Aug 22, 2026121 ms
Aug 29, 2026118 ms
Oct 17, 2026108 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 campwander.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

12 to fix36
  • Reduce unused JavaScript

    5.7 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

  • Render-blocking requests

    2.3 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

  • Improve image delivery

    1.1 s · 488 KiB

    14 images could be 488 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Squarespace adds 1.0 s

    1.0 s

    Squarespace costs a phone 1.0 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 7.6 s

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

  • 5,173 HTML elements

    The page has 5,173 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 (Squarespace, Facebook and shapo.io and others), adding 2.8 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 394 KiB

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

  • Reduce unused CSS

    600 ms · 147 KiB

    About 147 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Legacy JavaScript

    450 ms · 139 KiB

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

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 263 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: 101 ms

    101 ms

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

Core Web Vitals

7 to fix41
  • Largest Contentful Paint: 19.2 s

    19.2 s

    Your largest element takes 19.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: 27.5 s

    27.5 s

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

  • Speed Index: 13.6 s

    13.6 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 829 ms

    829 ms

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

  • Cumulative Layout Shift: 0.101

    0.101

    The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

2 to fix60
  • Page weight: 4.7 MB in 201 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 201 requests on a phone: scripts 2.7 MB (104), images 828 KiB (30) and other files 389 KiB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    35 KiB

    1 image is downloaded at several times the size a phone draws it, for example Screenshot+2025-11-17+at+4.30.52 PM.png at 300 px wide, shown at 62 px. Resized copies would save about 35 KiB.

  • About 1.3 g of CO₂ per visit

    1.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 158.5 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 load when needed

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

Accessibility

4 to fixGoogle 9495
  • Unlabelled dropdowns

    1 dropdown has no label.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

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

  • 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. (20 elements).

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 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 10091
  • Meta description is long (184 characters)

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

  • Structured data has 3 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/690fc31c33b86401380…”.

  • 22 internal links, 0 external

    The homepage links to 22 pages on campwander.com and 0 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “The Camp Wander Shop”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Camp Wander | Essential Oils & Natural Wellness Shop”.

  • Canonical URL set

    The canonical URL is https://www.campwander.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://www.campwander.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    14%

    A phone browser shows 407 words, but the HTML your server sends has only 58. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • llms.txt published

    The site publishes https://www.campwander.com/llms.txt (1 KiB, 7 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix83
  • 1 page points its canonical at the homepage

    https://www.campwander.com/all-products declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.campwander.com/all-products all use the title “Camp Wander | Essential Oils & Natural Wellness Shop”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page with very little text

    https://www.campwander.com/all-products has 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.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • 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 4 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 407 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 31 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Squarespace
E-commerce
Shopify;Shopify Plus;Squarespace Add to Cart
Analytics
Google Analytics | Google Tag Manager
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

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

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