What are web bots, how they affect e-commerce, and an extremely simple machine-learning recipe to fight them.
When it comes to enhancing web page loading times using HTTP/2, there is an unexplored, uncharted land of opportunities, by just using backend waiting times to — optimistically — start sending assets to the browser before the contents are returned by the backend.
Tools like PageSpeed Insights, Pingdom Tools and WebPagetest are common to monitor website speed. But unfortunately they were not created for the modern web.
All of these tools can be used to reduce website loading times:
Implementing a web server around the concept of HTTP/2 Push is a good opportunity to understand how this technique works. We are pleased to share some of that knowledge with you.
We often talk about Full stack monitoring, integrated. The word “integrated” is quite abused in the tech world. Usually, “integrated” means that the feature comes with the product. So, ShimmerCat includes full stack monitoring, out of the box, and our service is rather unique even on that sense. But there is more.
To use HTTP/2 Push effectively, servers need to know well what is not necessary to Push. Cache digests provide the necessary information to make that possible.
A flash in a loading web page doesn’t look good, but it is quite hard to solve when it happens randomly. We look to three tweaks that can make the flash more regular and therefore easier to solve.
HTTP/2 Push gives you the possibility to serve everything in one go: as soon as the server notices that the client is requesting the html file, it can send both this file - and most or all the other files that the client is going to need. This feature substantially improve performance. You can also see more in this video
About ShimmerCat and AngularJS, RequireJS and HTTP/2 Push.
Browsers do all sort of clever things to render a website fast. But they are not omniscient, and because they lack data, they end up wasting precious seconds and bandwidth.