13.7 sec in total
836 ms
12.6 sec
308 ms
Visit b2bdigg.com now to see the best up-to-date B 2 Bdigg content and also check out these interesting facts you probably never knew about b2bdigg.com
Thongfa.com - ลงประกาศฟรี! ชื้อ ขาย คอนโด บ้านเดี่ยว ทาวน์เฮ้าส์ ขายบ้าน บ้านมือสอง บ้านใหม่ โครงการใหม่ คอนโดใหม่ ที่ดิน อาพาร์ทเมนท์ หอพัก พื้นที่ขายของ สำนักงาน โกดัง โรงงาน ตึกแถว อาคารพาณิชย์
Visit b2bdigg.comWe analyzed B2bdigg.com page load time and found that the first response time was 836 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
b2bdigg.com performance score
836 ms
9118 ms
25 ms
55 ms
1090 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original B2bdigg.com, 28% (29 requests) were made to Thongfa.com and 20% (21 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (9.1 sec) relates to the external source Thongfa.com.
Page size can be reduced by 459.3 kB (50%)
917.7 kB
458.4 kB
In fact, the total size of B2bdigg.com main page is 917.7 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. Javascripts take 564.9 kB which makes up the majority of the site volume.
Potential reduce by 69.4 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 69.4 kB or 84% of the original size.
Potential reduce by 11.0 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. B 2 Bdigg images are well optimized though.
Potential reduce by 358.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 358.6 kB or 63% of the original size.
Potential reduce by 20.3 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. B2bdigg.com needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 86% of the original size.
Number of requests can be reduced by 49 (51%)
97
48
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of B 2 Bdigg. 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 4 to 1 for CSS and as a result speed up the page load time.
b2bdigg.com
836 ms
www.thongfa.com
9118 ms
jquery.min.js
25 ms
js
55 ms
markerclusterer_packed.js.xhtml;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1090 ms
home.v1.min.js.xhtml;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1084 ms
css3-buttons.css
1316 ms
default.css.xhtml;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
830 ms
home.v1.min.css.xhtml;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1029 ms
jsf.js.xhtml;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1974 ms
show_ads.js
4 ms
ga.js
12 ms
__utm.gif
14 ms
chart
144 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
499 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
497 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
497 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
499 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
500 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
499 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
855 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
863 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
863 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
857 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
860 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
719 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
959 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1099 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1105 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1112 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1119 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1115 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1203 ms
ImageServlet;jsessionid=4F3397D5FF42A38CCCBD4BF9F21B6738
1342 ms
chart
163 ms
chart
126 ms
chart
166 ms
chart
127 ms
chart
127 ms
chart
212 ms
chart
214 ms
chart
209 ms
chart
212 ms
chart
212 ms
chart
212 ms
chart
279 ms
chart
280 ms
chart
278 ms
chart
279 ms
chart
279 ms
chart
280 ms
chart
280 ms
chart
281 ms
ca-pub-5526971815473800.js
96 ms
zrt_lookup.html
95 ms
show_ads_impl.js
95 ms
common.js
28 ms
map.js
46 ms
util.js
84 ms
controls.js
44 ms
places_impl.js
43 ms
loading.gif.xhtml
1261 ms
detect-mylocation2.png
1274 ms
onion.js
68 ms
openhand_8_8.cur
124 ms
ads
284 ms
ViewportInfoService.GetViewportInfo
138 ms
stats.js
69 ms
osd.js
62 ms
css
35 ms
transparent.png
76 ms
powered-by-google-on-white3.png
75 ms
autocomplete-icons.png
74 ms
google4.png
50 ms
mapcnt6.png
50 ms
sv5.png
51 ms
tmapctrl.png
23 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
18 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
19 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
20 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
20 ms
tmapctrl4.png
20 ms
imgs8.png
71 ms
vt
82 ms
vt
83 ms
vt
76 ms
vt
78 ms
vt
66 ms
vt
120 ms
vt
121 ms
vt
130 ms
vt
130 ms
vt
138 ms
vt
151 ms
m_js_controller.js
23 ms
abg.js
35 ms
googlelogo_color_112x36dp.png
45 ms
imgad
35 ms
nessie_icon_tiamat_white.png
37 ms
s
25 ms
x_button_blue2.png
15 ms
veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js
5 ms
AuthenticationService.Authenticate
81 ms
b2bdigg.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise B2bdigg.com 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 B2bdigg.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.
b2bdigg.com
Open Graph description is not detected on the main page of B 2 Bdigg. 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: