Index Update with Eager Spool and Sort operators in Execution Plan

After an UPDATE statement on a large table, the execution plan shows updates of indexes (all non-clustered) that include the updated columns. Before each index update, there is an Eager Spool operator followed by a very costly Sort. Overall, the updates of the indexes consume about 50% of the execution time. Is there a way to optimize the indexes and minimize the costs?