Takealot is a popular South African ecommerce site. They stock a wide range of goods, so they have big Information Architecture challenges. They process of a lot of transactions, so they have big scaling challenges. We’re going to focus on something that we can see and test: the front-end performance of the site.
- Google’s PageSpeedInsight: 53 on mobile and, erm, 5 (!) on desktop
- Webaim’s WAVE: 1 error and 115 alerts
- WebPageTest on 3G, running Motorola G, Chrome: SpeedIndex of 19294 on first view
Here are a few things that stand out as areas for improvement:
- lots of static assets could be cached;
- lots of images could be optimised;
Setting expiry date or maximum age headers for more of the image, CSS, and JS files would mean files get cached by the browser: instead of fetching those files from the web every time, the browser would use the local ones. That means the page would load faster and use less of the user’s data.
Optimising the images would reduce the file sizes. That means the page would load faster and use less of the user’s data.
script tags inside the page itself: these should be moved to external files so that they can be cached, and more maintainable.
Published on Friday 10th June 2016.
Steve Barnett (@maxbarners) and Justin Slack (@justin_r_slack)
CTFEDs Organising Team