On 18 November 2026, the day before the official release date and with the first players already in the game, we measured the game's official page. It is probably the most visited page of the week, which makes it a good place to see how something that is not allowed to fall over gets built.
We found two things. The game's page is fast, and it is made with the same technology we use ourselves. The company's main homepage, one click away, weighs more than ten times as much.
If you came for the game rather than for websites: we also made a page that tells you how much of your life you spent waiting for GTA VI.
How we measured
We loaded rockstargames.com/VI six times in an automated Chromium browser: three times in a 1440 by 900 desktop window and three times as a 390 by 844 phone. Each time the browser started empty, with nothing saved. We also measured the main homepage once, on desktop.
The measurement was taken on 18 November 2026, at around 16:55 Romanian time, over a single fast connection that reached the internet through a node in Italy.
Three limits, so it is clear what the numbers say and what they do not:
- This is a lab measurement. A real phone on mobile data will be slower.
- It is one place and one hour. From another city or at another time, the numbers can differ.
- It is not a load test. We do not know how the site behaved under launch-night traffic.
The GTA VI page, on desktop
- 1.1 s
- until the main content appears (median of three loads)
- 3.8 MB
- for the whole page, in 156 requests
- 27 of 32
- images delivered as AVIF
What the GTA VI page does well
It is finished before you ask for it. The server answers with a header saying the page is prerendered, with Next.js. That means it is not rebuilt for each visitor: it is made once and sent as a file. The first response arrived in about 0.3 seconds, and the document is 113 KB.
For a page that millions of people open in the same hour, this is the choice that matters most. A server that only hands out files holds up far longer than one that computes every page.
It sits behind a content network. The files are delivered through Akamai, meaning from a server close to the visitor rather than from a single one far away.
The images are in a modern format. Of 32 images, 27 arrived as AVIF, a format that keeps the quality at a fraction of a JPEG's size. The largest is 248 KB.
Nothing jumps on screen. Text and images do not move while the page loads. The indicator that measures this was practically zero: 0.001 on desktop and 0.015 on the phone, where the threshold considered good is 0.1.
| Desktop | Emulated phone | |
|---|---|---|
| First response from the server | 0.30 s | 0.24 s |
| First visible content | 0.82 s | 0.75 s |
| Main content | 1.12 s | 1.31 s |
| Page weight | 3.8 MB | 11.3 MB |
| Requests | 156 | 173 |
These are medians of three loads each. "Main content" is what Google calls LCP, the moment the largest element on screen appears. The threshold considered good is 2.5 seconds.
What not to copy
Fast does not mean light. The page is fast because it is well built and because we measured it on a good connection. A few things would be expensive on an ordinary company's site:
- 1.4 MB of JavaScript, in 51 files. That is code the phone has to download and run. On an older phone you feel it.
- 11.3 MB on a phone. Of that, 7.6 MB is video. On Wi-Fi it does not matter. On mobile data it does.
- 17 requests to other companies, 536 KB in total: the cookie banner and the analytics tools. That is almost as heavy as all the images on an ordinary page.
Rockstar can afford this. People who open that page want to watch the trailer and they are patient. A customer looking for a plumber on a phone is not.
The homepage is another story
One click away, rockstargames.com is built differently. The document the server sends is 2 KB and nearly empty. The rest of the page is assembled in your browser, from 135 code files.
On our single load, on desktop:
- the main content appeared after 5.2 seconds;
- the page requested 241 files;
- it downloaded 44 MB, of which 39.5 MB was video.
Same company, same brand, same content network. The difference lies in how the page is built: one arrives finished from the server, the other is put together in your browser. The first appears in a second. The second, in five.
A detail for anyone who read our article on the PHP version calendar: one of the services behind the homepage publicly identifies itself as PHP 8.2.35. That is exactly the version carrying the 21 October fixes, so it is up to date. It is also the branch that leaves the calendar on 31 December 2026. The deadline is the same for everyone.
Our own site, measured the same way
It would be unfair to measure others and not ourselves. We put the tangled-design.ro homepage through the same procedure, in the same hour:
| Desktop | Emulated phone | |
|---|---|---|
| Main content | 0.52 s | 0.42 s |
| Page weight | 1.0 MB | 1.0 MB |
| Requests | 55 | 55 |
| JavaScript | 240 KB | 240 KB |
Our page is far simpler than theirs and has no video, so this is not a comparison between equals. It shows one thing only: the rules are the same at any size. A prerendered page, images at the size they are displayed, as little code as possible sent to the browser.
What to take from this for your company's site
Important pages are generated in advance
The homepage, the service pages and the articles have no reason to be computed on every visit. Ask whoever builds your site whether pages are served as ready-made files or built on each request.
Images come in a modern format, at the size they are shown
AVIF or WebP, not the 6 MB photo straight from a phone. It is the cheapest speed improvement there is.
Video only where it earns its place
A film that starts by itself on a phone can weigh more than the rest of the site put together. If it does not sell, it does not belong at the top of the page.
Count what you load from others
Cookie banner, analytics, chat, advertising pixels. Each one is another company your site's speed depends on.
If you want to understand the numbers above better, we wrote separately about what a fast website actually means.
Frequently asked questions
What is the GTA VI website built with? On 18 November 2026, the page at rockstargames.com/VI answered with the headers of a Next.js site prerendered on the server, delivered through the Akamai network. The main rockstargames.com homepage is a different, older application that is assembled in the browser.
How fast does the GTA VI page load? In our measurement of 18 November 2026, the main content appeared in 1.1 seconds on desktop and 1.3 seconds on an emulated phone, as the median of three loads. The whole page weighed 3.8 MB on desktop and 11.3 MB on the phone.
Did Rockstar's site hold up at launch? We do not know. We measured on 18 November, the day before the official release date, and did not run a load test. We can only say how the page is built and why that kind of build copes well with heavy traffic.
Our own measurements, taken on 18 November 2026. Grand Theft Auto and GTA are trademarks of Take-Two Interactive. We have no connection with Rockstar Games or Take-Two.
