Hi @wardencenter,
We are not aware about the Blocksy Companion doing something like this. But, if you would post here the link to your site, we’ll gladly have a look at why the redirects number is increased — but make sure to have Blocksy Companion activated.
Hope you can cooperate with us here so that we can find a solution to this problem together.
Waiting for your reply.
All the best!
Sure – thanks so much for your help:
https://dewingsenter.org/wp_staging/
The only plugin installed and activated is Blocksy Companion (which is why the site looks so silly). If you plug that site into tools.pingdom.com you’ll see the results I reference.
This is a staging of the main WP site. I’m in the final phase of checks/tests before migrating changes to the main site, but I’ll stay out until I hear back from you.
Thanks so much again.
Kim
Edit: I previously misspoke – I should have only one redirect for http/https… sorry about that.
-
This reply was modified 4 years, 3 months ago by
wardencenter.
@wardencenter Thanks a lot for the update. So, in the end, the issue was only about the http -> https redirect? Can you confirm that the Blocksy Companion still adds one more redirect on your site?
Please let us know, we’d really like to get this fixed if it’s confirmed.
All the best!
Thanks for replying. That development site has since been taken down (sorry, it was time).
No, it had two (2) redirects with only Blocksy Companion Plugin installed, if the site was tested using “http”. Without Blocksy Companion (so zero plugins installed), it went down to the expected one redirect for http>https.
Hope that helps and thanks again.
@wardencenter we understand but unfortunately we re-tested this on our end and we had no such redirect.
If you can give us exact steps to reproduce this, we will follow them and fix the issue if it can be reproduced.
Or, maybe you can bring your development site back and give us the full redirects chain so that we can see where everything is coming from.
Waiting for your reply so that we can fix the problem that you encountered.
Hi there – thanks for the kind reply. I understand.
Our redirects were fixed by installing and configuring the plugin “Asset Cleanup”, and disabling this “site-wide”:
Handle: blocksy-fonts-font-source-google * Stylesheet (.css)
Source: https://fonts.googleapis.com/css2?family=IBM+Plex+Sans+Devanagari:wght@700&family=Open+Sans:wght@300;400;500&family=Open+Sans+Condensed:wght@300&display=swap
I have no idea what’s causing the above. We’ve the Theme “Typography” set to “System Default” in the Customizer. We’re going through page by page looking for any custom fonts set on any pages. So far, we’ve found nothing and with this disabled, all pages look as expected (but then the System Default font looks very similar to those fonts).
Is there perhaps a way to disable this from within Blocksy? Just so we can remove the “Asset Cleanup” plugin (so many plugins!)?
Sincere thanks for checking in on my support post here!
Kim
AH-HA! We found it by using “https://www.sitelocity.com/critical-path-css-generator”
It’s in the header button. There’s no way that we can see to specify the font used for the header button. How do we make the header button use the “System Font” as specified in the “Typography” settings?
UPDATE: We started poking around all the Header settings in the Customizer. We had the Menu font and an “HTML” for the top row customized to “IBM plex sans”. Once we put those to “System Default” font, the button also went to “System Default” font. No more redirects and no more Blocksy showing up in site speed checks as a problem.
Marking as Resolved.
Cheers.
