Genericons.ttf causing mixed content erros

I’m not getting a mixed content warning on your site, and they’re in your source via HTTPS:

<link rel='stylesheet' id='genericons-css' href='https://physicaltherapyweb.com/wp-content/uploads/hummingbird-assets/22179f95bf0da0a4c1ae40445e83c643.css' type='text/css' media='all' />

Were you able to resolve this? If not, please make sure that your browser is up to date: https://browsehappy.com/

If it is not, please try updating your browser or switching to a different browser.

If it is, please do these two things:

1. Try clearing your browser’s cache and cookies.

2. Try with all browser extensions or add-ons temporarily disabled.

Please let us know how each step goes for you, and which browser (and version of) you’re using if you’re still having trouble.

I continue to get these errors in the developer console of both the latest Firefox and the latest Chrome on Mac.

I’ve cleared caches, used incognito mode, etc.

I also get these warnings when I use services like whynopadlock.com

Hi again James.

You are correct that I am properly linking to the css using https.

However, it appears that when Jetpack is serving this from the CDN, it is serving it over http, not https.

Ok, please try deleting Jetpack specifically from the Plugins section of your blog’s Dashboard: https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack

This will clear out Jetpack’s settings, and it should work properly after a reinstall.

Thanks James. That worked for getting rid of the issue with genericons.ttf loading over http and causing mixed content errors.

Unfortunately, it seems to have killed my pagespeed. I did a test on Google Pagespeed Insights before doing the uninstall – reinstall. Before I did it, my mobile score was 89/100; very close to excellent. Now my score is 4/100; very close to the worst possible score.

Do you have any idea why a reinstall of Jetpack might have this effect? Any suggestions on getting back to where I was prior to the Jetpack reinstall?

If I had to guess based on this thread, maybe it’s because the webfont is finally loading.

However, that should only add a fraction of a second, and not kill your score that much.

I’m not seeing anything terrible out of place with the speed tests I prefer:

https://gtmetrix.com/reports/physicaltherapyweb.com/B15jmWqq

https://www.webpagetest.org/result/190918_JH_ce1866aff12a68f2a99cb7a84d41e4d2/

And your PageSpeed score is definitely lower than 89, but not a 4 now: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fphysicaltherapyweb.com%2F

Personally, I don’t really trust PageSpeed all that much, I find it buggy, and it often suggests turning on things that Google’s own mod_pagespeed is already doing.

Make sure that you’re only using the Jetpack modules you want.

Most of Jetpack is designed to speed up your site by taking load off of your server, like our site accelerator https://jetpack.com/support/site-accelerator/ or stats https://jetpack.com/support/wordpress-com-stats/ subscriptions https://jetpack.com/support/subscriptions/ and related posts https://jetpack.com/support/related-posts/ which are all processed on our end (rather than hammering your database as these features traditionally do).

With that said though, the more Jetpack modules you add, the more your site has to initially process, just like it would if you added a separate plugin for the features, so always make sure you’re only using the features you want.

Regarding overall speed and load, here’s an excellent independent report: https://mattreport.com/jetpack-speed/

Thanks James. The deleting and reinstalling Jetpack seemed to only be a temporary fix. The genericons.ttf problem returned again shortly after.

I eventually fixed the problem by installing the Really Simple SSL plugin. I don’t like installing plugins if I don’t have to. However, I couldn’t find any other solution that worked. My PageSpeed seems to be fine again, at least for desktop. I do use GMetrix regularly as well as webpagetest.org periodically for speed testing.

Anyway, the issue is resolved for now. I’ll try to determine what Really Simple SSL did that made the difference and implement that alone.