Programmable

Website review, no card needed

asugardating.com logo

asugardating.com website review

Visit site (opens in a new tab)Reviewed 11 November 202618 issues · 70 checks

This review found 18 issues worth fixing on asugardating.com, 4 of them high impact, across 70 checks. The most urgent: 50 text elements 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

Site score

86B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
659 ms424 msMay 23Nov 7632 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026460 ms
May 30, 2026459 ms
Jun 6, 2026458 ms
Jun 13, 2026452 ms
Jun 20, 2026466 ms
Jun 27, 2026467 ms
Jul 4, 2026468 ms
Jul 11, 2026466 ms
Jul 18, 2026454 ms
Jul 25, 2026451 ms
Aug 1, 2026454 ms
Aug 8, 2026458 ms
Aug 15, 2026464 ms
Aug 22, 2026463 ms
Aug 29, 2026463 ms
Sep 5, 2026479 ms
Sep 12, 2026515 ms
Sep 19, 2026563 ms
Sep 26, 2026606 ms
Oct 3, 2026628 ms
Oct 10, 2026622 ms
Oct 17, 2026612 ms
Oct 24, 2026603 ms
Oct 31, 2026615 ms
Nov 7, 2026632 ms
Real-visitor tap response (INP)75th percentile, phones
91 ms54 msMay 23Nov 787 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202658 ms
May 30, 202658 ms
Jun 6, 202659 ms
Jun 13, 202659 ms
Jun 20, 202661 ms
Jun 27, 202661 ms
Jul 4, 202661 ms
Jul 11, 202661 ms
Jul 18, 202661 ms
Jul 25, 202661 ms
Aug 1, 202661 ms
Aug 8, 202661 ms
Aug 15, 202660 ms
Aug 22, 202659 ms
Aug 29, 202659 ms
Sep 5, 202662 ms
Sep 12, 202669 ms
Sep 19, 202677 ms
Sep 26, 202683 ms
Oct 3, 202686 ms
Oct 10, 202687 ms
Oct 17, 202686 ms
Oct 24, 202686 ms
Oct 31, 202687 ms
Nov 7, 202687 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

www.asugardating.com (opens in a new tab)
Full-page screenshot of asugardating.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix95

  • Use efficient cache lifetimes

    300 ms · 2.6 MB

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

  • Reduce unused JavaScript

    300 ms · 97 KiB

    About 97 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 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Google Analytics), adding 2.8 MB and 110 ms of main-thread time.

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 2.6 MB 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.

  • 3 long tasks on the main thread

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 checks passed

  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

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

  • Server response: 17 ms

    17 ms

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

Core Web Vitals

3 to fix100

  • Tap response (INP) got 50% slower for real visitors

    +50%

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

  • Largest content (LCP) got 36% slower for real visitors

    +36%

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “aSugarDating（甜心寶貝包養網）首頁主視覺：專為台灣漂亮甜心寶貝們及成熟男士相遇而設的交友平台”.

11 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.8 s

    0.8 s

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

  • Real-user INP: 66 ms

    66 ms

    Real visitors wait 66 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.7 s

    0.7 s

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

  • Real-user TTFB: 404 ms

    404 ms

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

  • Time to Interactive: 3.0 s

    3.0 s

    The page is fully interactive after 3.0 s.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • Speed Index: 1.5 s

    1.5 s

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

  • Total Blocking Time: 26 ms

    26 ms

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

Images and page weight

1 to fix85

  • Page weight: 2.9 MB in 16 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 16 requests on a phone: media 2.5 MB (1), scripts 217 KiB (3) and images 98 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.81 g

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

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

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9594

  • 50 text elements with low contrast

    50 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (4 elements)

    Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious 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.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

Google 100100

  • 20 internal links, 22 external

    The homepage links to 20 pages on asugardating.com and 22 external pages.

8 checks passed

  • Meta description: 106 characters

    Your meta description is 106 characters: “專為高端紳士與甜心寶貝打造的約會首選。aSugarDating 甜心寶貝包養網透過專業人工與 AI 雙重把關，全面杜絕假帳號，守護雙方隱私。在這裡告別無效社交，輕鬆遇見懂妳的實力紳士與心動對象。立即免費註冊體驗！”.

  • One H1 headline

    Your main headline reads: “aSugarDating 頂級訂製約會平台 | 甜心寶貝包養網”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “aSugarDating 甜心寶貝包養網｜嚴格真人審核｜高端精緻約會首選”.

  • Canonical URL set

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

AI search readiness

100

  • No llms.txt

    There is no https://www.asugardating.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

Other pages

1 to fix95

  • 1 page without an H1

    https://www.asugardating.com/intro has no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://www.asugardating.com/intro, https://www.asugardating.com/mediareports, https://www.asugardating.com/statement, https://www.asugardating.com/aboutus, https://www.asugardating.com/contactus and https://www.asugardating.com/sitemap and 3 others have 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.

  • 14 internal pages checked

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

6 checks passed

  • Linked pages load

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

Best practices

1 to fixGoogle 9693

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50

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

  • 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 72 words

    The homepage has only about 72 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.

2 checks passed

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and a star rating.

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

  • 4 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on asugardating.com, including 7 speed 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