asadkn

If you’re already using the Remove CSS feature on all of your CSS files, critical CSS won’t help. If only using on some files, using critical CSS instead will help.

The slow response can be from any number of things like plugin JS files that aren’t in excludes, or CSS files. First try by deferring and delaying load on all JS files. And apply remove CSS on all CSS files too. This should tell you if that’s the cause.

Otherwise, look into server response time.

This isn’t related to Debloat plugin and not an issue. You can google .map files to learn to more about what they are.

You’ll have to disable other optimization or cache plugin (or their features) that work on CSS such as merging or other processing.

Try again first with all other plugins disabled. Note: Some hosts have their “must-use” plugins that may also do CSS processing, so look for that too.

It usually should work with FontAwesome by default unless fontawesome is being injected in some odd way through Javascript. In that case, you should exclude classes like fa- and fab- and the CSS file (it maybe named fontawesome.css or something else). If you do have an example somewhere, I can take a quick look.

As for taking some time to load, that’s normal for the first load. And while logged in, there can be a lot of files that get CSS removed that might be a bit heavy for a shared host, depending on number of CSS files. So in debloat settings under General, you can disable it for admins.

For normal users, your cache plugin should make it all good.

I haven’t tested it.

But I doubt you’d need the remove CSS feature with Oxygen. It’s the most optimized builder already only loading CSS as needed.

Which AMP plugin are you using? Debloat works with official WordPress AMP plugin by Automattic.

That’s odd. Still not able to recreate this issue. Which other plugins you have active right now?

I will need also need full HTML code or at least the full script tag code (including src attribute) to guess what’s going on.

Ah yeah, I missed adding the changelog. No major changes. Just fixed a few PHP notices that occur with certain setting that would bother some who have debug logs enabled.

Hey,

Can’t recreate the issue in my end. Can you share a screenshot of the JS settings part so I can see the exact settings you have.

Also perhaps a link to your site.

And make sure nothing else was changed. If something else changed, let me know.

Best Regards,
Asad

As of right now, it’s not under active development but at the same time there are no known issues or improvements that can be made. If an issue arises, I will update it with a fix.

Hey,

Yes, on uninstalling, all changes will be undone (make sure to clear cache if you have a cache plugin).

Cheers.

Hey,

That’s very odd since the plugin does no modification to the original font files. Can you share the following info:

– Name of the fonts used and any special language subset.
– The specific font weights you’re seeing the issues at.
– If possible, the site where the problem can be seen.

Hey,

The plugin will fetch only the subsets specified by the original font registration by your theme (or a plugin if you use a plugin to add google fonts). Look at the HTML source code to find something similar to this:

https://fonts.googleapis.com/css?family=Open+Sans&subset=latin-ext

If it doesn’t have the subset defined, it means your theme wasn’t configured to fetch anything but latin characters. latin-ext needs to be defined in the subset by the theme.

Why does it work when not using this plugin?
Google uses unicode-range for modern browsers, adding all font definitions in single CSS file but this only works for latest browsers. They automatically fallback to older method this means your non-latin characters won’t show on old browsers. So it already working only on latest browsers only.

Good to hear you got it working. For anyone else checking this topic, F.A.Q. #1 here will help: https://plugins.theme-sphere.com/docs/sgf-pro/pages/f-a-q/

Hi Daniel,

I am quite swamped with other work right now but I will take a look at whenever I get a chance. Can you name the plugin you’re using for CDN?

I am using wp_upload_dir() in the plugin with baseurl key so not sure why the CDN plugin isn’t playing well – it should as it did with s3 offload plugin. Make sure the CDN plugin was activated before SGF and clear SGF cache from Settings > Self-Hosted Google fonts > Clear cache – and the cache plugin too.