As a continuation of the Magento Performance tests epic, we will test the performance of the Magento Cloud (Adobe Commerce Cloud) Lafayette 148 New York website. I have found this Sucess Story on the Adobe official website:
Adobe Lafayette 148 Sucess Story
In the wake of the pandemic, Lafayette 148 needed to put some long-term plans into action — and develop additional revenue streams. In June of 2020 they quickly announced plans to launch a new division of the business called AtelierDirect. The company enlisted a group of select stylists and brand ambassadors in key markets around the country to offer a new, private selling and styling service to clients craving a more curated, intimate shopping experience.
AtelierDirect was built with the help of Adobe Commerce, which enabled Lafayette 148 to create a portal — or “shadow website” — where its AtelierDirect stylists could conduct direct sales in real time at the customer’s home or office.
“What was really exciting is that we were able to leverage the solution to turn AtelierDirect into a reality within just a matter of weeks,” said Schuster. “And it’s just been incredible. It has made up the difference in term of losses when the retail stores were closed at the height of the pandemic.”
AtelierDirect’s stylists work with clients one-on-one, pulling a selection of items based on their size, lifestyle, and preferences, all of which are gleaned from customer data the company has accumulated over the years. Stylists can look up the purchase histories of customers to offer personalized suggestions, such as how to pair new pieces of clothing with their existing wardrobe.
AtelierDirect clients can make an appointment for the stylist to visit them at home or in the office. They can also visit the Lafayette 148 AD SoHo Studio in New York City. The service lets Lafayette 148 customers shop for clothing in the environment most comfortable for them. Currently, the company offers the service in 25 markets, and plans to expand in 2021.
Performance Result Category page:
Lafayette 148 has an elementary category page with 9 products.
Let's check how Magento 2 can handle a rendering of 9 products …
For the analysis, we will use the K6 performance tooling with the custom script for Magento.
The main metrics we need are:
http_req_waiting — Time spent waiting for a response from the remote host (a.k.a. time to first byte or TTFB).
Concurrent requests or Virtual Users — Virtual Users, or VUs are used to perform separate and concurrent executions of your test script. They can make HTTP(s) and WebSocket requests against a webpage or API.
Virtual Users, although emulated by k6 itself, can be used to mimic the behavior of a real user.
A single request
Result: 1.82 sec a single page response time…
I’m shocked how it is possible to 1820 ms per page with an average time of 1520 ms with the page with 9 products. Google recommendation for TTFB is 300ms. It is 6 times slower than Oracle Magento Commerce Cloud for 600$ per month. Lafayette 148 cloud host has cost more than $20K per month.
In this episode we compared Lafayette 148 Magento Cloud website with Oracle Magento Cloud:
Oracle Magento 2 Cloud on ARM instance Performance.
Let’s test the Oracle Cloud ARM Amper server performance with Magento 2 and compare it with the Adobe Commerce Cloud…
Let’s test Lafayette 148 Adobe Cloud website under the load.
10 concurrent requests
Result: 2 sec
20 concurrent requests :
Result: 3.3 sec almost doubles response time
Result: 4.14 sec
Result: 6.15 sec
Result: 7.63 seconds page response time
Adobe Commerce Product Page Performance:
Result: 2.31 sec
Result: 2.65 sec
Result: 4.07 sec
Result: 6.53 sec
Result: 7.37 sec
Result: 12.99 sec
I have never seen good implementation on Magento Adobe Cloud. We all understand that Adobe was deceived when they bought Magento Cloud. Still, it is not an excuse to sell broken cloud/eCommerce solutions harmful for the eCommerce businesses and continue to mislead. We all understand AEM is a good product, but it is not an apology not to fix Magento 2 and Commerce Cloud.
We all trusted in Adobe that Photoshop Creators could fix the broken Magento 2, but that wouldn’t happen….