Website review, no card needed

sdc.com logo

sdc.com website review

Visit site (opens in a new tab)Reviewed 11 October 202619 issues · 82 checks

This review found 19 issues worth fixing on sdc.com, 2 of them high impact, across 82 checks. The most urgent: 1 text element with low contrast. 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
6.1 s4.4 sApr 18Oct 34.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20265.5 s
Apr 25, 20265.5 s
May 2, 20265.4 s
May 9, 20265.4 s
May 16, 20265.5 s
May 23, 20265.6 s
May 30, 20265.8 s
Jun 6, 20265.9 s
Jun 13, 20266.0 s
Jun 20, 20265.9 s
Jun 27, 20265.9 s
Jul 4, 20265.9 s
Jul 11, 20265.9 s
Jul 18, 20265.9 s
Jul 25, 20265.8 s
Aug 1, 20265.7 s
Aug 8, 20265.6 s
Aug 15, 20265.3 s
Aug 22, 20265.1 s
Aug 29, 20264.8 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
350 ms167 msApr 18Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026329 ms
Apr 25, 2026325 ms
May 2, 2026321 ms
May 9, 2026318 ms
May 16, 2026313 ms
May 23, 2026315 ms
May 30, 2026317 ms
Jun 6, 2026318 ms
Jun 13, 2026318 ms
Jun 20, 2026313 ms
Jun 27, 2026312 ms
Jul 4, 2026310 ms
Jul 11, 2026310 ms
Jul 18, 2026310 ms
Jul 25, 2026300 ms
Aug 1, 2026273 ms
Aug 8, 2026245 ms
Aug 15, 2026212 ms
Aug 22, 2026193 ms
Aug 29, 2026189 ms
Sep 5, 2026188 ms
Sep 12, 2026192 ms
Sep 19, 2026195 ms
Sep 26, 2026196 ms
Oct 3, 2026196 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 sdc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sdc.com at 0.4 s0.4 s
  2. sdc.com at 0.8 s0.8 s
  3. sdc.com at 1.1 s1.1 s
  4. sdc.com at 1.5 s1.5 s
  5. sdc.com at 1.9 s1.9 s
  6. sdc.com at 2.3 s2.3 s
  7. sdc.com at 2.6 s2.6 s
  8. sdc.com at 3.0 s3.0 s

Speed

4 to fix81
  • Mobile performance score: 81

    81/100

    Your mobile performance score is 81 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 58 KiB

    About 58 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    320 KiB

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

  • Google Tag Manager adds 264 ms

    264 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google/Doubleclick Ads and others), adding 211 KiB and 275 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • Reduce unused CSS

    24 KiB

    About 24 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    17 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 301 ms of it running JavaScript. That is comfortably low.

  • Server response: 18 ms

    18 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Join the world’s largest international swinging lifestyle c…”.

  • Time to Interactive: 4.8 s

    4.8 s

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

12 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: 0.9 s

    0.9 s

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

  • Real-user INP: 24 ms

    24 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 566 ms

    566 ms

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

  • Tap response (INP) got 40% faster for real visitors

    -40%

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Total Blocking Time: 148 ms

    148 ms

    Scripts block the page for only 148 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.053

    0.053

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.0 s

    2.0 s

    Visually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.19 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.19 g of CO₂e: 22.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 686 KiB in 37 requests

    686 KiB

    Your homepage downloads 686 KiB in 37 requests on a phone: images 285 KiB (20), scripts 229 KiB (6) and HTML 80 KiB (1). That is a lean page.

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9692
  • 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.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 2 form fields without a label

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10095
  • Structured data has 2 problems

    Structured data found (Organization, SoftwareApplication and WebSite) but with 2 problems, for example “SoftwareApplication: no offers (price) block”.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 149 internal links, 18 external

    The homepage links to 149 pages on sdc.com and 18 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “SDC.com is the world's leading swingers lifestyle dating website and community to find hookups, threesomes, swingers cl…”.

  • One H1 headline

    Your main headline reads: “Swingers Lifestyle Community for Open-Minded Couples & Singles”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “SDC Swingers Lifestyle: Seek, Discover, Connect | SDC.com”.

  • Canonical URL set

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

AI search readiness

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

  • llms.txt published

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

Other pages

1 to fix95
  • 2 pages without an H1

    https://www.sdc.com/swinging-swinger-relationships-guide and https://www.sdc.com/sdc-reviews 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 62 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 443 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Request a Business Profile”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Request a Business Profile” and “SDC Shop”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos and 10 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

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

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