Website review, no card needed

intakeq.com logo

intakeq.com website review

Visit site (opens in a new tab)Reviewed 11 October 202625 issues · 77 checks

This review found 25 issues worth fixing on intakeq.com, 6 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
1.9 s1.5 sApr 18Oct 31.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.9 s
Apr 25, 20261.9 s
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
168 ms67 msApr 18Oct 3111 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026151 ms
Apr 25, 2026154 ms
May 2, 2026152 ms
May 9, 2026154 ms
May 16, 2026156 ms
May 23, 2026156 ms
May 30, 2026154 ms
Jun 6, 2026145 ms
Jun 13, 2026137 ms
Jun 20, 2026126 ms
Jun 27, 2026118 ms
Jul 4, 2026111 ms
Jul 11, 202695 ms
Jul 18, 202681 ms
Jul 25, 202682 ms
Aug 1, 202680 ms
Aug 8, 202680 ms
Aug 15, 202680 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202680 ms
Sep 19, 202689 ms
Sep 26, 2026103 ms
Oct 3, 2026111 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 intakeq.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix73
  • Render-blocking requests

    1.3 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • Mobile performance score: 73

    73/100

    Your mobile performance score is 73 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 79 KiB

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

  • Use efficient cache lifetimes

    300 ms · 43 KiB

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

  • website-files.com adds 72 ms

    72 ms

    website-files.com costs a phone 72 ms of main-thread work and 433 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cookiebot, website-files.com and intellimize.co and others), adding 746 KiB and 265 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.

  • Improve image delivery

    30 KiB

    1 image could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 357 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

5 to fix100
  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Woman with tablet and form UI illustrations”.

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • 35 images without width and height

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • Speed Index: 3.5 s

    3.5 s

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

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

    1.6 s

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

  • Real-user INP: 118 ms

    118 ms

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

    1.6 s

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

  • Real-user TTFB: 660 ms

    660 ms

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

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

    -30%

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

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

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 11 ms

    11 ms

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    67e04d0c8190f3391310ec49_home-mobile-p-500.avif 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).

  • About 0.2 g of CO₂ per visit

    0.21 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 25.3 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: 761 KiB in 31 requests

    761 KiB

    Your homepage downloads 761 KiB in 31 requests on a phone: scripts 434 KiB (13), fonts 162 KiB (1) and images 123 KiB (9). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9696
  • 4 text elements with low contrast

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

3 to fixGoogle 9279
  • No meta description

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

  • Title is short (7 characters)

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

  • No structured data

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

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 44 internal links, 11 external

    The homepage links to 44 pages on intakeq.com and 11 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Easiest HIPAA Compliant form builder”.

  • Canonical URL set

    The canonical URL is https://forms.intakeq.com/.

  • 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://forms.intakeq.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://forms.intakeq.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.

  • Text is in the HTML

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

Other pages

5 to fix67
  • 1 page without a title

    https://forms.intakeq.com/features/ai-forms has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://forms.intakeq.com/features/customizable-online-forms and https://forms.intakeq.com/features/hipaa-compliant-forms all use the title “HIPAA Compliant Online Forms | Secure Client Intake”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://forms.intakeq.com/features/ai-forms has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://forms.intakeq.com/features/customizable-online-forms and https://forms.intakeq.com/features/hipaa-compliant-forms use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://forms.intakeq.com/features/ai-forms has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://forms.intakeq.com/start-a-free-trial-lander 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 25 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

  • About 397 words of copy

    The homepage carries about 397 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start free trial” and “View Pricing”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Start free trial”, “Pricing” and “Get a demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • 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 intakeq.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on intakeq.com, including 10 speed issues, 3 SEO issues and 2 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