See the attached video. Looking further after recording this. If I have any fonts registered in Bricks->Custom fonts the number of queries significantly increases. The more fonts, the more queries, even if the fonts arenāt being used anywhere.
I had 15 font families registered and was getting over 800 queries. Moving the 13 unused fonts to trash the queries dropped to 200.
I just replied to your email.
We can replicate this issue and will enhance the way Bricks retrieve the custom fonts before generating the CSS style.
Side note:
You can still use the Custom fonts on the production site as usual although the number of queries seems high, the load time added is below 0.1s
Appreciate your time in reporting this issue to us. Thank you.
Yes, I forgot to put a note on the forum comments. My performance issue was that PHP Opcache disabled. When I was troubleshooting and saw 800 queries, it led me down the wrong path
Hey guys, it looks like it 1,7,2 update has caused an issue.
All of my custom fonts are being output as inline CSS in the Browser. I even tried trashing them, and then completely deleted them. They still get output as Inline CSS.
I have no caching enabled and tried incognito.
Checking the DB. The options table for ābricks_font_face_rulesā still has all the deleted fonts
I havenāt updated yet, but Bricks has an issue with fonts, or at least thatās what happened to me when I migrated a website (all-in-one wp migration).
The solution I found is to go to a template, then to Settings > Theme Styles > Typography, delete the font and save it. After that, add the font again and it should work. At least, thatās what worked for me with migrations, maybe it could work for you too.
Iām still not sure if it worked by chance or if thereās a bug in the system.
I had a similar issue after cloning my bricks blueprint. Font URLs were still pointing to the old domain and Cors wasnāt enabled on my server so it couldnāt retrieve them. Re-generating external css files fixed it though. Maybe give that a try next time u migrate cause thatās a lot easier than resaving them in the typo settings.
First of all, the fact that the font-face rules are added inline is not a bug: Changelog ā Bricks
Currently, you can force the rules to regenerate the font-face rules and get rid of the unused ones by adding a new custom font. We will try to improve this in the future so that the rules are also regenerated when a font is deleted.
However, the font-face rules have no influence on your page performance because the fonts are not loaded unless they are requested somewhere. This means that if you do not use the font, the font file will not be loaded.
The inline font-face rules only ensure that the path to the file is available everywhere. This allows you, for example, to use the font in custom CSS, which was previously only possible in a cumbersome way (by manually adding the font-face rule).
Hi Alan,
With Bricks 1.7.3, now available as a one-click update in your WordPress Dashboard, the font-face rules will update as soon as you enter the ācustom fontsā screen, so there shouldnāt be no more issues.
