Delivering thin resources is essential, especially when it comes to HTML. If HTML is turning out big, we have no room left for CSS resources or javascript in our performance budget.

En rythme de croisière, et grâce à une stratégie de cache plutôt défensive, 3 machines standard (8 vCPU et 30 Go de RAM) sous Node sont suffisantes pour supporter la charge. Ce dimensionnement est auto-scalable en cas de très fort pic de trafic, c’est-à-dire que le nombre de machines augmentera automatiquement pour absorber l’afflux de connexion. De quoi envisager plus sereinement les grandes soirées de matchs.

Since the beginning, Google has insisted AMP is the best solution for the web’s performance problem. And Google’s used its market dominance to force publishers to adopt the framework, going so far as to suggest that AMP’s the only format you need to publish pages on the web. But we’ve reached a point where AMP may “solve” the web’s performance issues by supercharging the web’s accessibility problem, excluding even more people from accessing the content they deserve.