I've been working on building "the fastest news website" for a few reasons:
1. I got tired of waiting for news websites to load, so I made a text-only news website that only has major news headlines.
2. I wanted to demonstrate to the world that if you want to build something really fast on the web, you can do it without loads of JavaScript.
3. I wanted to show that you can design something that looks good without having tons of images, etc.
I put together the speed page at https://legiblenews.com/speed to hold my website to be more accountable for speed, but it's also interesting to see how fast other news websites are (or in most cases, are not).
Some feedback I'm interested in receiving:
1. What's your take both on the speed ranking methodology for Legible News?
2. Are my descriptions of the metrics for a non-web developer reasonable? Example of that at https://legiblenews.com/speed/websites/associated-press, and if you click through the links on that table, you see a description like https://legiblenews.com/speed/audits/cumulative-layout-shift
Sorry ahead of time, but I can't fit all news websites on the speed report. I had to target general news websites, not ones for specific niches like HN for Tech. If there's something you think that's missing please post it, but I can't promise that I'll add it.
If you like it, please consider subscribing! Thanks!
I'm not sure that a 10% donation to Wikipedia from subscription revenue is quite enough when you are doing quite a simple reformat of all the volunteer work that goes into the current events section of Wikipedia.
You are effectively changing $9.99 for a weekly email digest of the https://en.wikipedia.org/wiki/Portal:Current_events page and giving them $1. I think if you went 50/50 on it I would probably feel it was more fair, you are adding value but I assume thats all automated.
I will give you credit for your 100 score, that page on wikipedia gets an 86 on page speed insights.