Info about solution and how ti works on apiunit
Speed up your website by loading ApiUnit from CDN/Cloudflare:
ApiUnit is hosted on servers spread across the globe - scripts are loaded faster because they are served from the nearest locations to the end user. If the same version of ApiUnit has already been downloaded (even on a different website), it is loaded from cache. CDN/Cloudflare reduces the number of HTTP requests handled by your server so it speeds it up as well!
URL Structure
The URL structure for ApiUnit is as follows:
// cdn.apiunit.com / [application.name] / [version.number] / [distribution.type] .js
example:
cdn.apiunit.com/newsletter/1.1.0/min.js
cdn.apiunit.com/newsletter/1.1.0/source.js
OR
cdn.apiunit.com/newsletter-1.1.0-min.js
cdn.apiunit.com/newsletter-1.1.0-source.js
The following distributions (see comparison table) are available:
basic - the Basic preset
standard - the Standard preset
standard-all - the Standard preset together with all other plugins created by ApiUnit*
full - the Full preset
full-all - the Full preset together with all other plugins created by ApiUnit*
classic - the Classic editor
inline - the Inline editor
balloon - the Balloon editor
balloon-block - the Balloon block editor
decoupled-document - the Document editor
- Plugins not included in a preset need to be enabled with config.extraPlugins.
serve the versions in structure:
over nodejs. app:
- use github repository
- generate the filesystem for each version of project use pattern:
https://wp-rocket.me/blog/reduce-http-requests-speed-wordpress-site/
- Minifying and Combining HTML, CSS and JavaScript Files
- Fix Render-Blocking CSS and JavaScript Files
- Deleting and Optimizing Images
- Evaluating and Reducing External Scripts
There are also advanced file optimization options that can significantly improve site performance including:
Minify HTML – Minifying HTML removes whitespace and comments to reduce the size.
Combine Google Fonts files – Combining Google Fonts will reduce the number of HTTP requests.
Remove query strings from static resources – This removes the version query string from static files and encodes it into the filename instead, to help improve your GTMetrix score.
Minify CSS files – Minifying CSS removes whitespace and comments to reduce the file size.
Combine CSS files – This merges all your files into one, reducing HTTP requests.
Optimize CSS delivery – Optimizing CSS delivery eliminates render-blocking CSS on your website for faster perceived load time.
Minify JavaScript files – This setting removes whitespace and comments to reduce the file size.
Combine JavaScript files – Similarly to combining CSS files, combing your JavaScript files helps reduce HTTP requests by combining your site’s internal, third party and inline JavaScript.
Load JavaScript deferred – Loading JavaScript deferred eliminates render-blocking JavaScript on your site and can improve load time.
You can also integrate the CDN of your choice for even more caching superpowers. There are loads of options like Batman’s utility belt, except WP Rocket is so much easier to set up and implement.
Using a CDN can further speed up how quickly your pages load for users. A CDN is a network of servers, usually located at various sites around the world. These servers cache the static content of your site, such as images, CSS and JavaScript files. When someone lands on your site, the static content is served from the server located closest to the user’s physical location. Shorter distances to the server means faster data retrieval. But keep in mind that if the majority of your site visitors are local, a CDN isn’t necessary – CDN’s are more suited to websites that have international traffic.
With WP Rocket, you can integrate your website with CloudFlare, a popular CDN. Go to the “CDN” tab in WP Rocket to enable CloudFlare and then add your account. For more, check out WP Rocket’s documentation on how to use CloudFlare with WP Rocket.
While Cloudflare is a useful free option for users with small websites, larger websites should invest in a premium service, such as MaxCDN (now StackPath), KeyCDN or even an open source option like jsDelivr.
A cache temporarily stores content for faster retrieval on repeated page loads.
Using a cache for storage is called “caching.”
Below are the differences between each kind of cache, summarized for clarity:
A site cache saves certain types of content and is controlled client-side.
A browser cache saves the same types of content, and is saved on your computer, through your browser, and is controlled by the browser. It’s a type of client-side cache.
Server caches store content, code, queries, or similar data on a server, or multiple servers, and is controlled by the server instead of a browser (client), or user.
A server cache is a type cache that’s related to site caching, except instead of temporarily saving content on the client side, it’s stored on a site’s server. Server caching is also fully handled and amistered on the server without any involvement of the end user, or a browser.
Types of server caching include, but aren’t limited to:
Object caching – Storing database queries in a server-side cache for quick retrieval on subsequent page loads.
CDN caching – A Content Delivery Network (CDN) is a cluster of servers that are geographically located all around the world. They cache content that’s loaded using the server that’s closest to the end user for much faster loading times.
Opcode caching – PHP code is compiled between each request, then stored in a cache so it’s executable faster on repeated page loads.
When someone visits your site, Cloudflare will take your static content and store your content on Cloudflare’s network of servers around the world. Then, for future visitors, Cloudflare can serve up that cached static content from the Cloudflare edge server that’s nearest to each visitor.
Because of how this approach works, all of your content will still load from yoursite.com. This is different from how a lot of other CDNs work, where it’s common to serve your content from a separate URL like cdn.yoursite.com.