If you create the base page as static html plus css then there is no need for "detecting" blocked JS, because the page will display properly everywhere.
And if what shows with the JS blocked is all that is there, then there does not look to be any reason there should be any JS on this page to begin with.
You have two images, images display fine without JS. Although given their native size they need some css or width=/height= attributes to corral them into size. And a small amount of text (no need for JS to display text) and one form field and a submit button (both handled by basic html forms and posting to a CGI endpoint).
The only use of JS as of now is 1. storing URL source param (optional), and 2. to prevent redirection on pressing 'submit'. This one I can probably work upon. I've used tailwind CDN (was warned not to on prod). Didn't know it gets blocked too, as evident from the ugly formatting + those huge SVGs.
Comments
If you create the base page as static html plus css then there is no need for "detecting" blocked JS, because the page will display properly everywhere.
And if what shows with the JS blocked is all that is there, then there does not look to be any reason there should be any JS on this page to begin with.
You have two images, images display fine without JS. Although given their native size they need some css or width=/height= attributes to corral them into size. And a small amount of text (no need for JS to display text) and one form field and a submit button (both handled by basic html forms and posting to a CGI endpoint).
The only use of JS as of now is 1. storing URL source param (optional), and 2. to prevent redirection on pressing 'submit'. This one I can probably work upon. I've used tailwind CDN (was warned not to on prod). Didn't know it gets blocked too, as evident from the ugly formatting + those huge SVGs.
Here is how it renders with all JS blocked: https://0x0.st/HLFl.png