Wordpress LScache Plugin: a::before content: field is trimmed by UCSS
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi there, im struggeling with UCSS and a::before / a::after symbols quoted as unicode in content: field. Please have a look on the given site for example. The arrows on navigational links get replaced by numerical part of the unicode ID: Before UCSS: content: 2B60 After UCSS: content: B60 Without optimization and with local CSS optimization everything is fine. As soon as UCSS is calculated by quic.cloud, the backslash and all numeric characters seem to be trimmed. I tried 2190 as a different arrow unicode letter, but this is trimmmed to 90 . It looks like there is a treatment which trims the pattern of backslash and up to 2 numerical chars if the first char following the backslash is numeric. I use font awesome symbols as well, but those start with fxxx (facebook- and mail-to-links on every page) and dont get trimmed by ucss. Can you please check whether there is a problem on the quic.cloud optimization algorithms? Or if not, please give me a hint how to fix this, without waiving UCSS functionality. The page I need help with: https://www.ballettschule-buxtehude.de/allgemein/rueckkehr-in-den-tanzsaal/ Still not working. Any ideas?
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference