Website review, no card needed

Close logo

close.com website review

Visit site (opens in a new tab)Reviewed 17 November 202621 issues · 80 checks

This review found 21 issues worth fixing on close.com, 10 of them high impact, across 80 checks. The most urgent: main-thread work: 22.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Close

  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
4.1 s1.2 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20263.1 s
Jul 25, 20263.4 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.7 s
Aug 22, 20263.4 s
Aug 29, 20263.2 s
Sep 5, 20262.8 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.4 s
Oct 3, 20262.2 s
Oct 10, 20261.9 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
241 ms122 msMay 30Nov 14162 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026136 ms
Jun 6, 2026139 ms
Jun 13, 2026147 ms
Jun 20, 2026153 ms
Jun 27, 2026160 ms
Jul 4, 2026162 ms
Jul 11, 2026149 ms
Jul 18, 2026141 ms
Jul 25, 2026155 ms
Aug 1, 2026175 ms
Aug 8, 2026214 ms
Aug 15, 2026227 ms
Aug 22, 2026218 ms
Aug 29, 2026207 ms
Sep 5, 2026154 ms
Sep 12, 2026141 ms
Sep 19, 2026140 ms
Sep 26, 2026140 ms
Oct 3, 2026145 ms
Oct 10, 2026144 ms
Oct 17, 2026146 ms
Oct 24, 2026154 ms
Oct 31, 2026155 ms
Nov 7, 2026164 ms
Nov 14, 2026162 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 close.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. close.com at 2.4 s2.4 s
  2. close.com at 4.8 s4.8 s
  3. close.com at 7.1 s7.1 s
  4. close.com at 9.5 s9.5 s
  5. close.com at 11.9 s11.9 s
  6. close.com at 14.3 s14.3 s
  7. close.com at 16.6 s16.6 s
  8. close.com at 19.0 s19.0 s

Speed

9 to fix36
  • Main-thread work: 22.5 s

    A phone's processor spends 22.5 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6,038 HTML elements

    The page has 6,038 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused JavaScript

    850 ms · 512 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 944 KiB and 814 ms of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 453 KiB

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

  • Google Tag Manager adds 296 ms

    296 ms

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

  • Facebook adds 276 ms

    276 ms

    Facebook costs a phone 276 ms of main-thread work and 220 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.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 22 KiB

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

  • Improve image delivery

    83 KiB

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

  • Legacy JavaScript

    60 KiB

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

  • Minify JavaScript

    36 KiB

    36 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 23.5 s

    23.5 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The CRM that sells with you”. Most of its time is element render delay (2.3 s).

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

    +19%

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

8 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: 1.5 s

    1.5 s

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

  • Real-user INP: 164 ms

    164 ms

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

    1.5 s

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

  • Real-user TTFB: 610 ms

    610 ms

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

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

    -44%

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

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

100
  • 2 images in older formats

    2 images (132 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.5 g of CO₂ per visit

    0.53 g

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

3 checks passed
  • Page weight: 1.9 MB in 138 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 138 requests on a phone: scripts 1.3 MB (47), images 309 KiB (52) and HTML 99 KiB (1). That is a lean page.

  • 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

1 to fixGoogle 9798
  • 56 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • Meta description is long (192 characters)

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

  • Structured data has 1 problem

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

  • 126 internal links, 28 external

    The homepage links to 126 pages on close.com and 28 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “The CRM that sells with you”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Close CRM | The CRM That Does the Work”.

  • Canonical URL set

    The canonical URL is https://close.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://close.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 (5,529 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://close.com/llms.txt (41 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187116307&Ver=2&mid=59fe1aa6-45b1-457d-92a1-17775bcc1170&bo=1&sid=730b3cf0e26a11f1b2653773388d5f76&vid=730b6330e26a11f196573fca8b1cdf4b&vids=1&msclkid=N&pi=918639831&l.

  • 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 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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 3,709 words of copy

    The homepage carries about 3,709 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try for free” and “Try Close free”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Pricing”, “Demo” and “Try for free”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 37 customer or partner logos, a star rating, 7 trust badges and “Join 11,500+ businesses”.

  • Analytics in place

    Analytics detected: Amplitude.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 7 of them by other companies (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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 close.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
Astro
Analytics
Segment | Amplitude
Hosting
Vercel

Hiring

Hiring
3 open roles
Teams
Engineering (2), Data (1)
Job board
ashby

Company

Employees
120
Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on close.com, including 14 speed issues, 2 SEO issues and 1 conversion gap. 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