Programmable

Website review, no card needed

Plaud logo

plaud.ai website review

Visit site (opens in a new tab)Reviewed 4 November 202619 issues · 78 checks

This review found 19 issues worth fixing on plaud.ai, 7 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Plaud

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

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

Site score

87B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.1 s1.7 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
489 ms258 msMay 16Oct 31285 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026433 ms
May 23, 2026424 ms
May 30, 2026430 ms
Jun 6, 2026432 ms
Jun 13, 2026443 ms
Jun 20, 2026453 ms
Jun 27, 2026453 ms
Jul 4, 2026448 ms
Jul 11, 2026450 ms
Jul 18, 2026453 ms
Jul 25, 2026438 ms
Aug 1, 2026462 ms
Aug 8, 2026449 ms
Aug 15, 2026416 ms
Aug 22, 2026392 ms
Aug 29, 2026357 ms
Sep 5, 2026342 ms
Sep 12, 2026340 ms
Sep 19, 2026337 ms
Sep 26, 2026336 ms
Oct 3, 2026337 ms
Oct 10, 2026337 ms
Oct 17, 2026347 ms
Oct 24, 2026321 ms
Oct 31, 2026285 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

www.plaud.ai (opens in a new tab)
Full-page screenshot of plaud.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix73

  • Render-blocking requests

    1.1 s

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

  • 3,380 HTML elements

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

  • Mobile performance score: 73

    73/100

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

  • Use efficient cache lifetimes

    550 ms · 109 KiB

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

  • Improve image delivery

    120 KiB

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

  • 1 long task on the main thread

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

  • Reduce unused CSS

    41 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, cdnfonts.com and shopifycdn.net and others), adding 228 KiB and 1 ms of main-thread time.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

2 checks passed

  • Main-thread work: 0.8 s

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

  • Server response: 19 ms

    19 ms

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

Core Web Vitals

5 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: 7.0 s

    7.0 s

    Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Plaud homepage banner”.

  • Real-user INP: 257 ms

    257 ms

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

  • Time to Interactive: 7.0 s

    7.0 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

9 checks passed

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

    1.3 s

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

  • Real-user TTFB: 502 ms

    502 ms

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

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

    -29%

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

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

    -11%

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

  • Speed Index: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 5 ms

    5 ms

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

Images and page weight

3 to fix65

  • 1 image over 500 KB

    Note-pro-081716-MB.webp weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (2.7 MB) 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.

  • 4 images far larger than shown

    430 KiB

    4 images are downloaded at several times the size a phone draws them, for example Note-pro-081716-MB.webp at 1,200 px wide, shown at 350 px. Resized copies would save about 430 KiB.

  • 1 image below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.49 g

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

1 checks passed

  • Page weight: 1.7 MB in 133 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 133 requests on a phone: images 756 KiB (33), scripts 594 KiB (54) and HTML 204 KiB (1). That is a lean page.

Accessibility

4 to fixGoogle 9495

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

  • ARIA role should be appropriate for the element (10 elements)

    ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.

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

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

2 checks passed

  • Every image has alt text

    All 267 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298

  • 13 links with vague text

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

  • 218 internal links, 43 external

    The homepage links to 218 pages on plaud.ai and 43 external pages.

8 checks passed

  • Meta description: 160 characters

    Your meta description is 160 characters: “The only AI note-taking platform that bridges in-person, phone calls, and online meetings into one workflow, trusted by…”.

  • One H1 headline

    Your main headline reads: “Plaud.ai - The World's No.1 AI Note-taking Brand”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Plaud.ai - The World's No.1 AI Note-taking Brand”.

  • Canonical URL set

    The canonical URL is https://www.plaud.ai/.

  • Structured data in place

    Structured data found: ItemList, Organization and WebSite.

  • 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.plaud.ai/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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95

  • 15 pages without an H1

    https://www.plaud.ai/pages/plaud-note-free-magnetic-case, https://www.plaud.ai/pages/shop-plaud, https://www.plaud.ai/pages/why-plaud, https://www.plaud.ai/pages/plaud-device-comparison, https://www.plaud.ai/pages/bulk-order and https://www.plaud.ai/pages/plaud-note-pro and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.plaud.ai/products/plaud-note-pro, https://www.plaud.ai/products/plaud-notepro-unlimited-plan, https://www.plaud.ai/products/plaud-notepro-pro-plan, https://www.plaud.ai/products/plaud-one, https://www.plaud.ai/products/plaud-note-ai-voice-recorder and https://www.plaud.ai/products/plaud-note-unlimited-plan and 1 other have 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 74 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

1 to fixGoogle 10093

  • 14 small tap targets

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

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

100

  • 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 975 words of copy

    The homepage carries about 975 words of visible text.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Plaud”.

  • 45 calls to action

    The homepage has 45 calls to action, for example “Plaud OnePre-order”, “Bulk Order” and “Learn More”.

  • 4 short forms

    4 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: 147 testimonial or review blocks, 6 customer or partner logos, a star rating, 10 trust badges and “2,000+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 11 other companies contacted

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

1 checks passed

  • Consent tool: consentmanager

    A consent management tool (consentmanager) 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 plaud.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
47 open roles
Teams
Global Product R&D Center (12), Global Brand Center (8), User Ops and Growth (5), Algorithms & Platform R&D (4)
Job board
ashby
Careers page
jobs.ashbyhq.com/plaud (opens in a new tab)

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on plaud.ai, including 9 speed issues and 1 SEO issue. 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