10.7 sec in total
1.9 sec
8.3 sec
456 ms
Welcome to ham.in.th homepage info - get ready to check Ham best content right away, or after learning these important things about ham.in.th
THAILAND AMATEUR RADIO CLUB
Visit ham.in.thWe analyzed Ham.in.th page load time and found that the first response time was 1.9 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ham.in.th performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.4 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
1921 ms
28 ms
1371 ms
1481 ms
43 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 37% of them (51 requests) were addressed to the original Ham.in.th, 11% (15 requests) were made to Scontent.xx.fbcdn.net and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Ham.in.th.
Page size can be reduced by 437.8 kB (60%)
727.5 kB
289.7 kB
In fact, the total size of Ham.in.th main page is 727.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. 60% of websites need less resources to load. Images take 226.2 kB which makes up the majority of the site volume.
Potential reduce by 122.8 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 122.8 kB or 87% of the original size.
Potential reduce by 36.7 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, Ham needs image optimization as it can save up to 36.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 140.3 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 140.3 kB or 70% of the original size.
Potential reduce by 138.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. Ham.in.th needs all CSS files to be minified and compressed as it can save up to 138.1 kB or 86% of the original size.
Number of requests can be reduced by 69 (52%)
133
64
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ham. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ham.in.th
1921 ms
yuiloader-dom-event.js
28 ms
vbulletin-core.js
1371 ms
css.php
1481 ms
jquery.js
43 ms
vbulletin_read_marker.js
1099 ms
css.php
1189 ms
css.php
1204 ms
vbulletin-sidebar.js
1099 ms
css.php
1737 ms
connection-min.js
16 ms
vbulletin_md5.js
1388 ms
show_ads.js
9 ms
brand
27 ms
tracker.php
719 ms
brand
74 ms
animation-min.js
10 ms
doc_bg.png
458 ms
logo.png
864 ms
close_login.png
721 ms
gblv.php
208 ms
dyblv.php
148 ms
mblv.php
147 ms
navbar_container_bg.png
548 ms
navtab_bg.png
560 ms
arrow.png
841 ms
t_bg.jpg
1575 ms
navbit-home.png
1045 ms
collapse_40b.png
1107 ms
forum_old-48.png
1129 ms
icon1.png
1165 ms
lastpost-right.png
1336 ms
subforum_old-48.png
1597 ms
icon14.png
1678 ms
forum_link-48.png
1754 ms
users_online.png
1756 ms
spider-icon-black-3.png
1895 ms
forum_stats.png
2128 ms
legend.png
2150 ms
forum_new-16.png
2227 ms
forum_old-16.png
2307 ms
category-16.png
2306 ms
forum_link-16.png
2457 ms
tab-collapsed.png
2711 ms
widget-forum.png
2784 ms
unknown.gif
2859 ms
cron.php
4051 ms
breadcrumb_bg.png
2993 ms
body_bg.png
3249 ms
page_title_bg.jpg
3318 ms
page_title_inner_bg.png
4669 ms
bebasneue-webfont.woff
3937 ms
ca-pub-5713888949100616.js
171 ms
zrt_lookup.html
102 ms
show_ads_impl.js
102 ms
head_bg.png
3762 ms
subhead_bg.png
3836 ms
tdg_bg.png
4319 ms
rss_40b.png
4348 ms
google_custom_search_watermark.gif
96 ms
likebox.php
484 ms
ads
350 ms
osd.js
12 ms
tracker.js
928 ms
misc.php
4427 ms
misc.php
4149 ms
m_js_controller.js
45 ms
abg.js
57 ms
misc.php
4184 ms
tdg_bg.png
4398 ms
favicon
69 ms
googlelogo_color_112x36dp.png
54 ms
nessie_icon_tiamat_white.png
31 ms
s
24 ms
x_button_blue2.png
13 ms
lEK1oKJ42kW.css
97 ms
CsWNZDQah6k.css
99 ms
XCdv7aD40Gm.js
116 ms
lnwXDK64af8.js
145 ms
mn6tHWuLI-Y.js
143 ms
x8BMxYCqTb9.js
143 ms
F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js
7 ms
424319_357469630999098_1485497719_n.jpg
101 ms
308326_188969761182420_1978612854_n.jpg
57 ms
10509590_823382881020387_1844462490786594721_n.jpg
108 ms
12644703_805766549570175_511090315657835929_n.jpg
95 ms
12004932_913036885400912_1351540126658591720_n.jpg
40 ms
11960136_471014873078407_7263186584524841340_n.jpg
78 ms
1489202_1375947276010853_1494034504_n.jpg
118 ms
12650941_1031012536937201_585372585543730079_n.jpg
134 ms
1660306_148322758891610_5845011796119133714_n.jpg
77 ms
12439051_173489679702542_7969141155430366906_n.jpg
86 ms
11147870_1598192983799144_7130807727556836611_n.jpg
120 ms
10413437_181903335523010_1093859878518233779_n.jpg
116 ms
68289_4346547259496_1526456836_n.jpg
113 ms
377949_219502774790494_2062470662_n.jpg
133 ms
12043107_1045511002146691_1243873624580120945_n.jpg
134 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
20 ms
VXcANLwwL5J.js
10 ms
50Trs1RKgUY.js
12 ms
ads
180 ms
b_bg.jpg
3814 ms
doc_bg.png
4026 ms
107 ms
adj
98 ms
beacon
73 ms
stat.gif
344 ms
21 ms
0
102 ms
surly.js
175 ms
a.js;p=11022203438472;a=11022203449152;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=1459171817
72 ms
verify_selector.js
163 ms
blank.gif
154 ms
bapi
103 ms
10527836_Family_Value_728x90.gif
35 ms
ba.html
57 ms
pixel
63 ms
4.gif
64 ms
verifyr.js
62 ms
lidar.js
8 ms
sbhK2lTE.js
7 ms
cTrvNaRi.html
9 ms
4311.js
83 ms
pixel
97 ms
pixel
92 ms
beacon.js
93 ms
dbapi
50 ms
0
43 ms
bg.png
66 ms
adchoices.en.png
93 ms
dt
81 ms
activeview
28 ms
dt
57 ms
sd
6 ms
box_19_top-right.png
26 ms
ci.png
25 ms
ham.in.th accessibility score
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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ham.in.th best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
ham.in.th SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
TH
TIS-620
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ham.in.th 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), while the claimed language is Thai. Our system also found out that Ham.in.th main page’s claimed encoding is tis-620. 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.
ham.in.th
Open Graph description is not detected on the main page of Ham. 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: