Programmable

Website review, no card needed

9count.co logo

9count.co website review

Visit site (opens in a new tab)Reviewed 9 November 202615 issues · 65 checks

This review found 15 issues worth fixing on 9count.co, 5 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. 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

89B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
10.4 s937 msMay 23Nov 72.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20269.2 s
May 30, 20269.3 s
Jun 6, 20269.2 s
Jun 13, 20269.2 s
Jun 20, 20269.1 s
Jun 27, 20269.1 s
Jul 4, 20269.1 s
Jul 11, 20269.0 s
Jul 18, 20268.8 s
Jul 25, 20268.5 s
Aug 1, 20268.6 s
Aug 8, 20268.5 s
Aug 15, 20268.7 s
Aug 22, 20268.5 s
Aug 29, 20267.6 s
Sep 5, 20266.0 s
Sep 12, 20263.7 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
250 ms114 msMay 23Nov 7149 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026234 ms
May 30, 2026221 ms
Jun 6, 2026210 ms
Jun 13, 2026202 ms
Jun 20, 2026204 ms
Jun 27, 2026208 ms
Jul 4, 2026229 ms
Jul 11, 2026234 ms
Jul 18, 2026234 ms
Jul 25, 2026228 ms
Aug 1, 2026217 ms
Aug 8, 2026211 ms
Aug 15, 2026203 ms
Aug 22, 2026206 ms
Aug 29, 2026193 ms
Sep 5, 2026183 ms
Sep 26, 2026148 ms
Oct 3, 2026151 ms
Oct 10, 2026130 ms
Oct 17, 2026142 ms
Oct 24, 2026149 ms
Oct 31, 2026149 ms
Nov 7, 2026149 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.getwinkapp.com (opens in a new tab)
Full-page screenshot of 9count.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

99

  • Improve image delivery

    150 ms · 180 KiB

    3 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 178 KiB and 215 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    74 KiB

    About 74 KiB of JavaScript is downloaded but never used on this page.

  • 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: 99

    99/100

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

  • Main-thread work: 0.7 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

2 to fix100

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

  • Real-user TTFB: 906 ms

    906 ms

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

12 checks passed

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 135 ms

    135 ms

    Real visitors wait 135 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: 1.7 s

    1.7 s

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

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

    -35%

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

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

    -78%

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

  • Time to Interactive: 3.4 s

    3.4 s

    The page is fully interactive after 3.4 s.

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

  • Total Blocking Time: 66 ms

    66 ms

    Scripts block the page for only 66 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).

  • First Contentful Paint: 1.0 s

    1.0 s

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

  • Speed Index: 1.0 s

    1.0 s

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

Images and page weight

2 to fix86

  • An image on the first screen is lazy-loaded

    hteLeU49QRdClk4ij53Ca.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 12 images far larger than shown

    222 KiB

    12 images are downloaded at several times the size a phone draws them, for example i-A646gp6YvmmDsM66GrU.webp at 511 px wide, shown at 156 px. Resized copies would save about 222 KiB.

  • About 0.4 g of CO₂ per visit

    0.44 g

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

2 checks passed

  • Page weight: 1.5 MB in 30 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 30 requests on a phone: images 1.2 MB (25), scripts 177 KiB (1) and fonts 118 KiB (2). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

1 to fixGoogle 10097

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

2 checks passed

  • Every image has alt text

    All 77 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 10079

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Wink – Discover & Connect with new People Who Share Your Interests”.

  • No structured data

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

  • 28 internal links, 25 external

    The homepage links to 28 pages on 9count.co and 25 external pages.

5 checks passed

  • Meta description: 138 characters

    Your meta description is 138 characters: “Discover and connect with new people who share your interests and intentions. Wink is an AI-powered social app for mean…”.

  • Canonical URL set

    The canonical URL is https://getwinkapp.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://getwinkapp.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.

  • No llms.txt

    There is no https://www.getwinkapp.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.

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

Other pages

2 to fix93

  • 7 pages share a meta description

    https://www.getwinkapp.com/privacy, https://www.getwinkapp.com/terms, https://www.getwinkapp.com/communityguides, https://www.getwinkapp.com/for-ai-agents, https://www.getwinkapp.com/safety and https://www.getwinkapp.com/community and 1 other use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://www.getwinkapp.com/privacy, https://www.getwinkapp.com/terms, https://www.getwinkapp.com/communityguides, https://www.getwinkapp.com/safety and https://www.getwinkapp.com/community have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

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

6 checks passed

  • Linked pages load

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

Best practices

Google 96100

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed

  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58

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

  • Only about 28 words

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

3 checks passed

  • 10 calls to action

    The homepage has 10 calls to action, for example “Download on the App Store”, “Contact us” and “Download Wink”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

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

  • 1 other company contacted

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

Upkeep, stack and company

Stack

Hosting
Cloudflare

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on 9count.co, including 2 speed issues, 3 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