I use around 40 KB of JavaScript (transferred size). It’s self hosted. I don’t load JavaScript from other domains, and I have a very strict Content Security Policy.
My website’s performance and security should therefore be pretty good. I don’t think it’s a problem that I use client-side rendering, but I’m willing to change my mind if I’m presented with a good argument.
I'm sure that you trust your security and speed to be good, but for a random Internet user, your website is just a random website on the Internet, without any special deviation from the mean.
Those who consider the average JS website slow/insecure/tracker-ridden will just skip it if they see no content. Ain't nobody got time to do audits just for one article, and the leap of trust to drop the shields needs to be earned too.
I don't necessarily consider this a good argument. It eventually depends on how important those people are to you as the audience.
This is a good point. My notification “️This website requires JavaScript to render” is not sufficient. I should improve it to describe the website in more detail, provide contact information, include a screenshot, explain what JavaScript code is loaded if enabled, and other useful information.
8 comments
[ 4.0 ms ] story [ 33.9 ms ] threadMy website’s performance and security should therefore be pretty good. I don’t think it’s a problem that I use client-side rendering, but I’m willing to change my mind if I’m presented with a good argument.
Those who consider the average JS website slow/insecure/tracker-ridden will just skip it if they see no content. Ain't nobody got time to do audits just for one article, and the leap of trust to drop the shields needs to be earned too.
I don't necessarily consider this a good argument. It eventually depends on how important those people are to you as the audience.
The main content should always be visible upon page load.