{"id":21048,"date":"2017-02-21T13:50:14","date_gmt":"2017-02-21T12:50:14","guid":{"rendered":"https:\/\/www.inovex.de\/?p=2562"},"modified":"2026-03-17T08:58:21","modified_gmt":"2026-03-17T07:58:21","slug":"web-performance-optimisation-part-2-perceived-performance","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/web-performance-optimisation-part-2-perceived-performance\/","title":{"rendered":"Web Performance Optimisation (Part 2): Perceived Performance"},"content":{"rendered":"

In the previous article of this series<\/a> we talked about the boundaries of Web performance optimization (WPO). We introduced some metrics and a scale of measurement but we omitted one large part of the problem due to the purely technical point of view we took previously. In reality, while time and performance can be measured objectively it is perceived subjectively by humans. Static measurement scales and performance analyses are relevant for performance measurements but largely irrelevant in real world usage. As long as users have to interact with an application we have to make sure that we test and evaluate the application\u2019s performance from a real user\u2019s perspective. Consequently in this part of the series we want to talk about perceived performance and why it makes sense to put the user first when it comes to WPO.<\/p>\n

\n

<\/p>\n<\/div>