13.4 sec in total
640 ms
12.5 sec
222 ms
Visit carddass.in.th now to see the best up-to-date Carddass content for Thailand and also check out these interesting facts you probably never knew about carddass.in.th
??ҡ???ū????????????? ?繡?????????Ǻ???????Фèҡ????????ش?Ե????ͧ??ҡ?????????????ҧ?ú??ǹ ?ҷ? ⡤? ??ѧ ??е???Ф????? ?ա?ҡ??? ????????????????ö?ӵ???Ф÷???蹪ͺ?ҵ?????ѹ???㨪ͺ?????ҧ???մ?ӡѴ
Visit carddass.in.thWe analyzed Carddass.in.th page load time and found that the first response time was 640 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
carddass.in.th performance score
640 ms
258 ms
526 ms
152 ms
284 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 85% of them (76 requests) were addressed to the original Carddass.in.th, 2% (2 requests) were made to S10.histats.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10.5 sec) belongs to the original domain Carddass.in.th.
Page size can be reduced by 135.5 kB (55%)
248.2 kB
112.7 kB
In fact, the total size of Carddass.in.th main page is 248.2 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. 25% of websites need less resources to load. Javascripts take 159.0 kB which makes up the majority of the site volume.
Potential reduce by 19.3 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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 53% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.3 kB or 86% of the original size.
Potential reduce by 3.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. Carddass images are well optimized though.
Potential reduce by 90.4 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 90.4 kB or 57% of the original size.
Potential reduce by 22.8 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. Carddass.in.th needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 80% of the original size.
Number of requests can be reduced by 27 (32%)
85
58
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carddass. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
carddass.in.th
640 ms
style.css
258 ms
java.js
526 ms
js9.js
152 ms
bgMain.gif
284 ms
bgSubMenu.gif
297 ms
spacer.gif
526 ms
header.gif
2086 ms
bgMenu.gif
541 ms
menu_01a.gif
575 ms
menu_02a.gif
593 ms
menu_03a.gif
608 ms
menu_04a.gif
784 ms
menu_05a.gif
803 ms
menu_06a.gif
830 ms
menu_07a.gif
848 ms
menu_08a.gif
874 ms
menu_09a.gif
1045 ms
newsBox_01.gif
1066 ms
memBox_01.gif
1086 ms
butLogIna.gif
1109 ms
memBox_03.gif
1128 ms
butForGota.gif
1313 ms
butRegistera.gif
1331 ms
arw_01.gif
1351 ms
newArrival_01.gif
1373 ms
s.jpg
1384 ms
arw_02.gif
1574 ms
cardBox_01.gif
2407 ms
.jpg
1607 ms
DB_Banner_Ad_500x190pxl_V6.gif
10490 ms
cartoon-banner.jpg
2148 ms
eventTitle.gif
1830 ms
productTitle.gif
1864 ms
webboardTitle.gif
2091 ms
mainBox1_01.gif
2130 ms
contactTitle.gif
2338 ms
mainBox1_03.gif
2358 ms
mainBox1_04.gif
2385 ms
contactForm.html
2390 ms
ga.js
4 ms
__utm.gif
12 ms
377891.php
5 ms
cc_199.js
209 ms
19 ms
20 ms
ZQp6LCe0OO3LeZB6ES1CZrJvMefQTtT9oZjddBS5
54 ms
tpid=2DE7B66B6CC3AF59B12D06B5020A8C9D
33 ms
kitten
96 ms
27675
96 ms
logoKK.gif
2304 ms
mainBox1_05.gif
2323 ms
events
45 ms
dduid_sync
100 ms
mainBox1_06.gif
2122 ms
mainBox1_08.gif
2135 ms
memBox_02.gif
2094 ms
memBox_04.gif
2261 ms
newsBox_02.gif
2267 ms
newsBox_03.gif
2117 ms
newsBox_04.gif
2121 ms
newArrival_02.gif
2101 ms
arw_03.gif
2262 ms
newArrival_03.gif
2265 ms
cardBox_02.gif
2116 ms
arw_04.gif
2112 ms
cardBox_03.gif
2101 ms
bgAd.gif
2300 ms
mainBoxMiddle2.gif
2274 ms
mainBoxTop1.gif
2105 ms
mainBoxSideL.gif
2112 ms
bgBox.gif
2105 ms
mainBoxSideR.gif
2386 ms
mainBoxBottom.gif
2382 ms
mainBoxTop2.gif
2190 ms
mainBox1_02.gif
2166 ms
mainBox1_04b.gif
1950 ms
mainBox1_05b.gif
2149 ms
mainBox1_07.gif
1938 ms
foot.gif
1930 ms
styleSheets.css
1625 ms
menu_01b.gif
273 ms
menu_03b.gif
586 ms
menu_04b.gif
610 ms
menu_05b.gif
596 ms
menu_06b.gif
603 ms
menu_07b.gif
621 ms
menu_08b.gif
609 ms
menu_09b.gif
839 ms
carddass.in.th SEO score
![]()
EN
![]()
N/A
WINDOWS-874
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carddass.in.th can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Carddass.in.th main page’s claimed encoding is windows-874. 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.
carddass.in.th
Open Graph description is not detected on the main page of Carddass. 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: