Support » Plugin: Jetpack Boost » Body font size shrinks by about 50%

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author pyronaur

    (@pyronaur)

    Hey!

    Thanks for the report! Just to note you don’t need to disable the whole plugin – just disable Critical CSS for now.

    Looks like the issue might be coming from how the theme is setup to use em units for font sizes and/or the combination with CSS Variables.

    Is that a custom made design on your site, or is it a theme that I can download somewhere to check it out?

    Thread Starter ACEkin

    (@acekin)

    The theme is a child theme for Genesis Framework. It is called Mai Success, a paid theme.

    There were only three options, one about the CSS, a second to push the unnecessary JavaScript to the footer, and lazy load images. The current caching plugin takes care of them anyway.

    Not much boost for me. Thanks. You saw the images, I will delete them now.

    Cemal

    Plugin Author thingalon

    (@thingalon)

    Thank you for the report.

    I have investigated the issue, and discovered that we were not properly handling some of the media rules used by your theme, resulting in some incorrect CSS appearing in your Critical CSS.

    We will work on fixing the issue, and will aim to have a fix out in a release in the near future.

    Thread Starter ACEkin

    (@acekin)

    Thank you. I see a few more options in the plugin description images than I saw in my installation, only three. Could that be tied to the same issue?

    I will now reinstall the plugin but not activate it so that I will be aware of the update.

    May I also suggest a clear message, possibly in bold that before turning on the critical CSS option, the caching plugin should be stopped, and the cache be cleared as I understood after a failed attempt.

    Cemal

    Thread Starter ACEkin

    (@acekin)

    I have updated the plugin this morning and activated it. However, it has not been able to complete the site score after three tries. I am not going any further and empty the built cache at this point. Maybe after the next update.

    Cemal

    Plugin Author pyronaur

    (@pyronaur)

    Hey @acekin!

    Can you take screenshots of all your caching settings (all plugins, Cloudflare, etc.) so that I can set-up a test environment like yours? That would be a ton of help to deal with this 🙂

    Thread Starter ACEkin

    (@acekin)

    I’ll be glad to. But, is there a way to share this without baring the back end of my site in public? I will share a list of plugins, settings of the caching software, CloudFlare, the theme.

    Cemal

    Plugin Author pyronaur

    (@pyronaur)

    Sure thing – send them to JetpackBoost@automattic.com and add a link back to this thread.

    Plugin Author pyronaur

    (@pyronaur)

    Thanks for the screenshots.

    Can you activate Cloudflare developer mode and test Boost then? That’ll help figure out whether to look at Cloudflare more closely or WP Fastest Cache.

    Thread Starter ACEkin

    (@acekin)

    I have just updated the Boost plugin to the latest version, 1.0.3, and went to the JP Boost settings. It failed to complete the scoring. I disabled my caching plugin (once more) and tried again. No dice. I’m afraid Boost does not like my site!! For the time being, I will not try Boost again. Every time I delete the cache, it takes another week or ten days to build it again. I think disabling the caching software may be necessary before building the Critical CSS. A little more clarity on this may help others who are trying to use Boost.

    Cemal

    Plugin Author pyronaur

    (@pyronaur)

    Hey @acekin – 1.0.3 fixed other critical issues unrelated to CSS 🙂

    Did you try my previous suggestion – deactivating Cloudflare caching?

    Also – worth noting. Typically – deactivating caching plugins doesn’t actually deactivate caching. It’s a bit finicky in how that works, but once you’ve got caching set-up on your site – it usually requires a few more steps to actually get stop the caching.

    Regarding re-building cache – I wouldn’t worry too much about it. It’s normal for sites to have every first request go uncached, and every request after that is going to be served cached.

    With that said, I completely understand the desire to hold off for a little bit until we resolve all of the connection issues first.

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.