Display caching and Used CSS status

viobru commented 2 years ago

Is your feature request related to a problem? Please describe.

Currently, there is no way for customers to check from the site which pages have been already cached or which ones have the used CSS already created.

This can be checked through the server, but it is not handy for sites with lots of URLs.

From the customer: At the moment the preloading/caching runs itself and we get a wee message at the time to confirm it's running, similar to the used CSS process, but once those messages are gone we kind of just have to presume that the pages are cached and used CSS is processed.

Describe the solution you'd like Create a status section for the cache and used CSS, so customers can verify directly from the site if a URL has been cached and/or if the used CSS has been created for it.

Describe alternatives you've considered N/A

Additional context HS Ticket: https://secure.helpscout.net/conversation/2002117163/366959 Slack thread: https://wp-media.slack.com/archives/C08N8J6VC/p1662653993680349

webtrainingwheels commented 2 years ago

Requesting preload stats: https://secure.helpscout.net/conversation/2007580342/368089?folderId=377611

NataliaDrause commented 2 years ago

Preload and Used CSS status request: https://secure.helpscout.net/conversation/2010217975/368693?folderId=3864740

NataliaDrause commented 2 years ago

Preload status request: https://secure.helpscout.net/conversation/2024358554/371929?folderId=3864740

DahmaniAdame commented 1 year ago

RUCSS status request - https://secure.helpscout.net/conversation/2048084397/377096/

WordPresseur commented 1 year ago

Preload and Used CSS request: https://secure.helpscout.net/conversation/2062683526/380515?folderId=1213662

schobermuc commented 1 year ago

Extend: Is your feature request related to a problem? Please describe.

Preloading stops for websites with many pages. Checking the preload process as described would make that more visible. There is only the way of starting the process for the whole site. Which might again not run trough.
After an update in the content not all pages need to be preloaded again. Currently the preloading process can only be started for the whole page. Not for specific pages. Preloading takes a long time and needs a lot of CPU. Not ideal for websites with many pages.

Extend: Describe the solution you'd like: Not only an overview of checking the process of preload. Additionally a way of starting the preload where it stoped.

Describe alternatives you've considered Option to only start the preload for specific pages eg. by post type / when last preloaded / if already preloaded or not yet preloaded.