16.1 sec in total
1 sec
14.8 sec
259 ms
Visit prayod.com now to see the best up-to-date Prayod content for Thailand and also check out these interesting facts you probably never knew about prayod.com
ประโยชน์ดอทคอม(prayod.com) เป็นเว็บไซต์ให้ข้อมูลเกี่ยวกับการดูแลสุขภาพ ประโยชน์ของผัก ผลไม้ อาหาร และสมุนไพร ฯลฯ
Visit prayod.comWe analyzed Prayod.com page load time and found that the first response time was 1 sec and then it took 15.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
prayod.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value8.4 s
2/100
25%
Value7.1 s
30/100
10%
Value150 ms
95/100
30%
Value0.783
5/100
15%
Value6.8 s
55/100
10%
1011 ms
566 ms
36 ms
48 ms
554 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 47% of them (44 requests) were addressed to the original Prayod.com, 12% (11 requests) were made to Apis.google.com and 10% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (11.8 sec) belongs to the original domain Prayod.com.
Page size can be reduced by 725.8 kB (28%)
2.6 MB
1.9 MB
In fact, the total size of Prayod.com main page is 2.6 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. 80% 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 125.0 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 125.0 kB or 81% of the original size.
Potential reduce by 77.5 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. Prayod images are well optimized though.
Potential reduce by 316.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 316.3 kB or 72% of the original size.
Potential reduce by 206.9 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. Prayod.com needs all CSS files to be minified and compressed as it can save up to 206.9 kB or 81% of the original size.
Number of requests can be reduced by 48 (59%)
82
34
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prayod. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
prayod.com
1011 ms
wp-emoji-release.min.js
566 ms
css
36 ms
css
48 ms
font-awesome.min.css
554 ms
main.min.css
839 ms
swipebox.css
559 ms
easy-social-share-buttons.css
848 ms
bbpress.css
587 ms
style.css
826 ms
jquery.js
1954 ms
jquery-migrate.min.js
846 ms
jquery.swipebox.js
1170 ms
jquery.flexslider.js
1649 ms
modernizr.custom.js
1116 ms
affix.js
1126 ms
jquery.fitvids.js
1127 ms
themed-profiles.js
1394 ms
jsapi
23 ms
t13n
35 ms
platform.js
58 ms
masonry.min.js
1405 ms
jquery.masonry.min.js
1404 ms
jquery.imageScroll.min.js
1458 ms
pukka.js
1672 ms
essb-sticky-sidebar.js
1680 ms
wp-embed.min.js
1682 ms
pinit.js
17 ms
t13n
18 ms
css
47 ms
analytics.js
19 ms
poweredby_FFFFFF.gif
89 ms
avatar.png
291 ms
logo.png
290 ms
facebook.png
290 ms
google.png
310 ms
twitter.png
291 ms
all.js
88 ms
widgets.js
16 ms
branding.css
79 ms
%E0%B8%81%E0%B8%A3%E0%B8%B0%E0%B8%94%E0%B8%B2%E0%B8%94-450x585.jpg
4243 ms
%E0%B8%81%E0%B8%A3%E0%B8%B0%E0%B8%94%E0%B8%B1%E0%B8%87%E0%B8%87%E0%B8%B2%E0%B8%AA%E0%B8%87%E0%B8%82%E0%B8%A5%E0%B8%B2-450x326.jpg
3974 ms
%E0%B8%81%E0%B8%A3%E0%B8%B0%E0%B8%8A%E0%B8%B2%E0%B8%A2-2.jpg
4532 ms
%E0%B8%81%E0%B8%81%E0%B8%A3%E0%B8%B1%E0%B8%87%E0%B8%81%E0%B8%B2-450x406.jpg
7398 ms
%E0%B8%9E%E0%B8%B7%E0%B8%8A%E0%B8%9C%E0%B8%B1%E0%B8%81-450x311.jpg
3984 ms
%E0%B9%81%E0%B8%AD%E0%B8%9B%E0%B9%80%E0%B8%9B%E0%B8%B4%E0%B8%A5-450x302.jpg
4242 ms
%E0%B9%84%E0%B8%82%E0%B9%88-450x600.jpg
4774 ms
%E0%B8%82%E0%B9%88%E0%B8%B2-450x422.jpg
9421 ms
%E0%B9%80%E0%B8%9B%E0%B8%A5%E0%B8%B7%E0%B8%AD%E0%B8%81%E0%B8%95%E0%B9%89%E0%B8%99%E0%B8%AA%E0%B8%99-450x600.jpg
10077 ms
%E0%B9%83%E0%B8%9A%E0%B8%AD%E0%B9%88%E0%B8%AD%E0%B8%99%E0%B8%9A%E0%B8%B2%E0%B8%A3%E0%B9%8C%E0%B9%80%E0%B8%A5%E0%B8%A2%E0%B9%8C-450x435.jpg
9860 ms
%E0%B9%83%E0%B8%9A%E0%B8%A1%E0%B8%B0%E0%B8%A3%E0%B8%B8%E0%B8%A1-450x519.jpg
9589 ms
%E0%B8%94%E0%B8%AD%E0%B8%81%E0%B8%84%E0%B8%B3%E0%B8%9D%E0%B8%AD%E0%B8%A2-450x600.jpg
10069 ms
%E0%B9%81%E0%B8%AD%E0%B8%9B%E0%B9%80%E0%B8%9B%E0%B8%B4%E0%B8%A5%E0%B9%84%E0%B8%8B%E0%B9%80%E0%B8%94%E0%B8%AD%E0%B8%A3%E0%B9%8C-450x459.jpg
10155 ms
%E0%B8%AA%E0%B9%84%E0%B8%9B%E0%B8%A3%E0%B8%B9%E0%B8%A5%E0%B8%B4%E0%B8%99%E0%B9%88%E0%B8%B2-450x423.jpg
10650 ms
%E0%B8%AA%E0%B9%89%E0%B8%A1%E0%B9%81%E0%B8%82%E0%B8%81.jpg
10069 ms
%E0%B8%9E%E0%B8%A3%E0%B8%B8%E0%B8%99.jpg
11835 ms
collect
14 ms
branding.css
28 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
29 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
30 ms
Uxzkqj-MIMWle-XP2pDNAA.ttf
71 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
71 ms
fontawesome-webfont.woff
10542 ms
pR0sBQVcY0JZc_ciXjFsK5GUMC6XtjipT3aj9UHYjEM.ttf
70 ms
kH7K4InNTm7mmOXXjrA5v-Fc6ciOy_fNLnSqTl1JRpg.ttf
70 ms
72 ms
33 ms
xd_arbiter.php
73 ms
xd_arbiter.php
190 ms
transliteration.css
11 ms
transliteration.I.js
50 ms
16 ms
inputtools.js
14 ms
plusone.js
131 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
59 ms
cb=gapi.loaded_0
85 ms
cb=gapi.loaded_1
84 ms
follow
236 ms
pinit_main.js
121 ms
cb=gapi.loaded_2
42 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.th.html
46 ms
like.php
51 ms
postmessageRelay
89 ms
qeKvIRsJabD.js
242 ms
LVx-xkvaJ0b.png
244 ms
3193398744-postmessagerelay.js
55 ms
rpc:shindig_random.js
41 ms
rs=AGLTcCPJwk0CEvdYpVXR9fDZ9o-zFvpVZg
9 ms
rs=AGLTcCOJ4AMNA1EZSgGPzZnainRbXAPPWA
21 ms
rs=AGLTcCMnfUevIXaRz2EwrgydJvTaUuiKww
59 ms
cb=gapi.loaded_0
80 ms
jot
112 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
80 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
81 ms
prayod.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible name
prayod.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
prayod.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
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 Prayod.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 Prayod.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.
prayod.com
Open Graph description is not detected on the main page of Prayod. 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: