Website review, no card needed

37signals.com logo

37signals.com website review

Visit site (opens in a new tab)Reviewed 20 October 202615 issues · 65 checks

This review found 15 issues worth fixing on 37signals.com, 2 of them high impact, across 65 checks. The most urgent: 76 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

Real-visitor load time (LCP)75th percentile, phones
481 ms402 msMay 2Oct 17445 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026431 ms
May 9, 2026455 ms
May 16, 2026468 ms
May 23, 2026458 ms
May 30, 2026452 ms
Jun 6, 2026450 ms
Jun 13, 2026440 ms
Jun 20, 2026465 ms
Jun 27, 2026472 ms
Jul 4, 2026472 ms
Jul 11, 2026461 ms
Jul 18, 2026449 ms
Jul 25, 2026449 ms
Aug 1, 2026423 ms
Aug 8, 2026438 ms
Aug 15, 2026431 ms
Aug 22, 2026416 ms
Aug 29, 2026423 ms
Sep 5, 2026416 ms
Sep 12, 2026412 ms
Sep 19, 2026411 ms
Sep 26, 2026412 ms
Oct 3, 2026412 ms
Oct 10, 2026423 ms
Oct 17, 2026445 ms
Real-visitor tap response (INP)75th percentile, phones
33 ms23 msMay 2Oct 1728 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202625 ms
May 9, 202626 ms
May 16, 202626 ms
May 23, 202626 ms
May 30, 202626 ms
Jun 6, 202627 ms
Jun 13, 202626 ms
Jun 20, 202628 ms
Jun 27, 202632 ms
Jul 4, 202628 ms
Jul 11, 202628 ms
Jul 18, 202628 ms
Jul 25, 202626 ms
Aug 1, 202625 ms
Aug 8, 202625 ms
Aug 15, 202625 ms
Aug 22, 202626 ms
Aug 29, 202627 ms
Sep 5, 202626 ms
Sep 12, 202625 ms
Sep 19, 202624 ms
Sep 26, 202625 ms
Oct 3, 202625 ms
Oct 10, 202626 ms
Oct 17, 202628 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 37signals.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix100
  • Use efficient cache lifetimes

    750 ms · 133 KiB

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

  • Render-blocking requests

    750 ms

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

3 checks passed
  • Mobile performance score: 100

    100/100

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

  • Main-thread work: 0.1 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

1 to fix100
  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 25 ms to 28 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-10-17, real Chrome visitors' largest content (lcp) went from 0.4 s to 0.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

12 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.6 s

    0.6 s

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

  • Real-user INP: 36 ms

    36 ms

    Real visitors wait 36 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.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: 438 ms

    438 ms

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

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

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Two tokens of customer service”.

  • Speed Index: 0.9 s

    0.9 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.5 s

    1.5 s

    The page is fully interactive after 1.5 s.

Images and page weight

100
  • About 0.04 g of CO₂ per visit

    0.04 g

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

4 checks passed
  • Page weight: 138 KiB in 35 requests

    138 KiB

    Your homepage downloads 138 KiB in 35 requests on a phone: fonts 100 KiB (2), stylesheets 19 KiB (22) and scripts 9 KiB (7). That is a lean page.

  • 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

1 to fixGoogle 10097
  • 76 text elements with low contrast

    76 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 2 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

6 to fixGoogle 10071
  • Title is short (9 characters)

    Your title is only 9 characters: “37signals”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (45 characters)

    Your meta description is only 45 characters: “A catalog of ideas — signals — that drive us.”. 70 to 160 characters is enough to sell the click.

  • Structured data has 2 problems

    Structured data found (Article, Organization and WebSite) but with 2 problems, for example “Article: missing datePublished”.

  • No XML sitemap

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

  • No robots.txt

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

  • One H1 headline

    Your <h1> is empty.

  • 54 internal links, 16 external

    The homepage links to 54 pages on 37signals.com and 16 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://37signals.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://37signals.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (178 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page with very little text

    https://37signals.com/policies 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 43 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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 150 words

    The homepage has only about 150 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “00. Start here” and “Next Signal: Start here”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “00. Start here” and “Next Signal: Start here”.

Privacy and tracking

  • 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 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 37signals.com, 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 15 issues on 37signals.com, including 3 speed issues, 6 SEO 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