Homepage images not showing & A few other issues

  • Resolved Supplement Genie

    (@supplementgenie)


    5 years, 9 months ago

    I have enabled the debug mode but unsure if I report the issue here or if I should report somewhere else?

    I have activated the plugin and the images on my front page have been removed. the images are inserted via the wordpress customiser.

    Also, when I check the pages it gives me advise to defer render blocking scripts/css etc. is this something that I can do with your plugin? i have activated the defer option but it doesnt seem to be working.

    The last thing is the optimized pages. I am using the guest plan. There are some pages I would rather not use the optimisation plugin on which are being optimized and others which I would like to try it on which are not currently optimizing. can i change this?

    My Favicon has also been temoved from the tob but only on my homepage

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Pegasaas

    (@pegasaas)

    Hey @supplementgenie,

    I’m sorry to hear about this and I appreciate you taking the time to submit your issue — I will do everything in my power to determine what is going on and come up with a resolution.

    It sounds like a few things are going on:

    1) It sounds like the path to the images are being updated to reference the optimized version (stored in the /wp-content/pegasaas-cache/ folder), that the plugin optimizes on the fly, but that they’re not being saved to the pegasaas-cache/ folder. This is possibly caused by a block by a firewall such as Cloudflare, or by permissions on the server being non-typical resulting the plugin not being able to save the optimized file.

    2) The deferral of render blocking scripts should be automatic. If we’re still getting this flag from the PageSpeed system, then it indicates that those resources are likely being injected into the page via JavaScript, but are still considered render blocking. This can sometimes happen when the theme framework has attempted to provide their own web performance improvements, which actually counteract what our plugin is trying to accomplish. Another remote possibility is that the page that is being scanned is not actually optimized, but a server level cache (either Varnish, LiteSpeed, or CDN such as Cloudflare) that is serving a stale version of the page.

    3) During the installation routine, there is an “Advanced” option to choose which pages you want optimized. If you happened to choose “Everything”, all pages will have the “acceleration” flag turned on. You can TURN OFF the acceleration flag individually by going to the Pages (or Posts) option in the WordPress menu, and then click the “toggle” button which is on the right side of the row for each page listed. If you want to disable acceleration for all pages, there is now a “Tools” tab on the “Accelerator” dashboard. The “Tools” tab is located below the “speed gauge” interface. When you select it, you can disable all acceleration for a given Page / Post / Custom Post Type.

    Now, I would very much like to investigate issues #1 and #2. Please initiate a ticket through at https://pegasaas.com/contact/ with your website address (and reference this message) so that I can take a closer look. You will not need to take the plugin out of diagnostic unless I cannot figure out what is going on.

    Again, I appreciate you taking the time to submit your issue.

    Kind regards,
    Brandon Devnich
    Founder / Primary Developer
    Pegasaas

    Plugin Author Pegasaas

    (@pegasaas)

    Marking this issue as resolved. To summarize the issue, and the solution: This particular site was using permalinks without a trailing slash. The way our system was built, expected a trailing slash in the permalinks. This resulted in the optimized page cache not saving correctly.

    Handling for this scenario was added to the plugin and tested with the site that was having a problem. That update will be included in the upcoming 2.2.13 release.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Homepage images not showing & A few other issues’ is closed to new replies.