Google Chrome opens up the gap to Safari

2 mins read
Google Chrome opens up the gap to Safari

Google Chrome, with the latest update, has opened the gap with Safari on MacBooks and announced that it has become much faster.

Google Chrome opens up the gap to Safari

A few months ago, Google announced that the Chrome app was reaching fairly high speeds on macOS devices. Going a step further, the company even stated that Chrome is even faster than Apple’s own browser, Safari. Now, with the new update, Google Chrome is now claimed to be much faster on MacBooks.

Google Chrome is unrivaled on MacBooks
The company announced that the latest version of Chrome now runs 20 percent faster on Apple’s best laptops. Google, which uses Apple’s Speedometer to measure the response time of the application, has reached over 360 points with Chrome.

Nearly 300 browsers were compared. According to the results, Google Chrome has left behind all other browsers. It was also underlined that Chrome is 15 percent more successful than Safari in terms of graphics performance.

This increase in the speed of the browser came with several changes to ThinLTO. Last year, Google introduced a series of general JavaScript optimizations to improve the speed of the browser. As a result, Google Chrome is 43 percent faster on MacBooks with M1 processors compared to the end of 2020. Google also celebrated this with a post on Twitter.

While Google seems to be focused on macOS devices, it hasn’t forgotten about Android devices either. The company also noted that Chrome is up to 15 percent faster on Android devices thanks to advanced navigation technology in its browser UI array.

These speed figures revealed by the Google Chrome application are quite impressive. So which browser do you use and for what reason? You can share your opinions with us in the comments section.

FİKRİKADİM

The ancient idea tries to provide the most accurate information to its readers in all the content it publishes.


Fatal error: Uncaught TypeError: fclose(): Argument #1 ($stream) must be of type resource, bool given in /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php:2386 Stack trace: #0 /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php(2386): fclose(false) #1 /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php(2146): wp_cache_get_ob('<!DOCTYPE html>...') #2 [internal function]: wp_cache_ob_callback('<!DOCTYPE html>...', 9) #3 /home/fikrikadim/public_html/wp-includes/functions.php(5420): ob_end_flush() #4 /home/fikrikadim/public_html/wp-includes/class-wp-hook.php(324): wp_ob_end_flush_all('') #5 /home/fikrikadim/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array) #6 /home/fikrikadim/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home/fikrikadim/public_html/wp-includes/load.php(1270): do_action('shutdown') #8 [internal function]: shutdown_action_hook() #9 {main} thrown in /home/fikrikadim/public_html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 2386