LAUNCH DEAL — LIMITED Das Nest Lifetime 499 € 149 € Get the deal →
KakapoWP KakapoWP
Log in Get Lifetime
Kakapo Performance

Critical CSS

What the top of the page needs sits in the head. The rest follows afterwards.

For each template, the kakapo fetches a real sample page from your site, reads the local stylesheets linked there straight from disk and checks every rule against the document. What is needed above the fold goes inline into the head; the evaluated stylesheets load afterwards, without blocking rendering. No browser is involved: “visible above the fold” is a disclosed approximation based on the order of the elements, and when in doubt it keeps a rule in. That is why there is a preview, a test mode and a toggle per template.

Get lifetime — €149All Performance features
All eight plugins included in the lifetime deal — every future one too.

Critical CSS

7 templates · each template with its own run, its own toggle, its own preview

Test modePreview

What critical CSS offers

7 templates, each analysed and approved separately
Critical CSS inline in the head, the analysed stylesheets loaded later
Report: rules that matched no element
Preview of the same page with and without treatment
Test mode: only logged-in administrators see the change
Exclusion list for URLs, exception list for stylesheets

Here's how it works

1

Analyse the template — fetch a sample page, check the rules

2

Compare the preview with and without treatment

3

Approve the template, then switch it from test mode to live

FAQ about critical CSS

Is what's really visible at the top measured?
No. There is no browser and no viewport. All elements below body are numbered through; “above the fold” means the first 30 % (adjustable between 5 and 90) plus everything inside the registered landmarks — header area, navigation, first h1 and whatever you add. Wherever the method hits a limit, the rule counts as matched: a few kilobytes too many are more harmless than a missing rule.
Can I have the unused rules removed from here?
The list is a report, not a tool. Counting happens against one sample page per template — classes that JavaScript only sets on click, or a form on another page, do not show up there. You should delete in the theme source code, where it stays traceable.
What does the analysis run need, and what happens afterwards?
The PHP extension dom/libxml and a working loopback — the site has to reach itself over HTTP. If one of the two is missing, the analysis cannot even be started; what the reason is stands right there. If an evaluated CSS file or the theme changes later, the treatment pauses instead of shipping possibly wrong critical CSS.

More Performance features

Assets & scripts →Minify →Preload & DNS →
Ready?

Performance — pay once, use forever.

All eight plugins for a one-time €149 instead of €13 a month. Secure payment via Stripe. For the first 14 days, it's problem fixed or your money back.

Get lifetime — €149