The optimization process and recommendations:

1. Avoid OFFSET In LIMIT Clause (query line: 19): OFFSET clauses can be very slow when used with high offsets (e.g. with high page numbers when implementing paging). Instead, use the following \u003ca target\u003d"_blank" href\u003d"http://www.eversql.com/faster-pagination-in-mysql-why-order-by-with-limit-and-offset-is-slow/"\u003eseek method\u003c/a\u003e, which provides better and more stable response rates.
2. Create Optimal Indexes (modified query below): The recommended indexes are an integral part of this optimization effort and should be created before testing the execution duration of the optimized query.

Optimal indexes for this query:

CREATE INDEX event_idx_accoun_aggreg_proper_type_id ON "Common"."Event" ("AccountCode","AggregateType","PropertyId","Type","Id" desc);
CREATE INDEX event_idx_id ON "Common"."Event" ("Id" desc);

The optimized query:

SELECT
        e."Id",
        e."AggregateId",
        e."CreatedUtc",
        e."OriginClientId",
        e."OriginSubjectId",
        e."PropertyId",
        e."Type" 
    FROM
        "Common"."Event" AS e 
    WHERE
        e."AccountCode" = 'XXXX' 
        AND e."AggregateType" = 1 
        AND e."Type" IN (
            'type-1', 'type-2', 'type-3', 'type-4'
        ) 
        AND e."PropertyId" = 'YYYY' 
    ORDER BY
        e."Id" DESC LIMIT 100 OFFSET 0