Web hosting for car dealerships — measure a filtered result page, not the homepage

A dealership site is a catalogue with a search over it. Stock arrives from a feed, each vehicle carries thirty or forty photographs, and buyers narrow it down by six or seven fields before they look at anything in detail.

That shape produces a specific performance profile which almost nothing on a normal hosting comparison page addresses. The homepage is fine. The vehicle detail page is heavy but cacheable. The filtered result page is neither fine nor cacheable, and it is the page that decides whether an enquiry happens.

This guide works through the three of them in the order a buyer meets them, with the measurement that matters at each stage.

Six filter fields with a handful of options each produce thousands of possible combinations, each a distinct URL. A cache cannot help with that in any practical way, so every filtered view runs the query. What decides whether that hurts is indexing: a stock table queried on unindexed columns will scan the lot.

Time it directly. Load a filtered result page with a cache-busting parameter, read Time to First Byte, then load the unfiltered list and compare. If the filtered version is several times slower, the query is the problem rather than the platform, and NVMe storage is shortening a path that should not be that long in the first place.

Keep three numbers, not one: TTFB on a filtered result page with a cold cache, LCP on a vehicle detail page on Slow 4G, and total image count and weight on that same detail page. Those three describe a dealership site completely.

Re-run them after every theme change and after any stock plugin update. Twenty-five sites on Turbo gives you room to keep a staging copy alongside the live site, so a plugin update gets timed before it reaches the forecourt listing buyers are looking at.