affirm.com website review

About 796 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

Google Tag Manager costs a phone 1.6 s of main-thread work and 1.1 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, Optanon and Cloudflare and others), adding 4.2 MB and 1.7 s of main-thread time.

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

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

ctfassets.net costs a phone 0 ms of main-thread work and 2.8 MB 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 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

For real visitors the layout shifts by 1.42 (75th percentile). Good is under 0.1.

Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Flexible plans for every purchase”.

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

The layout shifts by 1.1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

Your homepage downloads 6.8 MB in 89 requests on a phone: media 2.7 MB (1), scripts 2.0 MB (26) and other files 1.6 MB (32). Under 2 MB keeps phones on slow connections fast.

1 image (37 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.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 69 pages on affirm.com and 12 external pages.

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.

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

/business, /how-it-works, /card, /how-it-works/why-affirm, /download and /shopping/browser-extension and 9 others have no <title>, so Google invents the link text in results.

/shopping/browser-extension is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/wallet/where-you-can-pay has no meta description, so Google writes the search snippet from whatever text it finds.

/business, /how-it-works, /card, /how-it-works/why-affirm, /download and /shopping/browser-extension and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://www.affirm.com/help/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

affirm.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

affirm.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 591 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.

Opening the homepage sets 27 cookies, 3 of them by other companies (measured from a US location before any click).

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