Website review, no card needed

youlend.com logo

youlend.com website review

Visit site (opens in a new tab)Reviewed 27 October 202627 issues · 79 checks

This review found 27 issues worth fixing on youlend.com, 12 of them high impact, across 79 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
5.3 s4.2 sMay 9Oct 245.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.8 s
May 16, 20264.8 s
May 23, 20264.8 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.8 s
Jun 20, 20264.8 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.7 s
Jul 25, 20264.6 s
Aug 1, 20264.4 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.3 s
Aug 29, 20264.3 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.5 s
Sep 26, 20264.6 s
Oct 3, 20264.7 s
Oct 10, 20264.9 s
Oct 17, 20265.1 s
Oct 24, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
158 ms135 msMay 9Oct 24138 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026146 ms
May 23, 2026146 ms
May 30, 2026146 ms
Jun 6, 2026147 ms
Jun 13, 2026147 ms
Jun 20, 2026149 ms
Jun 27, 2026151 ms
Jul 4, 2026153 ms
Jul 11, 2026155 ms
Jul 18, 2026155 ms
Jul 25, 2026155 ms
Aug 1, 2026155 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026153 ms
Aug 29, 2026147 ms
Sep 5, 2026145 ms
Sep 12, 2026144 ms
Sep 19, 2026144 ms
Sep 26, 2026145 ms
Oct 3, 2026144 ms
Oct 10, 2026143 ms
Oct 17, 2026143 ms
Oct 24, 2026138 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 youlend.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. youlend.com at 0.7 s0.7 s
  2. youlend.com at 1.3 s1.3 s
  3. youlend.com at 2.0 s2.0 s
  4. youlend.com at 2.6 s2.6 s
  5. youlend.com at 3.3 s3.3 s
  6. youlend.com at 3.9 s3.9 s
  7. youlend.com at 4.6 s4.6 s
  8. youlend.com at 5.2 s5.2 s

Speed

11 to fix46
  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    1.1 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 2.2 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 (Hubspot, website-files.com and Intercom and others), adding 2.1 MB and 1.8 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 891 KiB

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

  • Hubspot adds 622 ms

    622 ms

    Hubspot costs a phone 622 ms of main-thread work and 808 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.

  • 16 long tasks on the main thread

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

  • website-files.com adds 342 ms

    342 ms

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

  • Intercom adds 272 ms

    272 ms

    Intercom costs a phone 272 ms of main-thread work and 235 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.

  • 1,812 HTML elements

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

  • Improve image delivery

    150 ms · 96 KiB

    4 images could be 96 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.

  • Reduce unused CSS

    69 KiB

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

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 134 ms

    134 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 18.6 s

    18.6 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 5.1 s

    5.1 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Total Blocking Time: 744 ms

    744 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.8 s to 5.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: 2.0 s

    2.0 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.1 s

    1.1 s

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

  • Real-user TTFB: 488 ms

    488 ms

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

  • Cumulative Layout Shift: 0.084

    0.084

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

Images and page weight

1 to fix70
  • Page weight: 4.9 MB in 115 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 115 requests on a phone: media 2.2 MB (1), scripts 1.9 MB (30) and images 313 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.39 g

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

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

2 to fixGoogle 9397
  • 5 text elements with low contrast

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

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 178 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 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“Flexible financing, integrated directly into your…” and “Heading 1”). One clear main headline is easier for people and search engines.

  • 5 links with vague text

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

  • 85 internal links, 11 external

    The homepage links to 85 pages on youlend.com and 11 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Flexible financing integrated directly into your platform. Our embedded financing solutions can be live on your platfor…”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “YouLend | Global Embedded Financing Platform”.

  • Canonical URL set

    The canonical URL is https://youlend.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://youlend.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix67
  • 1 linked page is broken

    Your homepage links to https://youlend.com/products/spend, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://youlend.com/resources-overview is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a meta description

    https://youlend.com/use-cases/e-commerce-and-tech and https://youlend.com/use-cases/software use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 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.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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 2,124 words of copy

    The homepage carries about 2,124 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: “Apply for funding”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Apply for funding” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 155 testimonial or review blocks, 58 customer or partner logos and “400,000+ businesses”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

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

  • 8 cookies set on arrival

    8

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

  • 28 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 youlend.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
Framework
Bootstrap
Analytics
Google Tag Manager
Hosting
AWS

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