Google Chrome's page performance audit suggests to put CSS imports before JS imports in the header, to allow for parallel downloading of CSS and JS files.
However, I have noticed that this causes Firefox to clear the window before rendering the new page when navigating to another page. So if I have CSS before JS, Firefox will clear the old page, show a white screen for half a second and then show the new page. If I put JS before CSS, the old page will stay on the screen until it is replaced by the new page. The latter obviously looks much better, since the header stays on screen permanently. Chrome doesn't seem to have these issues.
Is this a known issue? What is the recommended course of action here?