Click on the _"Configuration"_ tab to break this stage into component parts,
exposing the cause of the slowness.

image::performance/build-scan-configuration-breakdown.png[title="Build scan configuration breakdown"]

Here you can see the scripts and plugins applied to the project in descending order of how long they took to apply.
The slowest plugin and script applications are good candidates for optimization.

They are suitable for complex build logic that needs to be shared across projects, builds, and teams.
You can also write them in Scala or Groovy but that is not recommended.

Here is a breakdown of all options for implementing Gradle plugins:

[cols="~,~,~,~,~"]
|===
|*#* |*Using:* |*Type:* |*The Plugin is:* |*Recommended?*

|1
|Kotlin DSL
|Script plugin

As your build logic is evolving and changing it is also important to make sure that the cache effectiveness is not regressing.
Build scans provide a detailed performance breakdown which show you how effectively your build is using the build cache:

[.screenshot]
image::build-cache/performance-task-execution.png[]