The flags of Google Chrome are defined as a series of commands that allow us to interact with some hidden functions of the browser. As Google itself indicates on the Chrome flags page, its use is related to experimental functions that have not yet been implemented in the browser. Many others are destined to configure Chrome beyond the options that the application itself offers natively.
Among the possibilities that the browser flags offer us, we find that of accelerating and improving the speed of Google Chrome without resorting to third-party extensions , and this time we have compiled several of them to apply in any version of Chrome, even in the mobile phone.
First of all, how to access the Chrome flags?
Accessing the Chrome flags is very simple. As simple as typing the following address in the browser's address bar:
- chrome: // flags /
Then, Google Chrome will show us a list with all the commands to apply, which will depend on the version we have.
enable-parallel-downloading
Although the activation of this flag does not improve the speed of the browser directly, it does increase the speed of the downloads through the parallel download of packages , which directly affects the download speed that Chrome is capable of offering in based on the speed that we have contracted in our Internet connection.
To activate the command in question we will write the following address in Chrome:
- chrome: // flags / # enable-parallel-downloading
Then we will mark 'Enabled' to activate this feature.
proactive-tab-freeze-and-discard (proactive tab freeze)
The memory expense that Chrome causes in the system is well known. Much of the blame lies with the tabs that are stored in the computer's RAM memory to speed up their access later. Luckily, there is a command that allows us to freeze both the state and the memory consumption of the browser tabs , which we can access from the following address:
- chrome: // flags / # proactive-tab-freeze-and-discard
Finally we will mark the option 'Enabled Freeze and discard, heuristics disabled'.
smooth-scrolling (smooth gliding)
As the name of the command suggests, the smooth scroll is a function that allows us to navigate between the content of the web pages in a more agile way without suffering the known "stumbles" that occur when sliding the mouse wheel up or down.
Accessing the command is as simple as entering the following address:
- chrome: // flags / # smooth-scrolling
Later we will mark 'Enabled' to activate the characteristic in question.
gpu-rasterization (GPU rendering)
Chrome generally makes use of the processor and RAM to keep it running smoothly. Fortunately, the browser allows us to play with the computer's graphics card to further improve its performance when loading pages.
To do this, we will enter the following URL in the Chrome address bar:
- chrome: // flags / # enable-gpu-rasterization
Finally, we will mark the option 'Force-enabled for all layers' to force the rendering in all the components of the application. Along with this command, it is recommended to activate the OOP rendering flag that can be found at the following address:
- chrome: // flags / # enable-oop-rasterization
For the latter we will use the 'Enabled' option.
accelerated-2d-canvas (2D graphics acceleration)
A function very similar to the previous one that this time improves the processing of 2D graphics, such as images or plain text with animations , which are processed via software. The application of this command delegates the processing to the hardware of the computer, and we can access it through the following URL:
- chrome: // flags / # enable-accelerated-2d-canvas
Like the rest of the commands, we will mark 'Enabled' so that the function is applied correctly.
zero-copy-rasterizer (zero copy raster)
Taking advantage of the GPU of our computer again, relegating the processing threads to the graphics card , a task that is usually associated with the CPU. We can access this through the following command:
- chrome: // flags / # enable-zero-copy
Finally we will mark Enabled to activate the feature in Chrome.
Other commands and flags to speed up Google Chrome
There are many flags that allow us to improve the speed of Google Chrome. Since your explanation could lead us to more than one article, we leave you below with a list of all the commands and their configuration to apply in any version of Chrome:
- Automatic tab discarding : mark as 'Enabled'.
- Block scripts loaded via document write : mark as 'Enabled'.
- Brotli Content-Encoding : mark as 'Enabled'.
- Developer Tools experiments : mark as 'Enabled'.
- Experimental JavaScript : mark as 'Enabled'.
- Experimental QUIC protocol : mark as 'Enabled'.
- Fast tab / window close : mark as 'Enabled'.
- Future V8 VM features : mark as 'Enabled'.
- Hyperlink auditing : mark as 'Disabled'.
- New Media Controls : mark as 'Disabled'.
- No-State Prefetch : Mark as 'Enabled'.
- NoScript previews : mark as 'Enabled'.
- Number of raster threads : between 2 and 4.
- Offline Auto-Reload Mode : mark as 'Disabled'.
- Only Auto-Reload Visible Tabs : mark as 'Enabled'.
- Optimize background video playback : mark as 'Enabled'.
- Override software rendering list : mark as 'Enabled'.
- Simple Cache for HTTP : mark as 'Enabled'.
- Tab audio muting UI control : mark as 'Enabled'.
- Touch Events API : mark as 'Disabled' (only if you don't use touchscreens).
- Touch adjustment : mark as 'Disabled' (only if you don't use touchscreens).
- Use all upcoming UI features : mark as 'Enabled'.