Wordpress LScache Plugin: Load More Pagination
Last Updated on: Wed, 15 Apr 2026 00:00:02 Okay, Ive looked all over for an answer to this but no luck. Using Woocommerce, Elementor, and pagination for the custom product archive pages, and have been asked by the client to change pagination to Load More, which I have been testing on a staging site (FacetWp). Had to build a new grid as the old one didnt allow it (and didnt want to add another plugin when far too many already). Everythinng seems to work fine but? Im wondering if the plugin actually caches the products after the first lot have loaded (I have it set for 25 products initially), and the Load More is clicked to load another 25 and so on. Id assumed that when the Load More was clicked it would be treated like Page 2 and cached and would do so everytime the Load More is clicked (just like clicking pages). When I next visited the page after it was cached (used a different browser not logged in) I would have expected near instant loading like when pages are cached and you hit page 2, 3 etc. But not so. In fact while the initial 25 products load quickly, clicking the Load More is no faster than not having the cache on ? its fast enough with or without, but Im suspecting its not actually caching those after the intial first load. I had a look at View Page resource and though the page was cached those extra products after each submission of the button werent listed. Server seems to show more resources used for clicking that page than the one on the live site with pagination too. I dont combine any of the JS or CSS files (caused problems for me) and I have switched off ESI on the staging site (its on at the live one). I dont have object cache on either. Is there a setting that should be on/off when using Load More/Infinite Scrolling pagination to make sure all on the page are cached after the initial load, or is it just a thing that caching and Load More/Infinite Scrolls dont work together well. Im about ready to tell the client he might have to stick with traditional pagination. if the more page is loaded by ajax call , which I assume it is , as this is the most common way , the ajax call wont be cached. Thanks for the response. Yes its FacetWP and uses ajax, and there doesnt appear to be a way to have it not do so. If it was a small retail site it would probably be ok?from a customer POV even if those extra products are not cached it loads quickly enough BUT? its a busy wholesale site and hes already had to add more CPU resources so having those extra products uncached and using extra server memory when is not an option. Guess Ill have to tell him he has to stick with trad pagination if he wants all the products cached, unless he wants to pay for extra physical memory. Thanks for clearing that up for me!
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference