The transportation layer could benefit from generalized tables, similar to how land use was implemented.

The landuse layer needs to be optimized dramatically. Looking at the following screenshots, one with the landuse layer enabled and one without, you can see the tile sizes go from 10s of kb to 100s of kbs.

Suggested solution: Create either generalized tables or generalized materialized views and apply simplification to the geometries. This will dramatically reduce the number of vertices we need to encode in the tiles and likely produce a noticeable performance gain.

The transportation layer uses materialized views for simplified geometry data. These views need a refresh strategy so they can be updated alongside the hourly imposm updates.

The lower zooms (3,4) have some heavy tiles (over 1mb). I believe this is due to the water layer, but this needs to be investigated. We might benefit from creating some generalized tables for the water layer.