Who has the fastest website in F1?
jakearchibald.com
jakearchibald.com
They could have team points as well as manufacturer points depending on the web servers.
Based on language and phrasing used on the blog, the author is British, and F1 has been a staple on mainstream terrestrial channels for decades, although it has seen a decline as F1 has increasingly became boring and predictable, and almost entirely dictated by team tactics and car reliability.
We'll see what this season holds (since at this time last season it still looked like it would be a good fight to the end), but I'm optimistic. If Bottas can retain his form from Australia (I think the wind really threw him off in Bahrain), and if Vettel can get his head on straight, we could see a legit four-way fight for the title.
If you weren't around in the days of Senna then you really have missed the best of times.
Always felt kind sorry for Mansell as you felt that he is on the verge of getting World Championship but never really got there on a consistent basis.
Although I rarely watch motorsports these days, I'm much more inclined to watch something like MotoGP than F1.
I fully appreciate that the heady, noisy, dangerous days of F1 are over, as driver & fan safety, as well as hybrid engines take over the sport. But still, exciting wheel to wheel racing can happen, as evidenced by the race in Bahrain over the weekend.
This year at least, the teams seem on a more even spread, and it is hard to pick a runaway winner for the drivers or constructors championship.
Also it's now only live on Sky, which requires a minimum ~£30/m subscription; probably doesn't help viewing figures.
In contrast, for the last few years, only half the races have been free to view. As of this year, only one race a year is available to watch for free.
Shame, as the last race (Bahrain 2019) was possibly the best race I've seen in years.
In the movie "Grand Prix", the greatest shot in it was one continuous shot of a lap in the Monaco race, from the driver's POV. No added music, just the engine sounds. I wish that documentary would add such a scene for each track.
https://www.youtube.com/watch?v=xTezG7LJL5o
Race highlights with some onboard vision:
https://www.youtube.com/watch?v=nLExSMdjlUg
The onboard lap comparison videos are also good, like this one from last year's US grand prix:
https://www.youtube.com/watch?v=GH-Uv6OKeDc
You can see where time is being gained and lost throughout the lap.
This is quite sad, because there was a lot of legitimate on field drama last year, that they could have chosen to show instead. I'd even go so far as to say it was a mockumentary rather than a documentary.
Literally, the only good thing was that it seems to have been entertaining enough for a lot of people, that F1s viewership has increased quite a lot.
It's possible some of the sites would be faster from the UK or elsewhere, but ttfb was the least of these site's problems
CA: so now you need an engine and a driver. CH: you are spending the money you don’t have for the drivers. CA: I have a lot of money.
The build up to this was Red Bull announcing they are not going to use Renault engines in 2019 but before they knew they’ll lose the driver to Renault.
- bad project management from the client (they often don't care about technical quality or rather can't evaluate it)
- bad project management from the web contractor (they often don't care about technical quality or rather can't evaluate it)
- the web agency has too many projects due and needs to deliver asap
- exhausted & mismanaged dev teams (+ freelancers) which are constantly working on short lived projects, which are a mess because nobody doesn't really care
Also I am amazed over and over again how a lot of managers (or people) will lie straight to your (or the clients) face if they can thereby save their ass.
I used to work at an ad agency several years. We were locked into Wordpress or Drupal with Bootstrap and some base plugins for sliders as well as a ton of stuff for 'SEO' and tracking. The amount of time allotted to deliver the project was actually pretty small. You would get a mild scolding if you even bothered to look at performance. A lot of these things are a part of the theme/plugin out of the box and may not be optimized, but the images and the content was usually uploaded by an intern or whatever and they never bothered with image optimization.
This kind of work is typically outsourced, since it's not a core competency for the company. So the company would be contracting some web development agency which builds a homepage and potentially also hosts it. There are contracts and specifications in place around what needs to get built. In the web development domain I don't think the outsourcing aspect is a big plus or minus on execution ability. There will be some good and some bad agencies around - and an internal team might not really be doing a better job.
Regarding performance: They mostly wouldn't even recognize. The work is presented with some fast connection and device, so it's not visible. And even if it would be, the people responsible for it (or even the leads of those companies or teams) are not that tech savy and will just accept it as the current state of the art.
There will be far bigger discussions around other things than performance. E.g. which images and fonts are to be used, how trademarks and the brand are represented, etc.
we actually care about that, but our options are limited. of course, if the performance is heavily affected we can tell them to buzz off, but usually it's not a single tool that generates the problem, but the sum of all of them.
on the other hand, i'm aware that there's some value added by those tools.
One thing that wouldn't surprise me would be to see that the websites for some of the companies mentioned in the article are running on SharePoint. --If tuned properly, it can be quite fast, but like other solutions, it can also feel bloated and slow if it's not prioritized.
That shows it's not always the massive JS libs that are the problem. It's also a lack of knowledge and interest from those who build and maintain the site.
True, the QAs job is to test it delivers as requested, UX if it is usable by the end user, ops that is is not heavy on resources etc. But it is a joint responsibility between all and especially the developer and designer that they deliver quality and not cut corners.
If there is an ultimate responsible it would perhaps be the project/product owner who would decide what is important and how much time and effort they should spend on which parts. But still it is not just pass-the-buck, they are all responsible.
I guess the results would be very different when using 4g? and that the real problem is that the author is using a unrealisticly slow connection.
Also, it's a mistake for developers to assume that everyone is on 4g, and that those on 4g are experiencing good speeds.
Even in London, if you're at a train station that's hit by delays, connectivity grinds to a halt as everyone starts looking for alternative transport.
In the big cities in India, 4g is pretty much always like that.
Personally for simple content-based sites I find anything above ~half a second is already quite bad, assuming a reasonable underlying connection to the server (ping < 30 ms).
I'm a cofounder of PacketStream.io
We'd love to see you re-run these tests from our network of global residential proxies to see results from different locations around the globe. Our product lets you select a geolocation to exit from as part of the request.
If you're interested in free credits to run some more speed tests send me an email: ronald at packetstream io
Companies do a ton of market research, if there were some edge to optimizing your company’s site, I suspect there would have been 10 books on the subject by now.
Truth is they don’t do it because they don’t need it. Plain and simple. What exactly would they get other than HNs approval?
Your comment struck a cord with me because it’s a conversation I have had in IT millions of times.
The real wisdom in any type of endeavor is knowing when it’s ok to cut a corner and when there is absolutely no room for compromise.
Just mentioning it as it's quite a simple, fast, free change that doesn't cost any developer hours.
Yes.