Eliminate stack css files? Pagespeed insight issue

[adkseorev]

The integrity-light.css file seems to be the majority of my pagespeed issue for a site I’m working on, kertecllc.com.

Is there any suggested fix for this? (These results in the screenshot are for the homepage).

[christian]

Hey @adkseorev,

Check out our performance guide here https://theme.co/docs/how-to-improve-site-performance

Please just note that website performance is beyond the scope of our theme support. We understand that the theme’s CSS causes that in the Pagespeed Insights but that cannot be avoided for a theme with many features. Also, website performance is set depending on a lot of factors beyond the theme. With that said, I’d recommend you check out our Boost service to help significantly improve the speed of your specific website.

[adkseorev]

Yeah so this question is directly related to your theme files, not any external plugin files.

The file is the stack file. Do these need to be loaded?

I shouldn’t have to pay an additional $79 fee to first get a report about why your theme’s css file is causing a pagespeed issues and then another $1134 on top of that to actually have you fix the speed. That’s wild.

[ruenel]

Hey Bobby,

Thank you for following up. You are asking whether the integrity-light.css stack stylesheet file must load, since PageSpeed Insights reports it as the main issue on kertecllc.com. Please review the steps below.

1. Understand the stack style – integrity-light.css holds the styling of the stack selected in your Theme Options (Integrity, Light design). It is required for as long as that stack is active. If you prefer not to load a stack style, switch to the Blank or Starter stack under Theme Options > Stack. Neither stack loads the Integrity stylesheet. Please make this change on a staging copy of the site first.

2. Style the elements with your own CSS – The Blank and Starter stacks do not include the Integrity styling, so anything that stack currently styles (typography, buttons, forms, classic elements, WooCommerce) will need to be styled with your own CSS. Add it under Custom Code > Global CSS or in your child theme. Review every page on staging before applying the change to the live site.

3. Alternative: keep Integrity and optimize delivery – If you would rather keep the current styling, WP Rocket is already active on your site, but its “Remove Unused CSS” option is not enabled. Go to WP Rocket > File Optimization > Optimize CSS Delivery and enable Remove Unused CSS. This outputs only the CSS each page uses, which reduces the render-blocking and unused-CSS warnings for the stack file. Clear the WP Rocket cache afterwards, then check menus, modals, sliders and forms.

Hope this helps.