Alin (a11n)

Hi @lukeyr1minstrels1,

Since this issue is about how your site displays on mobile devices and not about the WordPress app, you might get more specialized help in the www.ads-software.com Support Forums, especially if you mention the specific theme you’re using. You can also try to contact the WordPress Theme’s developers as they might better quide you on how the theme works on smaller screen sizes.

This is the support forum thread for the WordPress app so if you have any questions related to the app, please let us know.

Best!

Hi @hansbeen,

I noticed the XML-RPC file is still not accessible on your site. Have you had a chance to try the suggestions James shared earlier? If you need any help, feel free to reach out.

Thank you!

Hi @wordpressdood125,

Yes, Jetpack includes a pop-up window feature for email subscriptions. You can enable it by navigating to?Jetpack → Settings → Newsletter?and toggling?Show subscription pop-up when scrolling a post?to the?on?position. Note that this pop-up is designed to appear only on posts, not pages or custom post types.

You can learn more about this feature here:

https://jetpack.com/support/newsletter/customize-the-newsletter-experience/#enable-a-subscriber-pop-up-for-your-posts

Let us know if this helps.

Hi @posterboyie,

Glad to hear you managed to sort it out.

Given the issue is solved, I’m going to close the thread and if anything comes up, feel free to reach out again.

Best regards!

Hi @jlou65535,

Thanks for your update! I’m not very familiar with Azure Front Door, so can’t make any recommendations about it, but since your focus is on Jetpack Boost, let’s try to resolve the issue related to Critical CSS generation.

It seems like the Jetpack connection is still interrupted, which is critical for Boost to function properly. Please follow these steps to try reconnecting:

1. Reinstall Jetpack: This can help resolve any connection issues. You can follow our guide here: Reinstall Jetpack, in case you didn’t try that yet.
2. Check for any conflicts: You’ve already disabled W3 Total Cache and you could also temporarily disable any other caching tools (such as Azure Front Door) to check if they’re interfering with the connection or the Critical CSS generation.

Once the connection is restored, try enabling Jetpack Boost again and see if the Critical CSS error is resolved.

Let us know how it goes or if you need further help!

Hi @ssevener,

Thank you so much for your kind words! Happy to help!

Hi @ravanh ,

Me again. Our developers confirmed the bug and they are already investigating it. As promised, we’ll keep you updated.

Thank you for reporting this!

Hi @ravanh,

Thank you for the details provided.

I’m checking with our developers and will keep you updated here.

Please stay tuned!

Hi @ravanh,

Thank you for providing the detailed error log. I’ve tried replicating the issue on my end but haven’t been able to reproduce it.

Could you please share your site URL with us so we can take a closer look and try to replicate the issue in a similar setup? It would also help us check for any potential causes specific to your environment.

If you want it to remain private, you can also contact us via?contact form. If you choose to reach out directly, please include a link to this thread.

Thank you!

Hi @hendrix924,

Thank you for providing the details.

I noticed that you currently have the Better Recent Comments plugin installed, and it looks like the Jetpack Comments feature is now disabled. Could you confirm if you deactivated Jetpack Comments and installed this plugin afterward? This might help us pinpoint whether the issue is related to the recent changes.

Since the issue persists, it might also be worth checking if any JavaScript errors are occurring when a comment is submitted. You can do this by opening your browser’s developer tools (usually by pressing F12 or by right-clicking and selecting Inspect). From there, navigate to the Console tab and try submitting a comment again to see if any errors appear. If any errors are displayed, please share them with us, as they could provide more insight into the issue.

Let me know what you find, and we’ll go from there!

Hi @readonecc,

Thank you for contacting us via email. I’ve just sent a reply so let’s continue there. I’m going to mark this as resolved and looking forwad to hearing back from you via email.

Best regards!

Hi @casaspain,

It looks like we had a similar case reported in the past and it turned out being an issue with Chrome only. Can you please check another browser, like Firefox or Safari to see if the issue persists? Also, please try to clear cache and cookies on Chrome and see how it goes.

Hi @africshowbiz1,

I noticed that Critical CSS couldn’t be generated for the page https://africshowbiz.ng//tag//playdee because it timed out while loading. I checked the page, and it does load very slowly.

It might be worth checking for large files or external scripts that could be causing this. You could also ask your hosting provider if there are any server issues or limits impacting the page’s performance.

Once that’s sorted, you can try generating the Critical CSS again.

Let me know if you need any help with this!

Hi @ppnsteve,

Thanks for your great question!

You’re right—CSS is generally applied site-wide. However, when we recommend regenerating Critical CSS after creating or editing a post or page, it’s because Critical CSS is optimized for the specific content that users first see when visiting a page. Since posts and pages can introduce new elements (like images, embeds, or custom blocks) that might impact the layout or what’s visible “above the fold,” regenerating the Critical CSS ensures that the most important elements load quickly.

In short, while the overall CSS doesn’t change, the Critical CSS helps prioritize loading the content that’s immediately visible to your visitors. Keeping it updated ensures the best performance!

Hope this clears things up! Let me know if you have any other questions.

Best!

Hi @jlou65535,

It looks like the Jetpack connection is currently completely interrupted. I’d recommend trying a full Jetpack reinstall and reconnect following the steps in this guide:

https://jetpack.com/support/reconnecting-reinstalling-jetpack/

Please give this a try and let us know how it goes.