484 ms in total
54 ms
311 ms
119 ms
Click here to check amazing Source Android content for India. Otherwise, check out these important facts you probably never knew about source.android.com
Android unites the world! Use the open source Android operating system to power your device. COPY
Visit source.android.comWe analyzed Source.android.com page load time and found that the first response time was 54 ms and then it took 430 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
source.android.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value6.9 s
7/100
25%
Value6.0 s
47/100
10%
Value720 ms
41/100
30%
Value0.025
100/100
15%
Value9.6 s
30/100
10%
54 ms
37 ms
24 ms
20 ms
55 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 58% of them (14 requests) were addressed to the original Source.android.com, 17% (4 requests) were made to Fonts.gstatic.com and 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (99 ms) relates to the external source Apis.google.com.
Page size can be reduced by 504.7 kB (69%)
732.5 kB
227.8 kB
In fact, the total size of Source.android.com main page is 732.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 507.6 kB which makes up the majority of the site volume.
Potential reduce by 8.7 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. This page needs HTML code to be minified as it can gain 2.2 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 8.7 kB or 69% of the original size.
Potential reduce by 37.9 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. Obviously, Source Android needs image optimization as it can save up to 37.9 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 379.8 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 379.8 kB or 75% of the original size.
Potential reduce by 78.3 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. Source.android.com needs all CSS files to be minified and compressed as it can save up to 78.3 kB or 84% of the original size.
Number of requests can be reduced by 5 (28%)
18
13
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Source 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 6 to 1 for JavaScripts and as a result speed up the page load time.
source.android.com
54 ms
css
37 ms
default.css
24 ms
jsapi
20 ms
android_3p-bundle.js
55 ms
docs.js
41 ms
api.js
20 ms
ga.js
49 ms
lists.js
16 ms
gcm_lists.js
19 ms
plusone.js
99 ms
sac_logo.png
30 ms
icon_more.png
29 ms
more_top.png
29 ms
more_mid.png
45 ms
more_bottom.png
46 ms
icon_search.png
46 ms
close.png
46 ms
android_framework_small.png
52 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
35 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
46 ms
Jzo62I39jc0gQRrbndN6nXYhjbSpvc47ee6xR_80Hnw.ttf
55 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
55 ms
__utm.gif
14 ms
source.android.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
source.android.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
source.android.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Source.android.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Source.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.
source.android.com
Open Graph description is not detected on the main page of Source Android. 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: