OFF on the Optimization page (Control it in a Page Rule) LOCATION: Speed > Optimization Auto Minify More so for the paid version that allows URL forwarding.
I haven’t researched the best use configuration for WooCommerce on Cloudflare Free as yet, but these rules should work just as well in WooCommerce or any other eCommerce plugin for WordPress.Īlso, this isn’t a WordPress beginner article, but if your willing to try, and search out the details, you’ll figure it out. NitroPack solves many other complex performance issues beyond just delivering page structure to client devices.This guide is focusing on a WordPress site configuration for Cloudflare in general.APO does not help with visualizing pages on client devices.This removes trips to the origin server, improving metrics like TTFB and possibly FCP APO lets you cache dynamic content on Cloudflare’s edge locations.They can work together, as long as you go through the configuration process NitroPack and Cloudflare’s APO do very different things.If you want a more technical deep dive, check out our article on How NitroPack Works. Here’s a screenshot of our current feature set for a bit more context on what our service actually does:
NitroPack deals with these and all other site speed issues automatically. Without this technique, browsers load all images on the page, regardless if the user actually wants to see them.
Lazy loading helps the browser load only the images that visitors are currently looking at. Without a resource loading mechanism, this process takes tons of time, hurting the visitor’s experience Browsers must load, parse and execute all CSS and JS files before rendering a page.
Often the biggest reason for slow load times, images must be resized, compressed and converted to the right type This is where NitroPack offers a ton of other benefits.įor example, here are three crucial performance problems that APO doesn’t solve: If you deliver the page structure to the client but can’t visualize it fast, your website is still slow. However, the bigger challenge with site speed is actually visualizing pages on client devices. It does that by caching and providing the HTML from the edge location nearest to the client. If you’re interested, check out Cloudflare’s article, specifically the section on how APO works.įor now, just remember that APO’s only purpose is to deliver content to client devices faster. We won’t go into it, as it’s not important right now. There’s a whole process that goes on behind the scenes here. As a result, metrics like Time to First Byte (TTFB) and First Contentful Paint (FCP) may improve. This mechanism removes unnecessary trips to the origin server. The benefit of using it is that your HTML can be cached and served from Cloudflare’s edge network. This service caches dynamic content with the help of Cloudflare Workers. Next, let’s talk about what APO actually does. That’s why you can use them simultaneously, as long as you configure NitroPack and Cloudflare to work together. īoth services help with site speed but do so in entirely different ways. NitroPack and APO don’t do the same thing. To start, let’s clear up the biggest misconception on the topic: People sometimes get confused about how NitroPack compares to Cloudflare’s Automatic Platform Optimization (APO) service.