Website review, no card needed

sugardaters.li logo

sugardaters.li website review

Visit site (opens in a new tab)Reviewed 17 November 202629 issues · 68 checks

This review found 29 issues worth fixing on sugardaters.li, 6 of them high impact, across 68 checks. The most urgent: render-blocking requests. 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
3.7 s3.2 sMay 30Nov 143.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.5 s
Jul 4, 20263.5 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.5 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.5 s
Nov 7, 20263.5 s
Nov 14, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
174 ms161 msMay 30Nov 14170 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026172 ms
Jun 6, 2026171 ms
Jun 13, 2026170 ms
Jun 20, 2026169 ms
Jun 27, 2026167 ms
Jul 4, 2026167 ms
Jul 11, 2026167 ms
Jul 18, 2026164 ms
Jul 25, 2026165 ms
Aug 1, 2026163 ms
Aug 8, 2026162 ms
Aug 15, 2026162 ms
Aug 22, 2026163 ms
Aug 29, 2026164 ms
Sep 5, 2026168 ms
Sep 12, 2026170 ms
Sep 19, 2026169 ms
Sep 26, 2026170 ms
Oct 3, 2026169 ms
Oct 10, 2026169 ms
Oct 17, 2026168 ms
Oct 24, 2026168 ms
Oct 31, 2026170 ms
Nov 7, 2026170 ms
Nov 14, 2026170 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 sugardaters.li (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix64
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 108 KiB

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

  • Reduce unused JavaScript

    300 ms · 64 KiB

    About 64 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.

  • 3 long tasks on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and Sentry), adding 136 KiB and 1 ms of main-thread time.

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

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 108 ms

    108 ms

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

Core Web Vitals

7 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: 13.1 s

    13.1 s

    Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tritt unserer lebendigen Community bei und übernimm die Kon…”.

  • Time to Interactive: 13.1 s

    13.1 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user CLS: 0.18

    0.18

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user INP: 170 ms

    170 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 468 ms

    468 ms

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

  • Total Blocking Time: 159 ms

    159 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix67
  • Page weight: 2.2 MB in 151 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 151 requests on a phone: other files 1.3 MB (51), scripts 445 KiB (79) and HTML 144 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.62 g

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

Accessibility

2 to fixGoogle 9693
  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 12 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 14 WCAG 2.2 A/AA and best-practice rules on the phone render: 12 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10081
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “SugarDaters - Erleben Sie SugarDating-Beziehungen in einem sicheren Raum”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (303 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), 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.

  • 38 internal links, 3 external

    The homepage links to 38 pages on sugardaters.li and 3 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Dein Liebesleben zu deinen eigenen Bedingungen”.

  • Canonical URL set

    The canonical URL is https://sugardaters.com/de.

  • 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://sugardaters.com/sitemap/xml.

AI search readiness

1 to fix83
  • 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.

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://sugardaters.com/llms.txt (6 KiB, 17 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

    https://sugardaters.com/en/home and https://sugardaters.com/us/home all use the title “SugarDaters - Experience SugarDating Relationships In A Safe Space”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://sugardaters.com/en/home, whose canonical is https://sugardaters.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages share a meta description

    https://sugardaters.com/en/home and https://sugardaters.com/us/home use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://sugardaters.com/en/home, https://sugardaters.com/us/home, https://sugardaters.com/da/home, https://sugardaters.com/es/home, https://sugardaters.com/se/home and https://sugardaters.com/fi/home and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://sugardaters.com/bg/home 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 32 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 10092
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “[NUXT_E1005]”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 11 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 sugardaters.li, 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 29 issues on sugardaters.li, including 11 speed issues, 4 SEO issues and 5 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