Michael Aigner und Mike Schäkermann, beide Mitbegründer von stilnest.com, zeigen Best Practices, wie sie die Magento-Performance ihrer Website aus Nutzersicht erfolgreich optimiert haben und damit die Umsätze deutlich steigern konnten. Das zugehörige Webinar finden Sie hier: http://ow.ly/OPDif
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
Stilnest.com: Wie beste Magento-Shop-Performance für zufriedene Kunden sorgt
1. 1 #Dynatrace
Stilnest.com
Wie beste Magento-Shop Performance für zufriedene
Kunden sorgt.
Harald Zeitlhofer
Technology Strategist
Dynatrace
Michael Aigner
COO
Stilnest.com
Mike Schäkermann
Head of IT
Stilnest.com
13. Stilnest IT-Team
Michael Aigner
COO & Co-Founder
BSc Mobile Computing & MA Coporate Management & Economics
Before 1.5 years IT-Consultant for CSC in New York
Responsible for IT & Production
Mike Schäkermann
Head of IT & Co-Founder
BSc Multimedia Technology
Responsible for the Development & Hosting of the Stilnest Shop
15. PERFORMANCE THREATENS GOALS
In November 2014 we had a problem.
We discovered that our Magento Shop was
actually pretty slow!
So what do you do in that situation?
→ Our infrastructure was very limited at that
time, so let’s change that (WRONG!)
→ Don’t we know someone who works at that
performance company?
→ It turns out that in fact we had problems with
our code and with Magento!
16. PERFORMANCE THREATENS GOALS
Within the first session with Harald we discovered the first
major problems:
→ lessc CSS pre-processor
→ Social Login Module
→ PHP execution was really slow
22. After updating to PHP 5.5
PHP compilation time could
be reduced considerably just
by using PHP 5.5 + Opcache!
23. PERFORMANCE THREATENS GOALS
One directly business-relevant issue:
A seemingly harmless layout change
slowed down our page considerably!
What had happened?
We had added a small information to our
product listings: the available stock quantity
of each item in the list
Analysis: drill-down of using Dynatrace and
sensors to measure method-level performance
Problem: the PHP method to calculate the stock
quantity was extremely inefficient
Solution: pre-calculation of stock quantity values
and caching of those in the database + caching
of database results in private member variables
Consequences for our workflow?
24. STATUS QUO
Our infrastructure changed a lot since the
beginning.
We are thoroughly monitoring every change
that goes live and included performance
monitoring in our development & review
process.
Our website evolved over time, but we see a
clear correlation between our website
performance and our conversion rate.