Might be worth reaching out to the site's creator -- info taken from their site [https://zu1k-com/about/]:

"If you have any questions to communicate with me, the preferred way is to comment directly in the comment area of the corresponding blog post, and I will receive an email notification

In addition, you can also reach me in the following ways:

Email: i@zu1k.com

Twitter: @zu1k_lv

GitHub: @zu1k

Keybase: @zu1k

Matrix: @zu1k:mozilla.org

My PGP public key can be obtained at https://pgp.zu1k.com or hkps: //keyserver.ubuntu.com

( 2A65 F6F3 1EDA D922 D7E7 E97B AE38 1A8F B1EF 2CC8)"

They act like gatekeepers. Along with blocking, as in this case, they make browser assumptions that force visitors to use one of the most recent mainstream "approved" and unmodified browsers.

For other browsers, they serve "Checking if the site connection is secure" with javascript fingerprinting and a captcha, and sometimes even solving the captcha won't let me in. i have also seen frontends misbehaving due to them not expecting cloudflare error response codes.

Some dvelopers apparenly just blindly enable cloudflare and don't care. :(