Hi @julianoe ,
I’m sorry about this issue.
I’ve tested the new version on several sites and I wasn’t able to replicate this issue with bold fonts.
This is most probably a conflict with some other plugin, so I suggest performing a conflict test as described here https://wpmudev.com/blog/wordpress-plugin-conflicts-how-to-check-for-them-and-what-to-do/
kind regards,
Kasia
It’s tested in Troubleshooting mode, with only default wordpress theme and Broken Link Checker activated and as you can see on those screenshots, it’s because your plugin enqueues Roboto fonts from a foreign domain (https://fonts.bunny.net/, why should I need request from there to check my broken links?).
It adds load time, adds some kb of data to load and foreign domain requests to wait for.. on every single request from every admin screen… No wonder users accuse BLC to become a bloatware. Maybe follow WordPress provided fonts CSS instead?
See the screenshots here
https://ibb.co/fHYZWg3
https://ibb.co/RPS7Svh
https://ibb.co/Ws9PmNt
https://ibb.co/gDGmhWV
If every one of the 45 plugins we need to make our website (thousands of visitors and dozens of active editors) work added 40ko of fonts (what’s more from a foreign domain!) we would end up with every page load on the admin weighing 2mo and taking seconds to load.
You are part of the 80 most downloaded plugins on the WordPress.org catalogue and among the biggest plugin editors and owners. Understand that users expect better of you.
Hi @julianoe
Could you please confirm if you are using Ubuntu OS?
We found it is adding the Roboto font causing the issue, there is a fix already with our QA team and we will be releasing this as soon as the tests are done, including it loading across pages.
Best Regards
Patrick Freitas
Hi,
not Ubuntu but Manjaro linux distribution indeed, with Firefox browser.
-
This reply was modified 3 years ago by
julianoe.
Hi @julianoe
Sorry for the inconvenience!
I have shared the reported distribution and browser, so it is considered in the tests to be performed by our QA team. There is not a ETA yet, but once the fix is verified, it will be added on an upcoming release.
Kind regards
Luis
it seems it still has not been fixed
Hi @julianoe
This issue was fixed in the middle of March in version 2.1.0.
Can you check if you use version 2.2.0 and do you still see this issue?
Kind Regards,
Kris
Hi @julianoe,
Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to re-open the thread if you need further assistance.
Best Regards
Nithin
