A Magento checkout with superior performance
A high conversion can only be accomplished if the checkout is performant. This is why we have aimed for the Loki Checkout to be the fastest Magento checkout on the market. And so far, the numbers show that this goal has been accomplished.
Conversion means performance
To increase conversion, the base rule is to increase performance first. Without a good performance, all other work is pointless. The Loki Checkout gives you the best performance, so the best way to increase conversion levels.
Fast page loads
The Loki Checkout loads quickly. This creates a more trustworthy buying experience. A fast checkout feels reliable and secure at the most critical stage of the customer journey.
Less loaders
The Loki technology causes page updates to be near-instant, removing the requirement for loaders in a lot of areas. Few loaders means less friction with the UI.
Happier user experience
Less loaders cause less friction. A faster UI makes the whole experience for a shopper better. The end result is a happier customer. Money in your pocket.
Comparison with all checkouts
The fastest initial page load.
When loading the Loki Checkout, the number of resources are minimal. We only require Alpine.js and a bunch of inline JavaScript. This makes it fast. Faster than any Magento Luma checkout. And even faster than the Hyvä Checkout, which requires an additional Magewire library.
Superb Lighthouse scores
Thanks to the fact that only Alpine.js is required, the Loki Checkout leads to high performance scores. For instance, we run regular checks upon our demo sites, to make sure that their Lighthouse scores are 100. Not because 100 is a number to be taken literally, but because this serves as a smoke test which tells us that if it drops, something needs to be fixed regarding performance.
One single AJAX request
The Loki Component technology is developed to optimize AJAX calls. Whenever you change a field value, an AJAX request is triggered which saves the change in the quote and updates all page elements where needed. If multiple fields change, it still is only 1 single AJAX request. When using autofill (which might change a dozen fields), it still remains 1 request.
Lazy loading fields
Not all fields need immediate updating. For instance, a street address requires fast updates, because it might influence shipping and payment. However, a firstname or lastname can be saved later. Each field (or actually every single Loki Component) allows for a simple configuration to enable lazy loading. They are saved when the first next AJAX request is sent.
Skip the queue when needed
Some component updates might be so heavy that bundling them with other component updates might cause issues. For instance, imagine autofill entering a shipping address while also a shipping method is selected, while that shipping method connects to an API that is dead-slow. The answer: Skip the queue for that shipping method. Again, a simple configuration change.