7.4 sec in total
823 ms
4.6 sec
2 sec
Click here to check amazing Team Android content. Otherwise, check out these important facts you probably never knew about teamandroid.de
Android Device & App Test Blog
Visit teamandroid.deWe analyzed Teamandroid.de page load time and found that the first response time was 823 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
teamandroid.de performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.7 s
1/100
25%
Value7.7 s
24/100
10%
Value120 ms
97/100
30%
Value0.019
100/100
15%
Value8.8 s
35/100
10%
823 ms
39 ms
270 ms
184 ms
368 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 22% of them (31 requests) were addressed to the original Teamandroid.de, 7% (10 requests) were made to Static.xx.fbcdn.net and 6% (9 requests) were made to Ecx.images-amazon.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Teamandroid.de.
Page size can be reduced by 1.2 MB (26%)
4.6 MB
3.4 MB
In fact, the total size of Teamandroid.de main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 238.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. 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 238.7 kB or 89% of the original size.
Potential reduce by 353.3 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. Team Android images are well optimized though.
Potential reduce by 528.9 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 528.9 kB or 73% of the original size.
Potential reduce by 66.1 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. Teamandroid.de needs all CSS files to be minified and compressed as it can save up to 66.1 kB or 73% of the original size.
Number of requests can be reduced by 71 (55%)
128
57
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Team 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 32 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.teamandroid.de
823 ms
shareaholic.js
39 ms
wp-emoji-release.min.js
270 ms
twiget.css
184 ms
style.css
368 ms
genericons.css
276 ms
css
27 ms
www.teamandroid.de
355 ms
authorbox.css
252 ms
lightbox.min.css
274 ms
jquery.js
436 ms
jquery-migrate.min.js
357 ms
twiget.js
364 ms
navigation.js
371 ms
wpsf-js.php
691 ms
86a47f18e1aca9194f46f75066789e54.json
34 ms
jquery.touchwipe.min.js
297 ms
jquery.lightbox.min.js
298 ms
count.js
299 ms
analytics.js
87 ms
2015-09-04-07.48.59-e1444125688273-900x280.jpg
398 ms
IMG_2090-900x280.jpg
399 ms
IMG_0248-900x280.jpg
397 ms
2014-01-28-14.20.38-e1391728113305.jpg
395 ms
nexus7_leder_case_IMG_0157.jpg
666 ms
sgs4_kfz_halterung_IMG_0012.jpg
574 ms
IMG_9965.jpg
573 ms
IMG_8723.jpg
572 ms
samsung_galaxy_s3_huelle_otternbox_IMG_8419.jpg
660 ms
IMG_8239.jpg
655 ms
Problem1.png
1234 ms
motorola_razr_testbericht_5744.jpg
1204 ms
ajax-loader.gif
656 ms
widgets.js
36 ms
qhFtudkoEdJV__ba4WegbA.ttf
134 ms
hpORcvLZtemlH8gI-1S-7i3USBnSvpkopQaUR-2r7iU.ttf
136 ms
b41KxjgiyqX-hkggANDU6InF5uFdDttMLvmWuJdhhgs.ttf
138 ms
Genericons.svg
1144 ms
8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=
33 ms
collect
99 ms
q
307 ms
q
312 ms
q
348 ms
q
319 ms
q
358 ms
q
342 ms
cm
538 ms
cm
552 ms
shrMain.min.js
65 ms
likebox.php
963 ms
all.js
92 ms
count.js
265 ms
www.teamandroid.de
1038 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
274 ms
a-logo-amazon.png
801 ms
41dGlhZC4oL._AC_SR98,95_.jpg
257 ms
ir
803 ms
json
776 ms
cart.gif
781 ms
json
768 ms
41K6HMmC8QL._AC_SR98,95_.jpg
239 ms
json
779 ms
41oqdabJrZL._AC_SR98,95_.jpg
225 ms
json
727 ms
json
733 ms
51EDYwLGHaL._AC_SR98,95_.jpg
197 ms
51GTv73lDiL._AC_SR98,95_.jpg
201 ms
json
719 ms
51yx9F87q9L._AC_SR98,95_.jpg
179 ms
jquery.min.js
174 ms
count-data.js
577 ms
count-data.js
574 ms
550 ms
41GsXIfQSfL._SL110_.jpg
535 ms
buy-from-tan.gif
580 ms
532 ms
41uDpHMm3kL._SL110_.jpg
527 ms
243 ms
kyEKgjk51ZE.css
270 ms
kTub4bakEmM.css
349 ms
FAHeNGXgPup.js
367 ms
FJmpeSpHpjS.js
354 ms
0wM5s1Khldu.js
347 ms
1bNoFZUdlYZ.js
346 ms
xd_arbiter.php
291 ms
xd_arbiter.php
439 ms
pageview.gif
161 ms
mwfz0xbshmhgtaqkbvpz_normal.png
156 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
80 ms
info.json
252 ms
partners.js
271 ms
419927_369230456430226_1720276945_n.jpg
117 ms
190410_197729980246942_3913125_n.jpg
141 ms
995357_1267001169995387_7297341371709450944_n.jpg
135 ms
10354686_10150004552801856_220367501106153455_n.jpg
133 ms
10306234_10204873410789791_2156693256949779201_n.jpg
221 ms
10923480_738021209647953_6506380694522276384_n.jpg
201 ms
12301581_876196389161003_5290550130983711890_n.jpg
202 ms
11902250_879778312076707_5552583621121502531_n.jpg
168 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
77 ms
sholic.js
10 ms
usermatch
275 ms
beacon.js
8 ms
cms-sh2c.html
73 ms
eexelate.js
8 ms
10 ms
ep
21 ms
ep
34 ms
I6-MnjEovm5.js
20 ms
pQrUxxo5oQp.js
24 ms
pixel
39 ms
160 ms
ping_match.gif
16 ms
2964
92 ms
jot
168 ms
pixel
128 ms
rs
63 ms
net.php
19 ms
match-result
85 ms
pixel
45 ms
generic
37 ms
usermatch
143 ms
generic
43 ms
ermcm
25 ms
xrefid.xgi
23 ms
pixel.gif
26 ms
pixel.gif
24 ms
VunKbMAoJVsAAd4iYncAAACY%26632
191 ms
pm_match
167 ms
i.gif
207 ms
pixelssl.htm
234 ms
cse
371 ms
xrefid.xgi
53 ms
crum
119 ms
crum
90 ms
rum
29 ms
rum
28 ms
rum
21 ms
ddcssl.htm
44 ms
crum
12 ms
ping
52 ms
teamandroid.de accessibility score
ARIA
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.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
teamandroid.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
teamandroid.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teamandroid.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Teamandroid.de 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.
teamandroid.de
Open Graph data is detected on the main page of Team Android. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: