17.7 sec in total
3.3 sec
14 sec
463 ms
Welcome to harvest365.org homepage info - get ready to check Harvest 365 best content for Taiwan right away, or after learning these important things about harvest365.org
善耕365公益媒合平台
Visit harvest365.orgWe analyzed Harvest365.org page load time and found that the first response time was 3.3 sec and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
harvest365.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.7 s
3/100
25%
Value11.3 s
5/100
10%
Value1,870 ms
9/100
30%
Value0.03
100/100
15%
Value11.2 s
20/100
10%
3295 ms
1033 ms
297 ms
5 ms
298 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 78% of them (101 requests) were addressed to the original Harvest365.org, 7% (9 requests) were made to Scontent.xx.fbcdn.net and 5% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Harvest365.org.
Page size can be reduced by 865.6 kB (10%)
8.9 MB
8.0 MB
In fact, the total size of Harvest365.org main page is 8.9 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. 65% of websites need less resources to load. Images take 8.4 MB which makes up the majority of the site volume.
Potential reduce by 131.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 20.4 kB, which is 13% 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 131.3 kB or 85% of the original size.
Potential reduce by 485.3 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. Harvest 365 images are well optimized though.
Potential reduce by 72.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 72.6 kB or 63% of the original size.
Potential reduce by 176.5 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. Harvest365.org needs all CSS files to be minified and compressed as it can save up to 176.5 kB or 74% of the original size.
Number of requests can be reduced by 19 (15%)
127
108
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Harvest 365. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
harvest365.org
3295 ms
app.css
1033 ms
xwg-all.css
297 ms
font-awesome.min.css
5 ms
dyfrom.js
298 ms
application.js
1775 ms
event_carousel.js
298 ms
raty.min.js
405 ms
event_index.js
406 ms
xwg-select.js
406 ms
platform.js
737 ms
jquery.cookie.js
622 ms
organization_address.js
689 ms
myjs.js
689 ms
home_page.js
615 ms
jquery.slides.min.js
875 ms
fancybox_overlay-e143dff05b5d9a5ffc815090c8641f6a.png
90 ms
harvest-logo.png
590 ms
191611377991.jpg
1923 ms
051220455457.jpg
1329 ms
261427418964.jpg
1921 ms
251135055422.png
1926 ms
171540287100.png
2506 ms
211500299234.jpg
2842 ms
prevArrow.png
1922 ms
nextArrow.png
1923 ms
151250003813.jpg
2223 ms
145448774673811.jpg
2482 ms
221158162876.png
2633 ms
300_144040958482652.jpg
2475 ms
311437441872.png
3105 ms
031630477596.png
3505 ms
241658333717.png
3518 ms
300_145614120612543.jpg
3240 ms
241145205525.jpg
3518 ms
300_145586938753173.jpg
3583 ms
221108051173.png
3709 ms
181019553295.jpg
4124 ms
161208555569.jpg
4412 ms
051715391435.jpg
4112 ms
271106179088.png
4273 ms
221512324268.png
4360 ms
sdk.js
201 ms
031549057095.jpg
5433 ms
142139161042.png
4960 ms
151755345712.jpg
4792 ms
011136267421.jpg
5113 ms
11391374_1139584289392037_388513876219273295_n.jpg
328 ms
12662014_997882196951107_8085815985659020284_n.jpg
414 ms
11988506_1044848848861615_1018484839714843421_n.jpg
440 ms
11898869_705863686211710_5975077405980686395_n.jpg
406 ms
12552954_965179023572009_6760467852229197919_n.jpg
399 ms
11235438_1246575105357054_939339691603965314_n.jpg
487 ms
d93e757e1104.png
119 ms
10393814_1078849652157147_8813593458710182437_n.jpg
253 ms
10956647_677815835656695_9091094703820988301_n.jpg
291 ms
582689_3746594430472_55942287_n.jpg
315 ms
cf5f02a7dec1.png
50 ms
fontawesome-webfont.woff
49 ms
analytics.js
34 ms
222 ms
217 ms
161646351461.png
5133 ms
xd_arbiter.php
181 ms
xd_arbiter.php
315 ms
071415099368.jpg
4788 ms
021056565801.jpg
4795 ms
collect
48 ms
300_145216044827572.jpg
5395 ms
145611731521828.jpg
5196 ms
300_145437751126424.jpg
5344 ms
011644137483.png
5510 ms
011420436044.jpg
4984 ms
252315467398.png
4616 ms
more.png
3977 ms
touxiang.jpg
4299 ms
200_144152405719824.jpg
4566 ms
200_144116445452437.jpg
4430 ms
thumb_928c3fc2-bff8-47be-b741-94b6a8fee32e.JPG
4586 ms
like.php
113 ms
like.php
90 ms
like.php
91 ms
rU2ubZ6l1Q5.js
298 ms
LVx-xkvaJ0b.png
318 ms
thumb_e364f077-9a8f-46e6-a363-255aa7d3da02.png
4445 ms
39d30880-4690-432d-981d-fda93cb9e384.jpg
4134 ms
b1c1725c-8a83-426e-af4d-e8172f513c65.jpg
4468 ms
400_142933820849905.jpg
4928 ms
like.php
138 ms
like.php
95 ms
organizationLogo.png
4343 ms
4adb858e-60c8-498f-888d-88a7b54478eb.png
4154 ms
400_142658828017290.jpg
4092 ms
142260285474783.png
4023 ms
842aef80-0b8d-4707-ad5d-833d9419db7a.jpg
4034 ms
400_143591018556315.jpg
4193 ms
142743957214919.png
4059 ms
partner-pre-7c145529d9ba1396dda2bf8231a358c4.png
3908 ms
145647338263245.png
3994 ms
145205203492419.png
3914 ms
145628043019138.png
3957 ms
145586911186531.png
3852 ms
145578223215342.png
3671 ms
145389229248280.png
3881 ms
145577633368562.png
3336 ms
145553195147339.png
3736 ms
145455221276235.png
3490 ms
144739674360119.png
3664 ms
145406173795791.png
3690 ms
145406203376002.png
3552 ms
145342574636502.png
3400 ms
145335151498413.png
3872 ms
142623121529111...png
3580 ms
145023097510548.png
3665 ms
145256314616423.png
3569 ms
142907176715612.png
3404 ms
400_145223840118872.jpg
3347 ms
145215199518738.png
3822 ms
partner-next-b7e4ccceeded6a8c91864648296bf1b1.png
3414 ms
Life.com.png
3284 ms
ETtoday.png
3265 ms
sina.png
3313 ms
lovefly.png
3253 ms
weibo.png
3395 ms
xlf.jpg
3116 ms
iVicon.png
3120 ms
gyzx.jpg
3159 ms
closebutton.png
2961 ms
pagination.png
3094 ms
harvest365.org 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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
harvest365.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
harvest365.org SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Harvest365.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Harvest365.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.
harvest365.org
Open Graph description is not detected on the main page of Harvest 365. 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: