Hey!

A 20s response time should not usually be caused by the public Railway URL. It’s worth checking whether the delay happens on every request or only on the first one after some inactivity, since that can point to a cold-start issue if the service has been sleeping.

Large or remote Cloud Optimized GeoTIFFs can also add significant processing time, and Titiler itself is CPU-intensive when generating tiles and reading metadata.

Checking Railway’s logs and metrics for CPU or memory spikes during requests can help narrow things down. Pre-warming tiles, enabling caching, or increasing CPU and memory allocation (the Hobby plan helps, but heavy workloads may still need more) are good ways to improve performance.