You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
-
Ooh, that's a good idea.
It didn't mean that.
It meant that "page 1 is fast", "pages 2 and onwards are a little slower".
But... hey, I could prefetch the next search page and then when you click the link the browser either has it, or the server has already cached the query... either way that would be fast.
Cool.
So my changes this evening (when I get home) will be:
- Split the search query into 2 queries, one that does the search and one that counts the results.
- Add a prefetch meta header to the search results page.
- Entirely unrelated, add a meta header to prevent sending referrer headers off-site, which improves privacy.
- Split the search query into 2 queries, one that does the search and one that counts the results.
Velocio
Would that mean that while a user is reading page 1, the subsequent pages would be being fetched and...cached for loading?...
Sorry I'm not massively familiar with this level of coding.