Frontend performance

Finding why a browser UI is slow to start or to respond, and what to change: how many requests it sends and whether they block each other, how large its bundles are, and which OData round trips it waits on. Distinct from query profiling, which starts at the service and the database rather than at the browser's network log.

Overview

SAP SHIPS

@openui5/sap.ui.core loads libraries and the component preload asynchronously, preloads the OData model and times its own work through the sap/ui/performance/Measurement module; @ui5/cli minifies an app and bundles it into Component-preload.js.

Not covered: At configuration and the build. SAP's performance page sends the reader to the browser's own developer tools to read the network log, and lists a slow OData service, web server or network among the back-end causes.

The one member in this batch, teched2025-CA262, is an SAP TechEd hands-on that demonstrates the analysis on a Fiori elements app; it provides no tool, so core-only rests on SAP's documentation and the two core artifacts.

SourceOpenUI5 documentation — Performance: Speed Up Your Appchecked 2026-09-14

THE COMMUNITY ADDS

@satiroglu/kaev reports, by static rule rather than by measurement, the patterns in a project's own code that make a UI5 application slow to start or to respond, such as a synchronous read call or an OData model refreshed inside a loop.

@satiroglu/kaev