Website review, no card needed

campingworld.com logo

campingworld.com website review

Visit site (opens in a new tab)Reviewed 12 October 202649 issues · 95 checks

This review found 49 issues worth fixing on campingworld.com, 22 of them high impact, across 95 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
2.4 s2.0 sApr 18Oct 32.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.2 s
Apr 25, 20262.2 s
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
252 ms227 msApr 18Oct 3249 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026241 ms
Apr 25, 2026238 ms
May 2, 2026238 ms
May 9, 2026238 ms
May 16, 2026237 ms
May 23, 2026237 ms
May 30, 2026234 ms
Jun 6, 2026232 ms
Jun 13, 2026232 ms
Jun 20, 2026230 ms
Jun 27, 2026233 ms
Jul 4, 2026235 ms
Jul 11, 2026231 ms
Jul 18, 2026231 ms
Jul 25, 2026232 ms
Aug 1, 2026230 ms
Aug 8, 2026233 ms
Aug 15, 2026235 ms
Aug 22, 2026236 ms
Aug 29, 2026237 ms
Sep 5, 2026238 ms
Sep 12, 2026241 ms
Sep 19, 2026245 ms
Sep 26, 2026247 ms
Oct 3, 2026249 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 campingworld.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. campingworld.com at 0.5 s0.5 s
  2. campingworld.com at 1.0 s1.0 s
  3. campingworld.com at 1.5 s1.5 s
  4. campingworld.com at 1.9 s1.9 s
  5. campingworld.com at 2.4 s2.4 s
  6. campingworld.com at 2.9 s2.9 s
  7. campingworld.com at 3.4 s3.4 s
  8. campingworld.com at 3.9 s3.9 s

Speed

15 to fix27
  • Reduce unused JavaScript

    4.3 s · 1.5 MB

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

  • Use efficient cache lifetimes

    2.8 s · 1.6 MB

    31 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

  • Render-blocking requests

    4.0 s

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

  • Reduce unused CSS

    1.3 s · 142 KiB

    About 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

  • Mobile performance score: 27

    27/100

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

  • Main-thread work: 8.2 s

    A phone's processor spends 8.2 s on main-thread work while loading, 5.3 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, VWO and Dynatrace and others), adding 2.1 MB and 3.4 s of main-thread time.

  • Google Tag Manager adds 906 ms

    906 ms

    Google Tag Manager costs a phone 906 ms of main-thread work and 712 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.

  • VWO adds 824 ms

    824 ms

    VWO costs a phone 824 ms of main-thread work and 249 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.

  • Dynatrace adds 489 ms

    489 ms

    Dynatrace costs a phone 489 ms of main-thread work and 144 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 470 ms. During a long task the page ignores taps.

  • vercel.app adds 356 ms

    356 ms

    vercel.app costs a phone 356 ms of main-thread work and 475 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.

  • Facebook adds 336 ms

    336 ms

    Facebook costs a phone 336 ms of main-thread work and 275 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.

  • 2,956 HTML elements

    The page has 2,956 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    263 KiB

    6 images could be 263 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    250 ms · 94 KiB

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

  • Minify JavaScript

    34 KiB

    34 KiB could be saved by minifying JavaScript.

  • 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 31 ms

    31 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Largest Contentful Paint: 16.2 s

    16.2 s

    Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “RVs, Camping Supplies & Outdoor Gear”.

  • Time to Interactive: 30.3 s

    30.3 s

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

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Speed Index: 9.5 s

    9.5 s

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

  • Real-user INP: 241 ms

    241 ms

    Real visitors wait 241 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.12

    0.12

    For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 241 ms to 249 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-10-03, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 717 ms

    717 ms

    Real visitors wait 717 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.5 MB in 227 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 227 requests on a phone: scripts 3.1 MB (70), images 855 KiB (55) and stylesheets 191 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    46 KiB

    3 images are downloaded at several times the size a phone draws them, for example 4pk-2.png at 591 px wide, shown at 171 px. Resized copies would save about 46 KiB.

  • About 1.3 g of CO₂ per visit

    1.26 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 151.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

13 to fixGoogle 6982
  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 38 images without alt text

    38 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

    5 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.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • 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 → h6, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 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: 44 passed and 11 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9297
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 833 internal links, 72 external

    The homepage links to 833 pages on campingworld.com and 72 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Shop the best selection of new & used RVs, outdoor gear, and camping supplies at Camping World—America’s largest RV dea…”.

  • One H1 headline

    Your main headline reads: “RVs, Camping Supplies & Outdoor Gear”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “#1 Destination for RV Sales & Camping Supplies”.

  • Canonical URL set

    The canonical URL is https://www.campingworld.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.campingworld.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (3,558 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix75
  • 1 page without a title

    https://www.campingworld.com/on/demandware.store/Sites-CampingWorld-Site/default/Stores-ShowGlobalStoreLocator has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.campingworld.com/on/demandware.store/Sites-CampingWorld-Site/default/Stores-ShowGlobalStoreLocator has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.campingworld.com/on/demandware.store/Sites-CampingWorld-Site/default/Stores-ShowGlobalStoreLocator has 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 199 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 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.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 248 words

    The homepage has only about 248 words of visible text; thin pages give Google and first-time buyers little to go on.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop RVs” and “Shop Gear”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop RVs”, “Shop Gear” and “Good Sam - Join Today”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 53 cookies set on arrival

    53

    Opening the homepage sets 53 cookies, 1 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.

  • 50 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on campingworld.com, including 24 speed issues, 1 SEO issue 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

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