Access android.com. Android | Do More With Google on Android Phones & Devices

Report Summary

About Website

Click here to check amazing Android content for India. Otherwise, check out these important facts you probably never knew about android.com

Discover more about Android & learn how our devices can help you Do more with Google with hyper connectivity, powerful protection, Google apps, & Quick Share.

Visit android.com

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

android.com

13 ms

www.android.com

61 ms

sticky-dialog.min.css

20 ms

survey.min.css

27 ms

tracking.min.js

26 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 17% of them (11 requests) were addressed to the original Android.com, 78% (51 requests) were made to Lh3.googleusercontent.com and 5% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (560 ms) relates to the external source Lh3.googleusercontent.com.

Content Size

6.6 MB

After Optimization

5.7 MB

In fact, the total size of Android.com main page is 6.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 759.2 kB

Original 1.1 MB
After minification 1.1 MB
After compression 340.1 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 759.2 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 142.3 kB

Original 5.4 MB
After minification 5.3 MB

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. Android images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 446 B

Original 97.2 kB
After minification 97.2 kB
After compression 96.7 kB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 29 B

Original 17.5 kB
After minification 17.5 kB
After compression 17.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Android.com has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Android. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

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 IDs are not unique

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

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

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Android.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Android.com 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

android.com

Open Graph data is detected on the main page of Android. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Android | Do More With Google on Android Phones & Devices

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)