Tes engineering blog

Before introducing async-define, I’d like to give some context to explain what problem it solves and why we have to deal with these kind of problems at Tes. micro-services integration One of the most important decisions we had to take when designing our micro-service architecture, is how to make micro-services work together. This is a particularly tricky choice, because you should choose a pattern that allows micro-services to be shipped independently and create the least amount of friction between services (and teams as per Conway’s law).

On Tuesday evening, post the launch of the new home page, we had a second set of performance problems that impacted the entire tes.com site around 6pm for 40 minutes, and then subsequently during two periods at 9pm and 12am. The root cause turned out to be a misconfigured Redis caching server that was moved to in response to the issues on the 24th of April. During the post-mortem of the issues the day before we had agreed that a key action was to upgrade and improve the monitoring of the part of our platform that does the composition of the shared fragments (e.g.

We had a number of site related performance issues on Monday 24th April that impacted the entirety of tes.com. The fix to which (as always) was deceptively simple, and resulted in response times on average dropping from 100ms to 10ms, and CPU usage on the server reduce by almost 400%. As part of the rebrand we have been rebuilding the services that supply shared assets to all parts of our platform, which include core styles, images and the fragments of HTML for the masthead, footer and left hand navigation rail.

Accelerated Mobile Pages are normal stuff of the web in many respects - publicly reachable via a URL, viewable in any browser, built with HTML, CSS and Javascript. The difference is, they load almost instantly on mobile - music to the ears of anyone who's waited 10 seconds for a page to load over 3G (all of us, then). More information is on the AMP project website. The payoff if you make an AMP version of your page SEO - AMP pages can be served higher up Google search results, for example in the carousel of article stories that you sometimes see when googling for news.

This is the second in a series of posts about improving page performance. Part 1 discussed what we're measuring and how. A video of me talking about the performance issues discussed in this post. The problem For the job details page, we accept banners supplied by schools which aren't compressed as well they could be. Large images don't block the rendering of the main content, however they hog bandwidth, especially on mobile.

A video of me talking about the performance issues discussed in this post. How are we defining 'page load speed'? How quickly the user can see and interact with core page content after they navigate. Non-core content could be adverts, their user avatar, or recommended links. It's important they appear as quickly as possible but they're not the main reason the user navigated to the page. Where are the biggest gains to be made?