extreme Pageload time (20 secs and up)

Hello folks,

I'm in desperate need of help. I'm developing a new site with MODX 2.2 and while testing it, I get unbelievably high page load times. This thing is bleeding hard. I'm getting 10 seconds if I'm lucky or up to 50 seconds sometimes on any page.

I've minified my scripts and CSS as always and yes this site is slighly bigger than any other project I've worked on, but these results are beyond rediculous. I can't GZIP the content since the hosting company doesn't support the compression due to high CPU usage. To be honest, I've never had to do that anyway. I know there's a problem this time.

Here's a simple page for instance where I'm loading minified js files.


Notice that even viewing the source code takes longer than usual.

Please disregard any design flaws as its being developped as we speak.

Here's my environment: PHP 5.2.17/MYSQL 5.1.51 [ed. note: treigh last edited this post 14 years, 6 months ago.]

Do you have many getResources/Wayfinder input and output modifiers calls?

Yes. On certain pages I'm using a lot of output modifiers and yes I'm using a lot of getResources calls on certain pages. Would that be an issue

Just so people know,

I've been reducing the number of getResources calls as well as output modifiers like @microcipcip suggested and where needed, I'm also serving mobile browser agents and legacy IE special CSS files and javascript using recommendations foud here: http://rtfm.modx.com/display/revolution20/Adding+CSS+and+JS+to+Your+Pages+Through+Snippets.
This ensures that those files are only sent to the browser agent if it matches th criteria.

The steps above in addition to more CSS optimization and minification as well as Javascript packing seem to have cut the extreme load times in half. I'm still not close to 2 secs page load, but its much better. Too bad my hosting company doesn't provide GZIP compression

I hope this helps someone [ed. note: treigh last edited this post 14 years, 6 months ago.]

Have you read this?
http://www.markhamstra.com/modx-blog/2011/10/caching-guidelines-for-modx-revolution/

I wish I saw this earlier. It could have saved me lots of time. Excellent article. Thx for sharing.

By the way, if you use a TV in getresource then write a query something like that:



This will add significantly speed

If any of the TVs don't need processing (i.e., you can use the raw value), you can also add &processTVlist to specify which ones need processing.

$includeTVlist=`1,3,6,9`
&processTVlist=`1,3`


Using the IDs of the TVs rather than their names will speed things up slightly too.

To get maximum speed, you can write your own custom snippet to replace getResources.

The bottom line, however, may be that your server is just overloaded by the number of visitors you get, especially if you're on a shared server.

------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

maybe you can try getCache - http://www.jasoncoward.com/technology/2010/10/simple-content-caching-with-getcache.html

Thx all.

A combinatiion of tips above plus additional file optimization seems to have stop the bleeding. A VPS hosting accounf will definetly be the way forward. A shared server is really not suited for this site.