aaronsingler

Thanks for the follow-up. I’ll reach out to you via email.
For the benefit of this post, I’ll post more info on the areas where I (a developer) got hung up.

The Cache Settings > Cache area has the ‘Exclusions’ for addressing files that are breaking from the optimization.

See screenshot. https://prnt.sc/0VbHqulJTHe5

The documentation page for this is here: https://support.nitropack.io/en/articles/8390302-excluded-resources

I reccomend adding more examples of how to add these exclusions with examples of js, css, and various combinations. Make sure to include info on how to structure the selector. Example, is it relevant to the root, or are how much of the url is required? Put in more examples of wild cards (*).

Provide more info on how to use the resource relation. Give examples of inline vs external file and how each affects the asset url/code selector.

The process for identifying what files need to be excluded from optimization to fix render issues needs help. Your documentation page explains how to use the developer tools console to identify dependent files when there is a rendering issue. This would be good if your plugin operated that way. It doesn’t however. Instead of getting console info that indicates what/where dependent files are, we get mostly preload files listed in the console. And to view the page source is completely useless for debugging. It’s solid script info.

So for example, let’s say the mobile menu toggle isn’t displaying on page load until the user scrolls or takes interaction. Using the search console while Nitro is active or in test mode delivers a long list of preloads, but no errors or info on what file is reacting badly to optimization. Is it jquery, or a script in the theme file, etc. No way to know.

In the Cache Settings > HTML & CSS > CSS > Generate critical CSS.
The on/off toggle makes sense. But there is an ‘include’ and ‘exclude’ css selectors. Why is there both? Doesn’t make sense to have an on/off and then have an include and exclude. Seems like only one would be needed. More info and examples/use cases. Same with the ‘Remove unused CSS’ There is an on/off and then include/exclude.

The test mode pageview count issue is a separate issue and just needs to be changed, so I won’t get into that.

Thanks for responding in ‘human’ ??

Your response sounds pretty ‘AI generated’.

Like I said, the initial tickets were answered quickly. I’ll give credit where credit is due. However, the last couple of tickets took days to get a response. These tickets were regarding two things.

The first, optimization options caused many broken items on the site.
I entirely understand that this is normal and the exclusion process is the best method to handle it. However, your UI and lack of clear instructions make this process not very intuitive.

The second was that while in ‘test’ mode the ‘pageviews’ were still be counted by all users. Meaning, while we were in test mode with nobody seeing any cached pages, the counter was still going up on pageviews and using up our limited pageviews. This resulted in all pageviews being used before we even got out of test mode. That seems like a programming mistake to me. Given the amount of testing and debugging that is needed to make sure an existing site still works after applying your optimizations, it makes zero sense for noncached pageviews outside of the test mode, would be counted at all.

You have a good start on your product, but it needs work. Your best bet is to listen to reviews (especially from your user base) and make adjustments. I don’t recommend using review responses to swat at reports of issues. Makes you look lame.

I to am getting this same issue.

Yep. Link is here: https://adventureawaitsub.com/product/the-christmas-child-redemption-river/

I also have the same problem. Checkbox not showing on free version. See screenshot. https://prnt.sc/wju7mg