Website review, no card needed

Paragon logo

useparagon.com website review

Visit site (opens in a new tab)Reviewed 20 October 202627 issues · 78 checks

This review found 27 issues worth fixing on useparagon.com, 6 of them high impact, across 78 checks. The most urgent: framerusercontent.com adds 1.0 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Paragon

  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
3.2 s2.0 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.3 s
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.1 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.6 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
339 ms66 msMay 2Oct 17158 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026108 ms
May 9, 202697 ms
May 16, 2026124 ms
May 23, 2026169 ms
May 30, 2026221 ms
Jun 6, 2026244 ms
Jun 13, 2026234 ms
Jun 20, 2026243 ms
Jun 27, 2026226 ms
Jul 4, 2026261 ms
Jul 11, 2026289 ms
Jul 18, 2026306 ms
Jul 25, 2026307 ms
Aug 1, 2026283 ms
Aug 8, 2026269 ms
Aug 15, 2026246 ms
Aug 22, 2026236 ms
Aug 29, 2026169 ms
Sep 5, 2026145 ms
Sep 12, 2026154 ms
Sep 19, 2026160 ms
Sep 26, 2026170 ms
Oct 3, 2026197 ms
Oct 10, 2026192 ms
Oct 17, 2026158 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 useparagon.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. useparagon.com at 0.7 s0.7 s
  2. useparagon.com at 1.3 s1.3 s
  3. useparagon.com at 2.0 s2.0 s
  4. useparagon.com at 2.6 s2.6 s
  5. useparagon.com at 3.3 s3.3 s
  6. useparagon.com at 4.0 s4.0 s
  7. useparagon.com at 4.6 s4.6 s
  8. useparagon.com at 5.3 s5.3 s

Speed

11 to fix59
  • framerusercontent.com adds 1.0 s

    1.0 s

    framerusercontent.com costs a phone 1.0 s of main-thread work and 2.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 4,267 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (framerusercontent.com, Cookiebot and framer.com and others), adding 3.3 MB and 1.3 s of main-thread time.

  • Improve image delivery

    150 ms · 900 KiB

    12 images could be 900 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.

  • Mobile performance score: 59

    59/100

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

  • Reduce unused JavaScript

    750 ms · 187 KiB

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

  • Use efficient cache lifetimes

    450 ms · 61 KiB

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

  • Main-thread work: 3.4 s

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Cookiebot adds 277 ms

    277 ms

    Cookiebot costs a phone 277 ms of main-thread work and 158 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.

  • Unpkg adds 0 ms

    0 ms

    Unpkg costs a phone 0 ms of main-thread work and 632 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.

  • 9 long tasks on the main thread

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

  • 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: 86 ms

    86 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.0 s

    9.0 s

    Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Connect your agent to customer data and tools. Keep the upk…”.

  • Time to Interactive: 10.6 s

    10.6 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

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

    +71%

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Total Blocking Time: 327 ms

    327 ms

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

  • Largest content (LCP) held steady for real visitors

    0%

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

7 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.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: 184 ms

    184 ms

    Real visitors wait 184 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: 756 ms

    756 ms

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

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 150 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 150 requests on a phone: images 1.3 MB (45), scripts 1.1 MB (52) and other files 735 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (207 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

2 checks passed
  • 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 9396
  • All page content should be contained by landmarks (76 elements)

    All page content should be contained by landmarks: 76 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.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 143 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • 21 links crawlers can't follow

    21 links have no real href, so search engines can't follow them.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 128 internal links, 57 external

    The homepage links to 128 pages on useparagon.com and 57 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Integration infrastructure for AI agents and SaaS products. Connect to the tools your customers use for tool-calling an…”.

  • One H1 headline

    Your main headline reads: “Connect your agent to customer data and tools. Keep the upkeep off your roadmap.”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Paragon — Integration platform for AI agents and products”.

  • Canonical URL set

    The canonical URL is https://www.useparagon.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.useparagon.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.useparagon.com/llms.txt (6 KiB, 44 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.useparagon.com/actionkit has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 9691
  • 3 small tap targets

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

1 to fix80
  • 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 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 671 words of copy

    The homepage carries about 671 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a demo”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Pricing”, “Start for free” and “Book a demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Segment.

  • Direct contact links

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

Privacy and tracking

  • 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

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

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 useparagon.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
Framer
Analytics
Google Analytics | Google Tag Manager | Segment

Hiring

Hiring
1 open role
Teams
Sales (1)
Job board
ashby

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on useparagon.com, including 17 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