The message "...
....." is normal behaviour, pagespeed can´t fecht a resource and "remember" the failure for some time and don´t try to fecht again for amount of time.
Regarding the config, you have 3 ModPagespeedDomain:
These 2 works only for http, not for https
Try to change for some like:
This cover http and https, the main domain (somedomain.com
) and all the subdomains belongs to it.
In the image Options I can see ModPagespeedFechtHttps enable and
ModPagespeedSslCertDirectory /etc/ssl/cert but in the image config only see
ModPagespeedFechtHttps enable so the config is incomplete, because
ModPagespeedSslCertDirectory /etc/ssl/cert is set but is not in the config image.
Cloudflare: you must set CF to respect the origin headers.
In Caching -> Configuration -> Browser TTL chose "Respect origin headers"
and if you have any Rules -> Page Rules you must set "Origin Cache Control" to enable.
Pagespeed serves html with cache-control: max-age=0, nocache so you must see this header in the html served
Other resources, like images, js or css are server with
max-age=31536000 when optimized (have pagespeed in the url)
When make this changes, clear the CF cache
To debug you must add ?PageSpeedFilters=+debug to the request:
and then take a look at the html code, here you can see debug messages as html comments.