Website review, no card needed

ChowNow logo

chownow.com website review

Visit site (opens in a new tab)Reviewed 30 October 202636 issues · 63 checks

This review found 36 issues worth fixing on chownow.com, 12 of them high impact, across 63 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for ChowNow

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

66D

Not ranked: the homepage didn't load normally in this review.

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.4 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.5 s
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
120 ms111 msMay 9Oct 24113 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026118 ms
May 16, 2026119 ms
May 23, 2026119 ms
May 30, 2026117 ms
Jun 6, 2026114 ms
Jun 13, 2026113 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026112 ms
Jul 11, 2026112 ms
Jul 18, 2026112 ms
Jul 25, 2026112 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026112 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026113 ms
Sep 12, 2026113 ms
Sep 19, 2026112 ms
Sep 26, 2026113 ms
Oct 3, 2026113 ms
Oct 10, 2026113 ms
Oct 17, 2026113 ms
Oct 24, 2026113 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 chownow.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix65
  • Improve image delivery

    1.1 s · 210 KiB

    2 images could be 210 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 65

    65/100

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

  • Use efficient cache lifetimes

    150 ms · 527 KiB

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

  • Reduce unused JavaScript

    617 KiB

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

  • Render-blocking requests

    450 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Maps adds 171 ms

    171 ms

    Google Maps costs a phone 171 ms of main-thread work and 405 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Maps, Optanon and mParticle and others), adding 782 KiB and 357 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    65 KiB

    Polyfills for old browsers add 65 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    22 KiB

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix67
  • 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: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 11.2 s

    11.2 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Cumulative Layout Shift: 0.165

    0.165

    The layout shifts by 0.165 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 247 ms

    247 ms

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

  • Tap response (INP) held steady for real visitors

    -5%

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

7 checks passed
  • 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: 93 ms

    93 ms

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

  • Real-user FCP: 0.6 s

    0.6 s

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

  • Real-user TTFB: 313 ms

    313 ms

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

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

    -25%

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

  • Speed Index: 3.0 s

    3.0 s

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

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

Images and page weight

1 to fix67
  • Page weight: 2.1 MB in 61 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 61 requests on a phone: scripts 1.2 MB (26), images 680 KiB (10) and fonts 98 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.58 g

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

Accessibility

4 to fixGoogle 8786
  • 3 text elements with low contrast

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

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

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

1 checks passed
  • 18 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 21 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 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

10 to fixGoogle 10040
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (97 characters)

    Your title is 97 characters, so Google will cut it off around 60: “Access denied | www.chownow.com used Cloudflare to restrict access | www.chownow.com | Cl…”.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 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 XML sitemap

    No XML sitemap at https://www.chownow.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at chownow.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • No X (Twitter) card tag

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

1 checks passed
  • One H1 headline

    Your main headline reads: “Error 1005”.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix21
  • Homepage answers HTTP 403

    Your homepage answered with HTTP 403, so visitors and search engines may see an error page.

  • 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 social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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.

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

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 chownow.com, 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

Hiring

Hiring
15 open roles
Teams
Outside Sales (8), Finance (2), Sales (2), Marketing (1)
Job board
lever

Company

Founded
2011
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 36 issues on chownow.com, including 12 speed issues, 10 SEO issues and 7 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