The optimization process and recommendations:

1. Avoid OFFSET In LIMIT Clause (query line: 24): 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:

ALTER TABLE `item` ADD INDEX `item_idx_sale_type_picture` (`sale_type`,`picture`);
ALTER TABLE `item` ADD INDEX `item_idx_score` (`score`);

The optimized query:

SELECT
        i.id,
        i.sale_type,
        i.property_type,
        i.title,
        i.property_name,
        i.latitude,
        i.longitude,
        i.street_number,
        i.street_name,
        i.post_code,
        i.picture,
        i.url,
        i.score,
        i.dw_id,
        i.post_date 
    FROM
        item i 
    WHERE
        i.picture IS NOT NULL 
        AND i.picture != '' 
        AND i.sale_type = 0 
    ORDER BY
        i.score DESC LIMIT 110000,
        60