Because I cant find an appropriate category, I just gonna drop this here:
Did a soft launch of a client site yesterday; its running CP v2 + WooCommerce (actually Re:Commerce) + site designed from scratch + massive web performance optimizations + a wagonload of other things.
It had to be launched pre-mature, because it was initially scheduled for official launch in May or July this year, but the clients original shop finally took its last breath about 2 weeks ago; it was already partially broken, but could somehow be coaxed to work a bit further.
Now, the webhosting company tried to upgrade PHP to a still supported version (its been running on and off with PHP 5.6 and 7.x), and thus … the end of the line was reached.
Beware: Website is purely in German so far. Originally planned was to either use Bogo (which would require a fork = CP version) or use a very simple combination of translated pages, ACF Pro + a bit of custom programming. That may still happen, but for now, its German only.
Currently, I’m way too busy with work to be doing a proper release, but with the IRL usage within an actual working shop, this certainly is prone to change. Ie. there is gonna go a bit more work into it, as I intend to backport or “get inspired by” parts and elements existing in the current WooCommerce iterations.
Right now, its pre-release level, mostly cosmetic changes, partially in labeling / naming, and making sure its functioning as intented.
Its properly optimized as well, using a combination of WP Super Cache, Autoptimize and proper image optimization.
With further optimization, it might even load faster / be more responsive while still loading. The main goal was getting the site online and working, so that wasnt the main priority.
*** some people still load their “script” tags just before the closing “body” tag, though this practice is not necessary with “defer” or “async” as this tells modern browsers when to load scripts ***
== PRECONNECT ==
If referring to remote content such as: https://code.jquery.com for instance, there’s also an opportunity “preconnect” to these domains which reduces DNS lookup requests later.
Thanks, but I cant seem to figure out what you’re referring to.
There is no “doubled” generation of the viewport meta tag.
Also, the preloading from fonts, scripts etc. from CDNs and external sources is blocked, because Consent Management.
In the last few, there were several … Abmahnwellen … because of embedded external “non-european” media, esp, Google Fonts.
This is a German site, so we’re in Europe, hence a lot of data protection laws. Hence we are using a Consent Management plugin, that makes all of this legal and sound.