WebPage loading unused Scripts/Styles

Pagespeed results can be viewed here:

https://pagespeed.web.dev/analysis/https-dunbarmedical-com-products-braces-and-supports-ankle-brace-support-ankle-brace-with-straps-bioskin-trilok-ankle-brace/fg208jz4tu?form_factor=mobile

@michaeltrotz
About the JS links you shared: we are not able remove unused JS file, just to minify and combine it.

About UCSS can you make sure the service is working and the queque is being created and run.
You can enable LSC logs to see what is the problem.

Hello – the first and seventh of these items seem to come from the LiteSpeed plugin itself so I would have hoped that they should not be appearing in the list in any case. Thanks.

these are not added by LSCWP , if you disable plugin and check again , you will see them as well , but only with different names

LSCWP just minify/combine them into /wp-content/litespeed/js or css/

Is there a way to know the original names and how they were added? Thanks.

disable JS minify JS conmbine , CSS minify and CSS combine , then you will see its original name and path

Hello – I have now got to a point at which the main PSI issue for all URLs tested appears to be unused CSS in the following file:

https://dunbarmedical.com/wp-content/litespeed/css/b2ca982c8b4a47d9858b6e414907e52f.css?ver=4166a

I am seriously doubting that this file represents a combined CSS file for the following reasons:

1. I have switched on the UCSS option (as well as the CCSS option). As I understand things, this should mean that the combined CSS file should vary depending on the URL tested. However, this same file is being reported (as a source of unused CSS) for all the URLs I have tested.

2. In addition, there should be no unused CSS at any URL if a unique CSS file is being generated for each URL.

3. Finally, I have run the Chrome Coverage report on a logged in view of the site (when the cache is bypassed) and this file appears in that report.

Given these observations, I am forced to conclude that this file is not a combined CSS file. If so, how should I deal with it in order to remove its impact on the PSI score?

The latest PSI results for the mobile view can be seen at:

https://pagespeed.web.dev/analysis/https-dunbarmedical-com/ixfupqjpw7?form_factor=mobile

Thanks.

• This reply was modified 1 week, 4 days ago by michaeltrotz.

when you have UCSS generated , you will see file as /wp-content/litespeed/ucss/xxxxx.css , or embed into inline style with name litespeed-ucss

and if you check the html source comment at bottom

<!-- QUIC.cloud UCSS in queue -->

the UCSS generation is still in queue

Thanks for the feedback. Is there a way to force prioritization of certain URLs where generation of UCSS and CCSS is concerned? Otherwise, how long will it be before I can see the effect of UCSS/CCSS for the home page URL?

unfortunately no , but you can clean the ucss queue , then access the ones you want to generate first manually , then this way they should be put into first queue

the time it takes for generation would vary , depends on your quota , generator node load …etc

OK – thanks. PSI is also reporting that there are several images (like the logo) that should be served in next gen formats like WebP. It is also suggesting the used of the Performance Labs plugin to achieve this. I have that plugin installed already but am not using it for that purpose in case it conflicts with LiteSpeed. Is there a way to use LiteSpeed to deal with that issue, or should I use another plugin like Performance Labs for that?

The logo file reported by PSI as needing conversion to WebP (or other next gen format) is https://dunbarmedical.com/wp-content/uploads/2023/09/Logo.jpg

Is there a way to check whether a WebP version of this file has already been generated by LiteSpeed and, if so, why is it not being used to generate website pages (according to PSI)?

you can go to Media , in the right-side column , it should have an indicator to indicates the optimization for images

some images may not get webp version for various version , or it has not been optimized yet

Hello – Going back to the UCSS issue, only 2 of these files have been generated and I have found the following message in the third css file:

/* [ERROR] UCSS generation took too long. Likely your CSS and/or HTML will need to be optimized. Please correct this and try again. */

Can someone suggest how to get around this issue and continue generating used CSS files?

Thanks.

unfortunately I don’t have good solution to this

there is a limit cap on size and time for UCSS / CCSS generation

by the error message you posted , please try to shrink a bit the page to make it below the limit

also we are testing something about UCSS internally , which also comes with wider limit range that could potentially work for you without you to do anything.