clairedelacroix

Hi Herman,

disabled all plugin as debugging routine, js error is still there even with astra theme alone.
I’ve also setted up a local enviroment, same error.

It shows up in dev console (incognito mode or not) only emulating iOS devices, android and desktop are all fine.
No performance issue.

Could you please check it? Because I’m seeing it on almost every astra powered page posted here.

Thank you.

Same console error here (astra 3.7.7.1). Yes, only on mobile resolution targeting on iOS.
Error happens even ispecting Astra official website itself.

@rafaeldplanet : you can add js with astra custom layouts (only astra pro), via astra hook plugin or in a child theme.

I really think that astra set font-display:fallback by default.
When you add a Google font (via customizer) you first see the fallback font, then the Google font.
The difference in letters size/style between them is the FUOT you are referring at I presume.

– Font-display:optional (or block) will hide the system font but you have to wait until google font loads, infact fallback or swap are used mainly to avoid some pagespeed warnings.

Astra font-display

How to modify Astra font-display

You can try also preloading but from what I remember you have to serve self hosted Google fonts.

Hope it helps!

That’s fine Herman, thanks!

Hi Suman,

after Astra 3.1 update I’ve opened ticket n: 511883:
at the beginning it was related other simple issues that I’ve faced updating from 3.0.3 to 3.1, but all of them I’ve solved by myself. On Saturday I’ve discovered the issue related to this thread that is the one I’m not able to solve: I’ve asked here first and then reported also in my ticket.
I’ve shared login details of my staging environment for debugging.

Hello Team Brainstorm Force,

thanks for quick reply and theme update!

Just tested now on staging Astra 3.1.2 and Astra pro 3.1 (anyway issue is related only to astra theme from 3.1 update): sadly header disappearing issue still exists.
Honestly I’ve never had a problem with Astra but I really hope it could be fixed soon because meanwhile I have to rollback to 3.0.3.

Any suggestion how to fix it or workaround?

Haven’t you tried setting submenu bg color under customizer transparent header settings?
From astra 3.1 I’ve found some items not editable anymore under primary header/menu but only under transparent header, other ones changed location.

• This reply was modified 3 years, 8 months ago by clairedelacroix.

That error in the console in my case was due to deferring JavaScript via Perfmatters plugin.

Same here. Error appears from last update.
Seems related to new HTTP request: /wp-includes/js/dist/i18n.min.js

Hi,

I don’t know. Updated to 3.1.0 on a staging site end I endend up with 4 more HTTP requests elementor related and 50kb more page size. (Even with DOM output enabled and “Improved Asset Loading” mode on).
Tested only a little time to be honest.

Same problem here. For me it seems solved clearing any cache: cache plugin, browser.

Regarding site health frozen on “results are still loading” as far as I know it should be fixed in the next jetpack update.

But the first problem from my point of view is Jetpack related because tree days ago I had the same issue (improper site heath items count) and I solved deactivating the plugin.
Once deactivated site health works as always: no more stuck on loading and proper items displayed.
Then I’ve reactivated and reconnected Jetpack and yesterday the issues started again.
It’s nothing I’m really worried about but I hope it will be fixed.

Thank you,

I’ve deactivated Jetpack in my network and site health performs right now: no more freeze on “results still loading” and no more issue dectected: both sites on good status.

Then I’ve network enabled and connected again and all seems fine, except from site health fixed on “results are still loading”. I’ve read it will be fixed in the next update.

I don’t know, maybe that problem started with the last Jetpack update. It seems that it frooze site health behaviour and notification.