Access google.fr. Google

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value1,540 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

google.fr

111 ms

www.google.fr

224 ms

googlelogo_white_background_color_272x92dp.png

17 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Google.fr and no external sources were called. The less responsive or slowest element that took the longest time to load (224 ms) belongs to the original domain Google.fr.

Content Size

38.8 kB

After Optimization

34.7 kB

In fact, the total size of Google.fr main page is 38.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 31.8 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 3.2 kB

Original 5.4 kB
After minification 5.4 kB
After compression 2.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 3.2 kB or 58% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 31.8 kB
After minification 31.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Google images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 858 B

Original 1.5 kB
After minification 1.5 kB
After compression 611 B

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 858 B or 58% of the original size.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Google. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[role] values are not valid

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

FR
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Google.fr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Google.fr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Google. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: