GeoDirectory, Varnish, and Cloudways
This topic contains 22 replies, has 5 voices, and was last updated by Guust 9 years, 1 month ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: cloudways, Events, gd booster, optimization, performance, varnish
-
AuthorPosts
-
September 28, 2015 at 8:44 pm #54912
Okay, I’m slowly but surely making some improvements and I’m going to try the multisite idea on my staging site–thank you.
I added this to htaccess and my score page speed score went up by about 5%. Do you see anything that would conflict with GD?
# Optimize cache-control <IfModule mod_expires.c> ExpiresActive on ExpiresDefault "access plus 1 month" ExpiresByType image/gif "access plus 1 month" ExpiresByType image/png "access plus 1 month" ExpiresByType image/jpg "access plus 1 month" ExpiresByType image/jpeg "access plus 1 month" ExpiresByType text/html "access plus 3 days" ExpiresByType text/xml "access plus 1 seconds" ExpiresByType text/plain "access plus 1 seconds" ExpiresByType application/xml "access plus 1 seconds" ExpiresByType application/rss+xml "access plus 1 seconds" ExpiresByType application/json "access plus 1 seconds" ExpiresByType text/css "access plus 1 week" ExpiresByType text/javascript "access plus 1 week" ExpiresByType application/javascript "access plus 1 week" ExpiresByType application/x-javascript "access plus 1 week" ExpiresByType image/x-ico "access plus 1 year" ExpiresByType image/x-icon "access plus 1 year" ExpiresByType application/pdf "access plus 1 month" <IfModule mod_headers.c> Header unset ETag Header unset Pragma Header unset Last-Modified Header append Cache-Control "public, no-transform, must-revalidate" </IfModule> </IfModule>
Thanks so much, Paolo.
September 28, 2015 at 9:26 pm #54914Hi again,
Leveraging browser cache by adding far away expiring headers can only be good.
You are welcome!
September 30, 2015 at 2:36 pm #55184Just to finalize my findings, here’s data from Plugin Performance Profiler that shows that GD Events plugin sucks up a lot of resources and adds immensely to page load time. I have deactivated the plugin because my events data was lost in an update, but I think this is good information to share anyway. This was tested over 3 days, and each report shows that Events is what is slowing down my site.
REPORT #1
WordPress Plugin Profile Report
===========================================
Report date: September 30, 2015
Theme name: unknown
Pages browsed: 23
Avg. load time: 3.8228 sec
Number of plugins: 24
Plugin impact: 89.82% of load time
Avg. plugin time: 3.4335 sec
Avg. core time: 0.0873 sec
Avg. theme time: 0.1712 sec
Avg. mem usage: 58.65 MB
Avg. ticks: 51,406
Avg. db queries : 89.48
Margin of error : 0.1308 secPlugin list:
===========================================
P3 (Plugin Performance Profiler) – 0.0122 sec – 0.36%
GoodBye Captcha – 0.0380 sec – 1.11%
GoodBye Captcha BuddyPress – 0.0006 sec – 0.02%
Akismet – 0.0031 sec – 0.09%
All In One Seo Pack – 0.0563 sec – 1.64%
bbPress – 0.0810 sec – 2.36%
BuddyPress Cover Photo – 0.0016 sec – 0.05%
Buddypress – 0.2160 sec – 6.29%
GeoDirectory BuddyPress Integration – 0.0292 sec – 0.85%
GeoDirectory Claim Manager – 0.0052 sec – 0.15%
GeoDirectory Custom Post Types – 0.0047 sec – 0.14%
GeoDirectory Events – 2.4438 sec – 71.18%
GD Booster – 0.0307 sec – 0.90%
GeoDirectory Payment Manager – 0.0339 sec – 0.99%
GeoDirectory – 0.1297 sec – 3.78%
WPBakery Visual Composer – 0.1615 sec – 4.70%
K Elements – 0.0153 sec – 0.45%
MailChimp for WordPress Lite – 0.0171 sec – 0.50%
MailChimp Sync – 0.0158 sec – 0.46%
myCRED – 0.0328 sec – 0.95%
External Links – 0.0299 sec – 0.87%
SumoMe – 0.0008 sec – 0.02%
Tweet Wheel Pro – 0.0526 sec – 1.53%
Wordfence Security – 0.0214 sec – 0.62%REPORT #2
WordPress Plugin Profile Report
===========================================
Report date: September 28, 2015
Theme name: Kleo Child
Pages browsed: 35
Avg. load time: 4.5470 sec
Number of plugins: 27
Plugin impact: 87.81% of load time
Avg. plugin time: 3.9925 sec
Avg. core time: 0.1557 sec
Avg. theme time: 0.2373 sec
Avg. mem usage: 140.80 MB
Avg. ticks: 66,020
Avg. db queries : 133.37
Margin of error : 0.1615 secPlugin list:
===========================================
P3 (Plugin Performance Profiler) – 0.0057 sec – 0.14%
Akismet – 0.0115 sec – 0.29%
All In One Seo Pack – 0.1054 sec – 2.64%
bbPress – 0.2097 sec – 5.25%
BuddyPress Cover Photo – 0.0033 sec – 0.08%
Buddypress – 0.4141 sec – 10.37%
GeoDirectory BuddyPress Integration – 0.0477 sec – 1.19%
GeoDirectory Claim Manager – 0.0166 sec – 0.42%
GeoDirectory Custom Post Types – 0.0154 sec – 0.39%
GeoDirectory Events – 2.0193 sec – 50.58%
GD Booster – 0.0212 sec – 0.53%
GeoDirectory Payment Manager – 0.0910 sec – 2.28%
GeoDirectory – 0.2966 sec – 7.43%
Go – Responsive Pricing & Compare Tables – 0.0820 sec – 2.05%
WPBakery Visual Composer – 0.2846 sec – 7.13%
K Elements – 0.0293 sec – 0.73%
MailChimp for WordPress Lite – 0.0394 sec – 0.99%
MailChimp Sync – 0.0264 sec – 0.66%
myCRED – 0.0693 sec – 1.74%
External Links – 0.0014 sec – 0.03%
SumoMe – 0.0006 sec – 0.01%
Revive old post Pro Add-on – 0.0032 sec – 0.08%
Revive Old Post (Former Tweet Old Post) – 0.0168 sec – 0.42%
Tweet Wheel Pro – 0.0865 sec – 2.17%
Wordfence Security – 0.0679 sec – 1.70%
WP to Twitter – 0.0222 sec – 0.56%
Wp Tweets Pro – 0.0053 sec – 0.13%REPORT #3
WordPress Plugin Profile Report
===========================================
Report date: September 28, 2015
Theme name: Kleo Child
Pages browsed: 9
Avg. load time: 4.7731 sec
Number of plugins: 27
Plugin impact: 73.89% of load time
Avg. plugin time: 3.5269 sec
Avg. core time: 0.5209 sec
Avg. theme time: 0.4915 sec
Avg. mem usage: 146.97 MB
Avg. ticks: 73,191
Avg. db queries : 162.89
Margin of error : 0.2338 secPlugin list:
===========================================
P3 (Plugin Performance Profiler) – 0.0062 sec – 0.17%
Akismet – 0.0141 sec – 0.40%
All In One Seo Pack – 0.1308 sec – 3.71%
bbPress – 0.2535 sec – 7.19%
BuddyPress Cover Photo – 0.0031 sec – 0.09%
Buddypress – 0.4386 sec – 12.44%
GeoDirectory BuddyPress Integration – 0.0811 sec – 2.30%
GeoDirectory Claim Manager – 0.0160 sec – 0.45%
GeoDirectory Custom Post Types – 0.0190 sec – 0.54%
GeoDirectory Events – 1.3413 sec – 38.03%
GD Booster – 0.0169 sec – 0.48%
GeoDirectory Payment Manager – 0.1099 sec – 3.12%
GeoDirectory – 0.2912 sec – 8.26%
Go – Responsive Pricing & Compare Tables – 0.0828 sec – 2.35%
WPBakery Visual Composer – 0.3319 sec – 9.41%
K Elements – 0.0350 sec – 0.99%
MailChimp for WordPress Lite – 0.0390 sec – 1.11%
MailChimp Sync – 0.0260 sec – 0.74%
myCRED – 0.0763 sec – 2.16%
External Links – 0.0014 sec – 0.04%
SumoMe – 0.0009 sec – 0.02%
Revive old post Pro Add-on – 0.0109 sec – 0.31%
Revive Old Post (Former Tweet Old Post) – 0.0175 sec – 0.50%
Tweet Wheel Pro – 0.0841 sec – 2.38%
Wordfence Security – 0.0699 sec – 1.98%
WP to Twitter – 0.0235 sec – 0.67%
Wp Tweets Pro – 0.0061 sec – 0.17%September 30, 2015 at 3:05 pm #55192Hi Dee,
I’ve asked Stiofan to reply. As far as I know performance profiler isn’t reliable at all. Results from Query monitor are the only one I’d consider.
Stiofan will give you more insights in a minute.
Thanks
September 30, 2015 at 3:16 pm #55196Hi Dee,
The profile plugins is about as reliable as my first car…
Attached is the results on my server (with 16 plugins) going my those results i should immediately disable P3 profiler…Do you see a 71% increase in speed when events is disabled?
Thanks,
Stiofan
September 30, 2015 at 7:07 pm #55249LOL. Your graph is a bit disheartening. Unfortunately I deleted some other plugins so I can’t retest it, but I’ll take your word for it. You can go ahead and close this thread, thanks.
October 28, 2015 at 2:54 am #58228I read through this thread. According to Stiopan, GD Events plugin is not using up a lot of resources and reducing page load, correct? I purchased Events plugin but I never activated it because of this thread. Please let me know that it’s ok to use Events plugin.
October 28, 2015 at 12:04 pm #58243Hi Lee, it is OK to activate GD Events. Let us know if you have any troubles with it.
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket