A couple issues…

Thanks for your report and the kind 5-star review even though you opened this support thread!

1. These entries seem to be caused by the browser trying load the files referenced by the CSS sourcemap. Sourcemaps are very helpful for debugging, that’s why these are included. Browsers usually only load them when you open the developer tools on the website.
Since you are using a plugin to log 404s, it’s probably the easiest solution to just exclude the messages for files inside the user-feedback/css/src folder.

2. You shouldn’t need to care about that extra <div> in the first place, but the container not being removed is actually a bug. Thanks for reporting this, it will be fixed in the next update.

Welcome and thanks!

Hey, I don’t know how farther you can really take this plugin, but perhaps there are some premium type things you can do to it.

If so, feel free to update me on that. It is nice.

I’ll link the author about this for the 404 and mention to them to that it would be nice to exclude certain paths in the 404 monitoring.

Thanks for the update! Appreciate it!