A web application or website that interacts with the user by dynamically rewriting the current web page with new data from the webserver, instead of the default method of a web browser loading entire new pages. – Wikipedia
Relevance in CRO
SPAs present new challenges and difficulties to overcome for folks running experimentation programs. Page loads are gone, which are a backbone triggering mechanism of traditional analytics tools. No page loads means that all the analytics scripts and testing tools installed on your site get loaded once and then just sit there not doing anything after their initialization. No more tracking pageviews, triggering an experiment based on URL, etc. Well… that’s not entirely true. You just have to do those things in a different way. With an SPA everything becomes event-based, so it adds additional development overhead. Clicking a link doesn’t actually load a new page, instead it fires a “virtual pageview” event, which is what you hook into for analytics tracking or experiment triggers instead.
SPAs are a new(ish) web development process that comes with its own set of pros and cons. Many of the popular testing platforms have updated their platforms to deal with test execution on SPAs, but not all. It’s definitely something you need to consider when evaluating making changes to your tech stack.« Back to Glossary Index