[Rich AParticipant]

Hi All,

Upon adding W3 Total Cache to a new site (tried others, W3TC provides the best optimization/performance), Fontawesome icons and post forward/back arrows do not show.

It has to do with W#TC minify. Enabling minify > “auto” breaks Fontawesome. Enabling minify > “manual” and disabling Inline JS minification corrects the problem, however it has a very negative impact on performance.

With W3TC active including minify overall performance is very good:

Pingdom “A” 91
PageSpeed “A” (93%) – YSlow B (83%)

When W3TC is deactivated performance drops to:

Pingdom “C” 73
Pagespeed “D” (67%) – YSlow D (54%)

I would like to keep using W3TC of course, but would also like to resolve the Fontawesome problem with Firefox and Chrome.

I’ve tried all of the remedies including COR (site is not using CDN), adding .htaccess file items, etc. with no change.

I’ve attached supporting screenshots and will post credentials in a private reply.

TIA!

[Rich AParticipant]

Additional screenshot:

[Rich AParticipant]

This reply has been marked as private.

[Rue NelModerator]

Hello There,

Thanks for writing in and the very detailed information. Are you using CloudFlare or may have installed a caching plugin like WordFence, W3 Total Cache or WP Super Cache? Please keep in mind that after doing every updates, always remember to clear all caches when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

Please let us know how it goes.

[Rich AParticipant]

Thanks for responding. Can you please read my original post? It answers all of your questions.

I’ll look forward to your advice.

Best wishes.

[Paul RModerator]

Hi,

I can see the icons on my end.

http://screencast.com/t/0s6eJMEySeE

Please clear your browser cache and check again.

Thanks

[Rich AParticipant]

Hi Paul,

Thanks for looking. Still not sure what the issue is. All browsers cache/history cleared and even when logging in using a proxy the FA icons do not appear in Firefox and Chrome (at least on my end).

Again, I can disable minify in W3TC and all FA items are immediately visible so it’s not a caching problem.

Any other thoughts would be welcome.

TIA.

[Nabeel AModerator]

Hi again,

Please add the following code in your Child theme's style.css file:

@font-face {
  font-family: 'FontAwesome';
  font-style: normal;
  font-weight: 400;
  src: local('FontAwesome'), local('FontAwesome'), url(https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/fonts/fontawesome-webfont.woff) format('woff');
}

Let us know how this goes!

[Rich AParticipant]

Hi Nabeel,

Thank you for looking into this. I already had similar code in my child theme’s style.css which should have resulted in the same outcome, however I swapped that out for the code you suggested. Unfortunately no change.

Ultimately it appears that there’s a conflict with W3 Total Cache and X Theme’s minify scripts.

That said, it really looks like X Theme is overkill for this website’s minimal requirements. I’ve tried using several other less robust, more basic themes and they all worked fine so I’m going to go ahead and switch to a different theme and save the X Theme license for a more appropriate website.

Thanks again to everyone that took the time to review this, it’s truly appreciated.

Best wishes,

Rich

[RadModerator]

Hi there,

X theme’s minified scripts are static files, it doesn’t change (unless there are updates). And a non-changing file should have no effect on W3 Total cache since it will stay the same. X theme doesn’t have a minify feature either.

Minified files are different from minify feature. Minified files are pre-compressed files, it doesn’t need processing like a minify feature that most optimization plugin has.

It may be related to something else, maybe transients or likes.

And you’re always welcome, see you gain next time 🙂

Thanks!

[Author]

Posts