1. Plain, small html - page size is 6.1 kb (request took 700ms for me, I guess the server side rendering is pretty fast too), css file 11kb; note html, css and js are all properly minified
2. Font-awesome and jquery at the bottom of page to not block page rendering, both loaded throught cdn (although a fallback jQuery exists)
3. Site's own js is only 5.6k
4. No large static assets, only image on page is an svg dlogo
5. Did not check with js off, but saw hints of decent fallbacks for no-script
A government site, lightning fast, try the search! No bullshit design.
A lot of that is done in the open, too.
I presume it was because prior to my comment, no one had yet explained to the guy that you don't need to deal with such a proxy setup to block ads in browsers.
So, your comment sort of made it sound like ad blocking not being too great for him, was because of Firefox and that Brave would be better at it, whereas it really just was because of a missunderstanding of the guy.
Besides that, Brave is also controversial. As much as some people have screamed bloody murder, because Eich's free speech was supposedly taken away by journalists/SJWs/Mozilla or whoever, a good other percentage of people do think that his donation was wrong and that he should have reflected on it and distanced himself from this (past) opinion.
Furthermore, many people think him basing it on Chromium was wrong. No matter how pissed off he might've been at Camp Mozilla, and no matter how much journalists would've slandered him again, if he started supposedly trying to work with Mozilla again by starting a fork of Firefox, there's just no way that you can work for 17 years on anything and then a few months later go "Actually, this competing product is better".
Chromium being Google software and him trying to sell his Chromium-based browser as privacy-friendly does not help it either. There's millions of lines of code in there with tens of thousands of design decisions, all made by the biggest data broker on the planet. You're not patching all of those out in any reasonable time frame.
Chrome is faster than FF with real world applications.
Might be Chrome pre-loading content that's behind links, which Firefox doesn't do for security, privacy, battery and not-eating-all-your-RAM-ery reasons.
I tried enabling preloading in about:config, which didn't seem to make a difference, but I'm not sure, if I did that right or if that feature is even functional at the moment. It's an experimental about:config flag after all, not a production feature.
Then again, this very much seems to be the exception on Chrome, too, so it's not exactly a reason to stop enjoying the internet without ads.
Aside from making pages with few database queries, it's about removing all 3rd party dependencies and going same-origin to speed up the front-end too.
The 2 biggest things that slow me down are auth and analytics, but on the latter I trust you use an adblocker, and for auth I have a plan.
Sadly it seems you can't register new accounts anymore because of their merger(?) with VisualPing, but their old site still functions for those with accounts and the speed is mindblowing as you can see there. I feel every website should strive to be like this.
Source of the site is here: https://github.com/CyberShadow/DFeed
Also, it runs on SQLite. I found that the most surprising of all.
Web development in D is incredibly fun. I love that I can compile HTML templates into machine code (which of courses catches template errors as compiler errors), I love how fast the result is, I love that there is a very lively collection of D packages around web development. In fact, the D package manager, dub, started as a package manager for Vibe.d, the main D web framework.