This page demonstrates a sample Flight Listing. It is visually identical to the Complex Flight Listings page.

BUT, for this example, all the flight results are rendered by a single component.

Take a look at the Blazrlytics Event Trace as you navigate through the list, or apply filters. Then compare the number of events that you are seeing to the amount which are produced by the Complex Flight Listings example.

Breaking down the components into many sub-components is a common practice in Blazor development. However, it can have a significant impact on performance.

This example is extreme, as there is no break-down of components at all. However, when paired with the Complex example it does illustrate what a huge overhead can be introduced by excessive componentisation.

Blazrlytics helps you to quickly spot excessive lifecycle events, and re-renders, and helps you to optimise your code.