Website review, no card needed

Pleo logo

pleo.io website review

Visit site (opens in a new tab)Reviewed 25 October 202626 issues · 80 checks

This review found 26 issues worth fixing on pleo.io, 3 of them high impact, across 80 checks. The most urgent: page weight: 5.9 MB in 106 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Pleo

  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
2.8 s1.2 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.1 s
May 16, 20261.5 s
May 23, 20261.6 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.9 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
429 ms135 msMay 2Oct 17169 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026395 ms
May 9, 2026327 ms
May 16, 2026237 ms
May 23, 2026273 ms
May 30, 2026295 ms
Jun 6, 2026319 ms
Jun 13, 2026355 ms
Jun 20, 2026348 ms
Jun 27, 2026359 ms
Jul 4, 2026330 ms
Jul 11, 2026286 ms
Jul 18, 2026263 ms
Jul 25, 2026233 ms
Aug 1, 2026220 ms
Aug 8, 2026217 ms
Aug 15, 2026212 ms
Aug 22, 2026216 ms
Aug 29, 2026211 ms
Sep 5, 2026217 ms
Sep 12, 2026223 ms
Sep 19, 2026201 ms
Sep 26, 2026189 ms
Oct 3, 2026183 ms
Oct 10, 2026170 ms
Oct 17, 2026169 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 pleo.io (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix80
  • Mobile performance score: 80

    80/100

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

  • Reduce unused JavaScript

    150 ms · 316 KiB

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

  • freshworks.com adds 341 ms

    341 ms

    freshworks.com costs a phone 341 ms of main-thread work and 358 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.

  • Use efficient cache lifetimes

    257 KiB

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

  • Main-thread work: 2.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (freshworks.com, Hubspot and Freshchat and others), adding 687 KiB and 495 ms of main-thread time.

  • 8 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Reduce unused CSS

    45 KiB

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

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

    3 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Clear the runway for financial leadership”.

  • Total Blocking Time: 295 ms

    295 ms

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

  • Speed Index: 3.6 s

    3.6 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 8 images without width and height

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

9 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.4 s

    1.4 s

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

  • Real-user INP: 162 ms

    162 ms

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

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (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: 738 ms

    738 ms

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

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

    -53%

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

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

    -40%

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

  • Cumulative Layout Shift: 0.035

    0.035

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

Images and page weight

1 to fix70
  • Page weight: 5.9 MB in 106 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 106 requests on a phone: media 4.5 MB (2), scripts 1.0 MB (57) and images 160 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (100 KiB) is 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 1.7 g of CO₂ per visit

    1.67 g

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

2 checks passed
  • 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

3 to fixGoogle 9796
  • 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.

  • All page content should be contained by landmarks (30 elements)

    All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 28 internal links, 7 external

    The homepage links to 28 pages on pleo.io and 7 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “The business expenses solution that empowers your people to do more. Join the thousands of companies that trust Pleo to…”.

  • One H1 headline

    Your main headline reads: “Clear the runway for financial leadership”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Smarter spending for your business - Pleo”.

  • Canonical URL set

    The canonical URL is https://www.pleo.io/us.

  • 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.pleo.io/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.

3 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 (547 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.pleo.io/llms.txt (16 KiB, 95 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 4 pages share a title

    https://www.pleo.io/us, https://www.pleo.io/us/home-s, https://www.pleo.io/us/home-l and https://www.pleo.io/en/multi-currency all use the title “Smarter spending for your business - Pleo”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.pleo.io/us/pricing, https://www.pleo.io/us/home-s, https://www.pleo.io/us/home-l, https://www.pleo.io/us/artificial-intelligence and https://www.pleo.io/en/multi-currency use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.pleo.io/us/getting-started, whose canonical is https://www.pleo.io/us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.pleo.io/us/pricing and https://www.pleo.io/en/multi-currency have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.pleo.io/us/getting-started 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 16 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 502 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: “Get started”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Pricing” and “Get started”.

  • Social proof on the page

    Social proof on the homepage: 1 trust badge and “Trusted by 40,000+ companies”.

  • Analytics in place

    Analytics detected: HubSpot.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 4 cookies set on arrival

    4

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

  • 13 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 pleo.io, 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
Hosting
AWS

Hiring

Hiring
33 open roles
Teams
Commercial (9), Customer Experience (4), Revenue Operations (4), SDR (4)
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 26 issues on pleo.io, including 11 speed issues, 1 SEO issue and 3 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