How Tamaris makes +2% more revenue with Speed Kit

Tamaris is a renowned German footwear and accessories brand with a rich heritage dating back to 1919. As a subsidiary of the Wortmann Group, headquartered in Detmold, Germany, the brand has established itself as a prominent player in the European fashion footwear market.

The company specializes in designing and manufacturing women's shoes, handbags, and fashion accessories that balance contemporary style, comfort, and affordability. Tamaris targets fashion-conscious women who seek trendy yet practical footwear for various occasions - from casual daily wear to more elegant evening events.

Experienced in ecommerce, Tamaris is aware of the positive impact page speed can have on the user experience, organic search rankings, and conversion rates. To leverage these positive effects of page speed, Tamaris searched for ways to enhance their web performance.

Tamaris decided to implement Speed Kit to enhance their web performance. After the integration into their Salesforce Commerce Cloud System, Tamaris was able to leverage the innovative caching algorithms and service worker technology of Speed Kit. The solution makes it possible to cache even dynamic HTML resources. Through Speed Kit, Tamaris was not only able to increase their performance metrics like the Largest Contentful Paint (LCP) or the Time to First Byte (TTFB), it also had a significant impact on their business metrics.

Speed Kit is an official ACE eligible technology partner and independent software vendor (advanced tier) of the AWS Competency Partner Program "Accelerate" as well as the Workload Migration Program. Our technology is powered by 13 different AWS services:

• Elastic Kubernetes Service (EKS): We use EKS to schedule and orchestrate our Speed Kit applications on EC2 instances.
• Simple Storage Service (S3): Speed Kit stores cached assets in S3 buckets. Additionally, we store RUM (Real User Monitoring) and PI (Performance Insights) data in S3 buckets for analytics purposes.
• Elastic Compute Cloud (EC2): Our workloads are hosted on EC2 instances, as managed through EKS.
• Kinesis Data Streams: Kinesis Data Streams are used to ingest RUM and PI data from Speed Kit, which is then consumed by Amazon Managed Service for Apache Flink. Fastly also streams access logs to our Kinesis Data Stream, which are similarly consumed by Amazon Managed Service for Apache Flink.
• Athena: We use Amazon Athena to query data stored in AWS S3 buckets, enabling performance insights and asset preloading.
• Elastic Container Registry (ECR): Docker images are stored in ECR and deployed in our Kubernetes cluster, which is managed by EKS. For third-party application images, we use the pull-through-cache feature of ECR.
• Elastic Container Service (ECS): We build Docker images using a service hosted on Amazon ECS.
• Route 53: Route53 is used to manage DNS records.
• Simple Email Service (SES): We use SES is used for sending transactional emails.
• Managed Streaming for Apache Kafka (MSK): We use MSK to facilitate consuming and producing custom event records for different applications.
• DynamoDB: Speed Kit uses DynamoDB to store information related to our predictive preload feature.
• Lambda: We use Lambda to pre-render client side renderd pages to make that actual server side rendered.
• ElastiCache (Redis OSS): We use ElastiCache to store our Bloom filter, which checks whether an asset is present in our cache.
  ‍

Click the image to open the architectual diagram of Speed Kit with AWS

Through an A/B test based on real-user monitoring (RUM) data and conversion data by Tamaris, the performance and business uplift through Speed Kit was proven with statistical significance.

‍

Largest Contentful Paint (LCP):

‍

On the performance side, the median value of the Largest Contentful Paint (LCP) on desktop decreased from 2359 ms to 1447 ms, while on mobile it decreased from 3335 ms to 1935 ms.

‍

Time to First Byte (TTFB):

‍

Furthermore, the median value for Time to First Byte (TTFB) on desktop improved from 727 ms to 466 ms, while on mobile it decreased from 831 ms to 539 ms. On the business side, the increase in page speed has led to a 3% increase in conversions per user, a 2% improvement in revenue per user, and a 2% growth in total revenue.