WPBakery includes a setting called Local Google Fonts, which remains disabled by default. When you enable it, WPBakery detects the Google Fonts used on the page, downloads them, and serves them locally. This may sound beneficial in theory, but it often causes drawbacks, especially when using the Total theme. We therefore recommend keeping the setting disabled.
Reasons to Disable WPBakery Local Google Fonts
Here are the main reasons why we recommend keeping it disabled:
Redundant functionality: Total already provides its own Google Fonts handling via the Font Manager, which allows you to specifically choose which fonts to upload to your site. It’s more efficient and safer.
Performance overhead: Each time you save a post, WPBakery parses the post content to check which CSS files load via wp_enqueue_style. It then loops through the files to find any Google Fonts and downloads them to store locally. This process can significantly slow down saving posts and pages on your site.
Maintenance issues: You cannot easily manage the downloaded local fonts or control which fonts WPBakery stores locally, which creates potential maintenance challenges.