9.7 sec in total
944 ms
8.2 sec
505 ms
Welcome to teedin2.com homepage info - get ready to check Teedin 2 best content for Thailand right away, or after learning these important things about teedin2.com
ศูนย์กลางการซื้อ ขาย บ้าน ที่ดิน เพื่อเผยแพร่ประกาศขายบ้านและที่ดินของท่านไปยังกลุ่มผู้ซื้อบ้านและที่ดินทั่วประเทศ เพิ่มโอกาศในการขายที่ดินให้ได้ราคาดี
Visit teedin2.comWe analyzed Teedin2.com page load time and found that the first response time was 944 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
teedin2.com performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value26.5 s
0/100
25%
Value54.9 s
0/100
10%
Value320 ms
76/100
30%
Value0.177
68/100
15%
Value18.7 s
3/100
10%
944 ms
1901 ms
586 ms
592 ms
15 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 32% of them (36 requests) were addressed to the original Teedin2.com, 14% (15 requests) were made to Static.xx.fbcdn.net and 9% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Teedin2.com.
Page size can be reduced by 804.5 kB (63%)
1.3 MB
477.5 kB
In fact, the total size of Teedin2.com main page is 1.3 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. 70% of websites need less resources to load. Javascripts take 891.1 kB which makes up the majority of the site volume.
Potential reduce by 201.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 201.9 kB or 81% of the original size.
Potential reduce by 16.4 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, Teedin 2 needs image optimization as it can save up to 16.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 557.6 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 557.6 kB or 63% of the original size.
Potential reduce by 28.6 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. Teedin2.com needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 81% of the original size.
Number of requests can be reduced by 58 (54%)
107
49
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teedin 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
teedin2.com
944 ms
www.teedin2.com
1901 ms
style.css
586 ms
wt-rotator.css
592 ms
addthis_widget.js
15 ms
jquery-1.7.1.min.js
1506 ms
jquery.colorbox-min.js
790 ms
jquery.hoverIntent.js
606 ms
imgRotate.js
1231 ms
master.js
1156 ms
js-image-slider.css
1183 ms
js-image-slider.js
1199 ms
generic.css
1380 ms
adsbygoogle.js
37 ms
t0031567.js
538 ms
fbevents.js
140 ms
teedin2-logo.png
615 ms
post.png
614 ms
ads-nav.png
616 ms
84.gif
1822 ms
82.gif
932 ms
92.gif
2737 ms
93.gif
1182 ms
search_btn.png
1195 ms
90.gif
1471 ms
96.gif
3065 ms
98.gif
1778 ms
99.gif
2394 ms
bannerE.gif
2051 ms
bannerF.gif
2380 ms
bannerG.gif
2415 ms
all.js
336 ms
bg-nav.png
2643 ms
search2.png
2956 ms
plusone.js
124 ms
loading.gif
2949 ms
bg-box.png
2986 ms
bg-search-form_01.png
3222 ms
bg-search-form_02.png
3276 ms
likebox.php
225 ms
ca-pub-6544794408628062.js
48 ms
zrt_lookup.html
48 ms
show_ads_impl.js
76 ms
footer.jpg
3450 ms
hold.png
3460 ms
th_donate_1.8.js
563 ms
th_common_1.4.js
564 ms
118 ms
cb=gapi.loaded_0
49 ms
cb=gapi.loaded_1
65 ms
fastbutton
120 ms
ads
337 ms
osd.js
16 ms
postmessageRelay
68 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
18 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
142 ms
xYm_UD1pmAz.css
338 ms
api.js
66 ms
core:rpc:shindig.random:shindig.sha1.js
120 ms
2536007149-postmessagerelay.js
92 ms
65 ms
xd_arbiter.php
244 ms
xd_arbiter.php
521 ms
10983424283978806373
36 ms
abg.js
39 ms
m_js_controller.js
50 ms
googlelogo_color_112x36dp.png
78 ms
s
28 ms
x_button_blue2.png
45 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
300lo.json
87 ms
controls.png
67 ms
ga.js
76 ms
goggen.php
585 ms
border.png
61 ms
loading-background.png
63 ms
loading.gif
63 ms
sh.7c7179124ea24ac6ba46caac.html
36 ms
layers.3643cb2e25fb91c29386.js
33 ms
th.js
31 ms
__utm.gif
20 ms
likebox.php
77 ms
like_box.php
94 ms
TGpOWuX6Pv8.css
69 ms
_rx8naC75Dy.js
140 ms
x5F9OMjKyLw.js
268 ms
ICDbTSzjQEg.js
314 ms
TTCre3391I0.js
208 ms
ZlkNRU5bFoV.css
202 ms
mbWe9Wkgf-v.css
205 ms
x5F9OMjKyLw.js
364 ms
TTCre3391I0.js
275 ms
575804_313783118749676_475466868_n.png
350 ms
36613_313767262084595_1057328045_n.png
417 ms
1959918_1495861147336196_5606793360474249939_n.jpg
485 ms
12190870_535549486609451_5574320780826166029_n.jpg
549 ms
1966736_1407421572844598_2489806777100450824_n.jpg
551 ms
12208726_127825117579524_6163867643300337941_n.jpg
556 ms
11898624_135051183502092_5766882467915058505_n.jpg
553 ms
12742045_1681749342042550_4998974202060837955_n.jpg
556 ms
12745716_548219092048355_5301836239720694884_n.jpg
557 ms
wL6VQj7Ab77.png
99 ms
s7jcwEQH7Sx.png
98 ms
1526109_10152723794287705_7137207901310113534_n.jpg
554 ms
activeview
13 ms
I6-MnjEovm5.js
70 ms
vlXaquuXMrr.js
136 ms
vlXaquuXMrr.js
136 ms
bullet.png
309 ms
ui
30 ms
teedin2.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
teedin2.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
Issues were logged in the Issues panel in Chrome Devtools
teedin2.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
TH
TH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teedin2.com can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it matches the claimed language. Our system also found out that Teedin2.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.
teedin2.com
Open Graph description is not detected on the main page of Teedin 2. 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: