MinimalCSS Post Types Tab

The Page Inventory tab shows the individual pages, posts, and other public content items that MinimalCSS can optimize.

This is where you review which pages are available for CSS generation, check their optimization status, generate CSS for specific pages, and exclude pages that should not be optimized.

What the Page Inventory Tab Is For

The Page Inventory helps you manage optimization at the individual page level.

Instead of applying optimization blindly across your entire site, you can review each item, test important pages first, and decide which pages should use optimized CSS.

Depending on your site, the inventory may include:

  • Pages
  • Blog posts
  • Landing pages
  • WooCommerce products
  • Custom post types
  • Other public frontend content types

The exact items shown depend on your WordPress site, active plugins, and the content types available on your site.

Why Page Inventory Matters

Not every page on a WordPress site behaves the same way.

Your homepage may use a page builder layout. A service page may include forms. A landing page may include animations, sliders, or custom sections. A blog post may use a simpler layout.

The Page Inventory lets you manage these pages individually so you can:

  1. Generate optimized CSS for specific pages
  2. Test optimized pages before going live
  3. Bypass pages that should not be optimized
  4. Check which pages have already been processed
  5. Retry pages that need CSS regenerated
  6. Focus first on the pages that matter most for traffic, conversions, and Core Web Vitals

This gives you more control than a single sitewide optimization switch.

Understanding Page Statuses

Each item in the Page Inventory may show a status that helps you understand where it is in the optimization process.

Common statuses may include:

Not Optimized

The page has been detected by MinimalCSS, but optimized CSS has not been generated yet.

This is common when you first install the plugin or when new pages are added to the site.

Optimized

Optimized CSS has been successfully generated for the page.

You should still test important pages after optimization to make sure the layout, design, and interactive elements are working as expected.

Excluded

The page has been excluded from optimization.

Excluded pages will not use optimized CSS generated by MinimalCSS.

When to Generate CSS for a Page

You should generate CSS for a page when you want MinimalCSS to create optimized CSS based on that page’s current frontend layout.

Start with your most important pages first, such as:

  • Homepage
  • Main service pages
  • Landing pages
  • Product pages
  • Contact page
  • High-traffic blog posts
  • Important conversion pages

After generating CSS, compare the optimized version with the bypassed version to confirm that everything still looks and works correctly.

Testing Optimized Pages

After generating CSS for a page, test the page before relying on it for visitors.

Review the page on desktop and mobile, and check important elements such as:

  • Header and navigation
  • Mobile menu
  • Hero section
  • Buttons and calls to action
  • Forms
  • Sliders or carousels
  • Tabs and accordions
  • Popups
  • Image galleries
  • Footer
  • WooCommerce or membership elements, if applicable

If the optimized version looks correct, you can continue optimizing more pages.

When to Exclude a Page

Some pages may not be good candidates for CSS optimization.

You may want to exclude pages that are highly dynamic, sensitive, or difficult to test.

Examples may include:

  • Checkout pages
  • Cart pages
  • Account pages
  • Login pages
  • Registration pages
  • Membership dashboards
  • Highly personalized pages
  • Pages that change layout based on user status
  • Pages with complex third-party widgets
  • Pages that are not publicly accessible

For WooCommerce and membership sites, be especially careful with pages that affect purchases, accounts, payments, or user access.

When to Regenerate CSS for a Page

Regenerate CSS when the design or structure of a page changes.

This may be needed after:

  • Editing the page content
  • Changing a page builder layout
  • Updating a template
  • Modifying the header or footer
  • Changing global styles
  • Updating theme settings
  • Adding or removing frontend plugins
  • Changing forms, sliders, galleries, or interactive sections

Regeneration helps ensure that the optimized CSS matches the current version of the page.

Bulk Generation

The Page Inventory may include options to generate CSS for multiple pages.

Bulk generation is useful once you have tested several important pages and are comfortable with the plugin’s output.

For a new setup, we recommend generating CSS in smaller batches first. This gives you a chance to review results and identify any pages that may need to be excluded.

After you are confident with the results, you can use broader generation options to process more pages.

Best Practice Workflow

A safe Page Inventory workflow looks like this:

  1. Open the Page Inventory tab.
  2. Find your homepage and other important pages.
  3. Generate CSS for one or two key pages first.
  4. Test the optimized pages.
  5. Confirm that desktop and mobile layouts look correct.
  6. Exclude any pages that should not be optimized.
  7. Generate CSS for additional important pages.
  8. Review failed or skipped items.
  9. Use bulk generation after the most important pages have been tested.

This approach helps you improve performance while reducing the risk of unexpected layout issues.

Troubleshooting

A page is missing from the inventory

Check whether the page is published and publicly accessible. Drafts, private pages, password-protected content, or unsupported content types may not appear in the inventory.

A page failed during generation

Try generating CSS for the page again. If it continues to fail, check whether the page redirects, requires login access, blocks requests, or depends on conditions that prevent MinimalCSS from viewing the page normally.

The optimized page looks broken

Compare the optimized and bypassed versions. If the issue only appears with optimized CSS, regenerate CSS for that page. If the issue remains, exclude the page while you review the layout.

I changed the page design

Regenerate CSS for that page so MinimalCSS can create optimized CSS based on the updated layout.

I am not sure whether a page should be optimized

Start by testing the page individually. If the page is important, dynamic, or part of a checkout, account, login, or membership process, consider excluding it unless you can test it carefully.