Performance

Overview

Affirm is continually working on ensuring all of our services are as performant as possible. This FAQ addresses some common questions about how the following services may affect your site:

• Collect calls.
• Script loading & Affirm.js.
• Affirm assets & "as low as" messaging.
• Loan application process.

FAQs

Why are there so many collect calls made to Affirm in the browser network tools? What do those do?

Collect calls are used to monitor performance and events that help Affirm function effectively. Some examples to help optimize the experience are browser/device info, "as low as" messaging, the URL of the page Affirm is on, and the Affirm.js version.

Is having Affirm on my site affecting my site’s performance?

All of the requests/calls to Affirm are fired with minimal blocking of the browser’s main thread before the user selects an element rendered by Affirm. This minimizes the impact that Affirm has on websites.

Is Affirm blocking other things on my page from loading?

No, many of our requests happen after the page (DOM-content) has been loaded.

Can I expect to increase compute power for Affirm?

The Affirm.js script loaded on your site has a minimal effect on the resources needed to power it. The Affirm.js package itself is very small and the resources it uses are proportional to how many Affirm components you have on your site.

Your promotional messaging takes too long to load, are there any ways I can make it load faster?

Our Promo JS API should help improve the latency of our promotional messaging. While the DOM content loads, create the components and once it is loaded, render the components.