20.3 sec in total
1.9 sec
18.3 sec
161 ms
Welcome to android-town.org homepage info - get ready to check Android Town best content for South Korea right away, or after learning these important things about android-town.org
안드로이드타운, 안드로이드, 전문가, 커뮤니티, T아카데미
Visit android-town.orgWe analyzed Android-town.org page load time and found that the first response time was 1.9 sec and then it took 18.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
android-town.org performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.5 s
19/100
25%
Value5.8 s
50/100
10%
Value530 ms
56/100
30%
Value0.293
41/100
15%
Value5.3 s
73/100
10%
1884 ms
945 ms
596 ms
677 ms
700 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Android-town.org, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Android-town.org. The less responsive or slowest element that took the longest time to load (7.4 sec) relates to the external source .
Page size can be reduced by 1.2 MB (46%)
2.6 MB
1.4 MB
In fact, the total size of Android-town.org main page is 2.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. 20% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 369 B
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 369 B or 43% of the original size.
Potential reduce by 78.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. Android Town images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 87% of the original size.
Potential reduce by 56.9 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-town.org needs all CSS files to be minified and compressed as it can save up to 56.9 kB or 81% of the original size.
Number of requests can be reduced by 57 (66%)
86
29
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Android Town. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
android-town.org
1884 ms
send.jsp
945 ms
style.css
596 ms
float.js
677 ms
_reset.css
700 ms
main.css
705 ms
menu_main.css
722 ms
css
25 ms
jquery-1.11.1.min.js
1398 ms
doubletaptogo.js
564 ms
css
16 ms
topline.jpg
469 ms
logoline.gif
465 ms
menu_01.gif
200 ms
menu_02.gif
240 ms
menu_03.gif
227 ms
book1.png
235 ms
book2.png
396 ms
files.png
451 ms
free.png
469 ms
lecture.png
480 ms
people.png
593 ms
menu_07.gif
676 ms
menu_08.gif
698 ms
menu_09.gif
702 ms
banner_doitandroid.gif
702 ms
banner_javaandroid.gif
957 ms
copy.gif
791 ms
NanumGothic-Regular.woff
7381 ms
board-list.do
1252 ms
menu_04.gif
918 ms
menu_06.gif
920 ms
layouts.css
236 ms
common.css
201 ms
oz.css
242 ms
alice.css
237 ms
datatable.css
399 ms
style.css
704 ms
prototype.js
1627 ms
extprototype.js
480 ms
oz.js
780 ms
alice.js
3414 ms
unicorn3.js
1198 ms
common.js
938 ms
board.js
2155 ms
tag.js
1171 ms
scroll.js
1405 ms
calendar.js
1438 ms
user.js
1872 ms
yahoo-dom-event.js
2157 ms
element.js
3344 ms
uploader.js
2345 ms
datasource.js
4032 ms
datatable.js
5777 ms
title.gif
238 ms
i_nox.gif
235 ms
i_doc.gif
201 ms
i_memo.gif
242 ms
h_1000.gif
239 ms
i_tag.gif
399 ms
h_500.gif
467 ms
h_2000.gif
473 ms
h_3000.gif
474 ms
btn_board_search.gif
482 ms
b_board_left.gif
596 ms
b_board_right.gif
701 ms
btn_board_write.gif
708 ms
slider.html
718 ms
title_top.gif
716 ms
title_bg.gif
787 ms
title_left.gif
788 ms
title_right.gif
929 ms
footer_line.gif
938 ms
empty.gif
952 ms
b_board_middle.gif
955 ms
jssor.core.js
300 ms
jssor.utils.js
520 ms
jssor.slider.js
2073 ms
slider_main.js
461 ms
main_bg.jpg
471 ms
loading.gif
234 ms
book_doitandroid.png
1488 ms
book_doitandroid_thumb.png
241 ms
book_javaandroid.png
4844 ms
book_javaandroid_thumb.png
244 ms
s5.png
2619 ms
s5t.jpg
481 ms
a07.png
485 ms
android-town.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
android-town.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
android-town.org 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
N/A
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Android-town.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Android-town.org main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
android-town.org
Open Graph description is not detected on the main page of Android Town. 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: