Sam Perrow

Hi @seedsca, thank you for the kind words.

I am developing a new version which allows the user to insert hints to specific pages, and a few other benefits. I’ve had to rewrite quite a bit of things to get it working properly, but I do have a version that can do that. I will PM you on slack about the details.

@kavitas and @mommens sorry to hear the upgrade to 1.6 was a bumpy one for you two. I had to refactor the whole plugin, modify table schema, and update the file structure to support the improved version I have been working on.
This would allow inline table editing (nearly the same as “quick fix”), ajax hint updates, and a few more improvements. Would either of you care to test out this new version? You can PM me on the WP slack channel.

I’m sorry that happened to you. I had checked how the upgrade process works for many PHP versions and didn’t encounter an issue.

But, on the bright side the newer version has several improvements over the older one, and I’m working on an even better version which allows users to input post specific hints, inline table hint editing, and ajax table updates.

Don’t use crossorigin on that request, and you should be good. I just tested it on my site and got the same error, and removing the crossorigin resolves it.
No need to use that attribute in this situation. Crossorigin’s are generally only used for preconnecting fonts.

@nicolaottomano I don’t believe there is much of a performance difference, if at all, of using hints in the HTTP header vs. the HTML head. The next version’s added benefits of using hints on a per-post basis more than makes up for the loss of that functionality.
I do see your point- and I may add an option to allow global hints to be added in the HTTP header, while post-specific hints will not have that ability.

Hi @nicolaottomano,
I have a version in development that allows users to insert hints to individual posts/pages, not just global hints. I did a lot of research on this matter, and as far as I know- at the time when HTTP headers are sent by wordpress, wp does not know what the current post is. For this reason, it’s not possible to send resource hints with HTTP headers to unique posts (afaik). If you can prove me wrong I’d be glad to reincorporate HTTP header support.
With that version in place, I don’t believe it is feasible or practical to keep support for HTTP headers.
I know the added ability to implement hints to unique posts will dramatically improve functionality and more than compensate for the removed support of HTTP headers.

Read this article for more information about why crossorigin is needed for fonts: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS.

If you are going to preload an image, you can do so, but there wouldn’t be a need to preconnect it also. What I mean is that when using preload, you must specify an entire URL for that resource, but with all preconnect hints you only need to specify a domain name. The reason is due to the different nature of the two resource hints.

I plan on releasing an updated version of the plugin which allows users to specify crossorigin, as, and the type attributes. Stay tuned!