Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-741621888
>Should I add unnplugged to each location, or the server should handle them
all directly?
Put it one time, out of any location but in the server block.
```
server {
listen 80;
server_name 127.0.0.1;
allow 127.0.0.1;
pagespeed unplugged;
location /nginx_status {
```
>I had managed to take the pagespeed from 180ms full load to 300ms full
load.
Maybe you have added more content to the page. But have:
InPlaceRewriteDeadlineMs
RewriteDeadlinePerFlushMs
set to values more higth than the default.
>Also I was once checking 1 week ago the cache side of pagespeed, I used to
have there inside 2 folders one so called v3 and the SHM folder,
These are diferrent caches... one for rewrited resources (those that have
pagespeed in the url), one for metadata about resources (what url belongs to a
webp version of a jpg url ando so..). SHM is a in memory cache, but you have
enabled to write it to disk every 5min (ShmMetadataCacheCheckpointIntervalSec)
to survive between restarts.
Local cache (pagespeed EnableFilters local_storage_cache;) is for others
purposes. Read https://www.modpagespeed.com/doc/filter-local-storage-cache.
>What are the debug variabled to see where issues occur and where pagespeed
have troubles
https://uhl.site/?PageSpeedFilters=+debug
You can enable/disable some filters (+ or -) as url parameters.
> i know you mentioned this is wrong and should be avoided, and so I do.
Inlining maybe wrong when http2 is in place.
>I just notice first console error, in long time now:
Maybe you have deleted a file in use... There is no directives to clean up
the statistics files.
>Is there a way to make the combined css's shorter especially is there even
possible to change the pagespeed addition to urls, maybe into something like ps
No and no. Maybe you can combine less files with `pagespeed
MaxCombinedCssBytes MaxBytes;`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
