12.9 sec in total
4.1 sec
7.7 sec
1 sec
Welcome to prachatai.org homepage info - get ready to check Prachatai best content for Thailand right away, or after learning these important things about prachatai.org
ประชาไท Prachatai.com เว็บไซต์ข่าว การเมือง สิทธิมนุษยชน กระบวนการยุติธรรม
Visit prachatai.orgWe analyzed Prachatai.org page load time and found that the first response time was 4.1 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.
prachatai.org performance score
name
value
score
weighting
Value3.7 s
31/100
10%
Value4.6 s
35/100
25%
Value11.2 s
5/100
10%
Value6,150 ms
0/100
30%
Value0.245
51/100
15%
Value22.2 s
1/100
10%
4146 ms
13 ms
13 ms
19 ms
124 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 21% of them (30 requests) were addressed to the original Prachatai.org, 27% (40 requests) were made to Blogazine.pub and 14% (21 requests) were made to Webanner.biz. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Prachatai.org.
Page size can be reduced by 629.9 kB (43%)
1.5 MB
834.2 kB
In fact, the total size of Prachatai.org main page is 1.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 622.1 kB which makes up the majority of the site volume.
Potential reduce by 128.7 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 128.7 kB or 85% of the original size.
Potential reduce by 59.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. Prachatai images are well optimized though.
Potential reduce by 330.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 330.4 kB or 60% of the original size.
Potential reduce by 111.4 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. Prachatai.org needs all CSS files to be minified and compressed as it can save up to 111.4 kB or 79% of the original size.
Number of requests can be reduced by 79 (54%)
145
66
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prachatai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.
prachatai.org
4146 ms
389e50fd975a48edf180ad3d2962fb45.css
13 ms
css_f5828c016f2a18c4fe52367902b55165.css
13 ms
js_7ecdc4d3a4897945beeda6bc94e8a4e5.js
19 ms
plusone.js
124 ms
show_ads.js
52 ms
adsbygoogle.js
51 ms
n0024469.js
616 ms
tracker.php
889 ms
counter.js
63 ms
new-icon-set-prachatai-2013.jpg
141 ms
a1
1148 ms
a1
676 ms
a2
691 ms
a2
679 ms
5661196852_eb39ebdd30_m.jpg
78 ms
likebox.php
276 ms
widgets.js
295 ms
new-prachatai-top-bg.gif
31 ms
new-prachatai-logo.gif
31 ms
menu-leaf.png
30 ms
12784704_10207959738885536_1307745471_n.jpg
30 ms
20160226_cover1_thumb.jpg
33 ms
cats-crop_288.jpg
36 ms
aa2.jpg
50 ms
aa1_32.jpg
35 ms
aa1_5.jpg
35 ms
00_520.jpg
34 ms
aa1_7.jpg
41 ms
aa1_31.jpg
42 ms
300x150%20%283%29_0.jpg
271 ms
25162463456_35efe439a7_o.jpg
46 ms
aa1_26_0.jpg
42 ms
25291461622_86d6320cb9_o.jpg
50 ms
thumb_4.jpg
55 ms
logo-blogazine-small-white-on-pink.png
54 ms
cover99.jpg
52 ms
head-feedburner.gif
52 ms
feed.png
53 ms
20160226_cover1_thumb.jpg
56 ms
300x150%20%283%29_0.jpg
58 ms
25162463456_35efe439a7_o.jpg
53 ms
20160220_thumb_maihed.jpg
55 ms
cb=gapi.loaded_0
41 ms
quote-head.jpg
471 ms
quote-body.jpg
217 ms
quote-leg-left.jpg
470 ms
2013
578 ms
a1
697 ms
a2
726 ms
a1
1276 ms
zrt_lookup.html
444 ms
show_ads_impl.js
182 ms
quote-footer.jpg
436 ms
quote-leg-right.jpg
443 ms
tpEPImsG-hT.css
492 ms
qCgU98_HbWI.css
551 ms
_rx8naC75Dy.js
679 ms
b94UUzHjapV.js
863 ms
0wM5s1Khldu.js
678 ms
TTCre3391I0.js
668 ms
ads
626 ms
fire.GIF
183 ms
a2
1031 ms
a3
1120 ms
osd.js
88 ms
ca-pub-5302548355457319.js
70 ms
ads
567 ms
sdk.js
166 ms
th_donate_1.8.js
620 ms
th_common_1.4.js
624 ms
system.base.css
91 ms
system.menus.css
218 ms
system.messages.css
212 ms
system.theme.css
214 ms
comment.css
215 ms
field.css
213 ms
node.css
344 ms
user.css
385 ms
views.css
386 ms
ctools.css
461 ms
alpha-reset.css
462 ms
alpha-mobile.css
461 ms
alpha-alpha.css
486 ms
formalize.css
503 ms
omega-text.css
504 ms
omega-branding.css
505 ms
omega-menu.css
506 ms
omega-forms.css
505 ms
omega-visuals.css
506 ms
global.css
507 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
157 ms
css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css
180 ms
css_LKLHxHgVOMz-MNKFnUma4-4RIgSj4pvSY2nskVkN8Ns.css
179 ms
css_D9ljCNt9BYU26ZmXmsdZKLoSObCaYxH15tmkN5wQtlE.css
183 ms
css_VFdBWSuFcaSSiEX83mjw2dXDcRRV0IsFSohDpZhLmrc.css
183 ms
css_jNZY2pFcG52OKxQWufeAKdwfAI1B8lEH_XBewZnhOPE.css
182 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
185 ms
js_obFUyTbqtcoGQtszVI46l1_oD927PzlDtlr_ilpYBqE.js
210 ms
js_Xdp_56Kwrjh9XNxqhxmaYOwIKVvPB-7wqAz_R60LA6w.js
194 ms
js_7qeIP5x1pp65EYN9l3ZhemvVP_ivW4oh0RbOXRf7TX4.js
200 ms
css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css
227 ms
blogazium-2016-alpha-default.css
485 ms
blogazium-2016-alpha-default-wide.css
487 ms
alpha-default-wide-12.css
485 ms
jquery.js
560 ms
jquery.once.js
498 ms
drupal.js
527 ms
th_BMyAsWMvOX3hjRa4ahkF2peKtUWwbAvATnU1BmZAWiU.js
528 ms
jquery.formalize.js
529 ms
omega-mediaqueries.js
527 ms
273 ms
1069183_10151549260386699_148296902_n.jpg
549 ms
wL6VQj7Ab77.png
146 ms
s7jcwEQH7Sx.png
145 ms
xd_arbiter.php
380 ms
xd_arbiter.php
575 ms
m_js_controller.js
144 ms
abg.js
201 ms
728x90-2_1.jpg
129 ms
tracker.js
2050 ms
picture-246-1456349751.jpg
268 ms
picture-63-1456610872.png
269 ms
picture-306-1456348942.jpg
268 ms
picture-322-1456348777.jpg
268 ms
picture-312-1456348874.jpg
267 ms
picture-293-1456349044.jpg
267 ms
picture-336-1456348625.jpg
345 ms
picture-275-1456349438.jpg
345 ms
picture-270-1456349512.jpg
345 ms
picture-272-1456349473.png
344 ms
googlelogo_color_112x36dp.png
343 ms
imgad
256 ms
nessie_icon_tiamat_white.png
291 ms
analytics.js
289 ms
s
177 ms
x_button_blue2.png
217 ms
I6-MnjEovm5.js
139 ms
f6T91Deal_q.js
140 ms
collect
27 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
7 ms
stat_gray.gif
271 ms
t.php
52 ms
collect
23 ms
like.php
78 ms
LVx-xkvaJ0b.png
41 ms
prachatai.org 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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
prachatai.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
prachatai.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
TH
TH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prachatai.org 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 Prachatai.org 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.
prachatai.org
Open Graph description is not detected on the main page of Prachatai. 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: