litespeedtech / litespeedtech/lscache_wp

UCSS by content type

Open
#408 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
257
Forks
123
PR merge metrics
No merged PRs in 30d

Description

Hello,

We are encountering problem to enable UCSS functionality by URL in the projects we manage. Our projects are huge, with thousands of URLs. In order not to over consume the page optimization limit per month, nor to lengthen the waiting time, we are forced to choose what type of content should have UCSS.

To exclude URLS such as attachment pages, author pages, taxonomy archives, forum pages, etc. we have tried to use the API filter `litespeed_ucss_exc` but we find it problematic, as the DB queries are very heavy. We are forced to develop a complex system to retrieve those thousands of URLs without excessive execution time.

Therefore we wanted to propose two alternatives, which we think would facilitate the implementation:

* Being able to indicate to the UCSS cron which URLs do not have to be included by means of an HTML attribute or some specific ID or CSS class.
* Being able to indicate not only which types of content are excluded from the UCSS, but also which ones are included.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the litespeed_ucss_exc API filter and the UCSS cron path described in the issue. Compare the two proposed ways to select content and identify the existing URL-query flow. Done would require a documented, efficient way to include or exclude content types without excessive database work.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.