7.9 sec in total
1.6 sec
5.8 sec
498 ms
Click here to check amazing 24 Android content for Germany. Otherwise, check out these important facts you probably never knew about 24android.com
Visit 24android.comWe analyzed 24android.com page load time and found that the first response time was 1.6 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize 24android.com rating and web reputation
24android.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value5.6 s
18/100
25%
Value9.7 s
11/100
10%
Value590 ms
50/100
30%
Value1.382
0/100
15%
Value11.5 s
18/100
10%
1600 ms
309 ms
208 ms
210 ms
211 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 72% of them (81 requests) were addressed to the original 24android.com, 9% (10 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain 24android.com.
Page size can be reduced by 271.9 kB (20%)
1.4 MB
1.1 MB
In fact, the total size of 24android.com main page is 1.4 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 978.5 kB which makes up the majority of the site volume.
Potential reduce by 64.9 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 64.9 kB or 81% of the original size.
Potential reduce by 11.1 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. 24 Android images are well optimized though.
Potential reduce by 164.5 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 164.5 kB or 59% of the original size.
Potential reduce by 31.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. 24android.com needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 78% of the original size.
Number of requests can be reduced by 50 (47%)
106
56
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 24 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 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.24android.com
1600 ms
style.css
309 ms
default.css
208 ms
savrix-style.css
210 ms
widget.css
211 ms
styles.css
211 ms
style.php
420 ms
nggallery.css
410 ms
shutter-reloaded.css
411 ms
title-excerpt-thumbnail.css
411 ms
pagenavi-css.css
412 ms
lightbox.min.css
508 ms
jquery.js
921 ms
jquery-migrate.min.js
612 ms
shutter-reloaded.js
612 ms
jquery.cycle.all.min.js
714 ms
ngg.slideshow.min.js
620 ms
jquery.min.js
915 ms
show_ads.js
5 ms
all.js
71 ms
jquery.flow.1.2.auto.js
622 ms
jquery.jcarousel.pack.js
622 ms
menu.min.js
631 ms
jquery.fieldtag.min.js
823 ms
jquery.form.min.js
852 ms
scripts.js
852 ms
jquery.touchwipe.min.js
853 ms
jquery.lightbox.min.js
965 ms
bodybg.jpg
1058 ms
24android.png
256 ms
nav_right.png
257 ms
nav_left.png
257 ms
catdd-bot.png
346 ms
topbox_mid.jpg
358 ms
topbox_top.jpg
462 ms
catdd.jpg
463 ms
lg_optimus_g_teaser_2.jpg
563 ms
timthumb.php
569 ms
mobile_shopping_studie.jpg
669 ms
timthumb.php
683 ms
teamviewer7_teaser.jpg
871 ms
timthumb.php
868 ms
amazon_kindle_fire_2_teaser.jpg
875 ms
timthumb.php
892 ms
android_august_weg_teaser.jpg
1195 ms
timthumb.php
1013 ms
timthumb.php
1092 ms
timthumb.php
1096 ms
timthumb.php
1114 ms
timthumb.php
1235 ms
timthumb.php
1274 ms
timthumb.php
1315 ms
timthumb.php
1318 ms
timthumb.php
1334 ms
timthumb.php
1417 ms
contenthead.jpg
1439 ms
rss.png
1477 ms
facebook.png
1519 ms
ca-pub-7962340789099053.js
64 ms
zrt_lookup.html
54 ms
show_ads_impl.js
79 ms
twitter.png
1485 ms
lg_optimus_g.png
1473 ms
Mobile_Shopping_-Studie_logo.png
2396 ms
teamviewer7_logo.png
2413 ms
333 ms
ga.js
34 ms
amazon_kindle_fire.png
1601 ms
xd_arbiter.php
95 ms
xd_arbiter.php
207 ms
ads
285 ms
__utm.gif
93 ms
osd.js
10 ms
android.png
1478 ms
angrybirds.png
1479 ms
lte.png
1494 ms
samsung_galaxy_s_3.png
1640 ms
total_war_battles.png
1591 ms
searchback.png
1581 ms
like_box.php
224 ms
go.png
1493 ms
lg_optimus_g_teaser_2-70x46.jpg
1637 ms
samsung_galaxy_s_3_schwarz_teaser-70x46.jpg
1579 ms
galaxy_note_2_benchmark_teaser-70x46.jpg
1575 ms
roNeOY-tz5Y.css
84 ms
UHhaxo8Cs3k.css
102 ms
_rx8naC75Dy.js
137 ms
x5F9OMjKyLw.js
168 ms
ICDbTSzjQEg.js
136 ms
TTCre3391I0.js
154 ms
galaxy_s_3_brown_teaser-70x46.jpg
1492 ms
samsung_galaxy_note_pm_teaser-70x46.jpg
1621 ms
529190_329649793755463_1223225469_n.jpg
184 ms
200453_158982677488843_7670119_n.jpg
158 ms
10354686_10150004552801856_220367501106153455_n.jpg
168 ms
12744097_1013597755345805_8213597833203498225_n.jpg
170 ms
10580030_744676455593644_1126356687629203877_n.jpg
177 ms
1379841_10150004552801901_469209496895221757_n.jpg
175 ms
12729239_10204209616401095_2052066473559869007_n.jpg
177 ms
522004_446624872087159_444257531_n.jpg
193 ms
12799130_1124348827595741_8900280964994622750_n.jpg
202 ms
wL6VQj7Ab77.png
21 ms
s7jcwEQH7Sx.png
22 ms
pagination.png
1477 ms
sprite.jpg
1479 ms
tslidebg.jpg
1490 ms
slide-page.jpg
1619 ms
scrollb.jpg
1538 ms
scrolltop.jpg
1500 ms
I6-MnjEovm5.js
19 ms
vlXaquuXMrr.js
36 ms
scrollbot.jpg
1477 ms
spritescroll.jpg
1574 ms
24android.com 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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
24android.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
24android.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 24android.com 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 German language. Our system also found out that 24android.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.
24android.com
Open Graph description is not detected on the main page of 24 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: