Hosting on Windows sever, problems with sitemap and Quick Cache

The initial page load is taking about 40 seconds!

The website is nothing heavy, I see that the generated html (620.1kB) is taking 92% of the time?

De-activate JetPack and activate the Twenty Eleven theme and see if that runs as slow?

Install the broken links plugin as well, as they can kill a website.

I use a windows server and use the basic setup with wp-super-cache

This test theme has slider and dynamic post images, with super cache loads in less than a second, so I would think there is a conflict somewhere!

HTH

David

An update: Hi David, Deactivated JetPack and am hesitant to change themes mid-afternoon.. Deactivating JetPack hasn’t seemed to help out on load time. If I remember correctly WordPress was working slow with the default theme on set up.

Could anyone help me set up Google Sitemap? I was hoping that it would work even though it is hosted on a Windows server.. any thoughts?

Deactivated JetPack and am hesitant to change themes mid-afternoon..

With the load being so slow I doubt if many visitors will wait over fourty seconds, most visitors will wait 2-3 seconds and they are gone!

Forget Google Sitemap, try wp-super-cache, and the broken link plugin!

David

Thanks David, I deleted JetPack, and to my dismay there were only minor improvements on page load time.. but not much!! GTMetrix gives me this feedback, https://gtmetrix.com/reports/sptrfa.org/GHHwJyOr
I do have broken link plugin, seems to be working fine.

Haven’t tried wp-super cache, wonder if there are walk-through setups someone could point me to?

I got as far as this message from WP Super Cache before getting stumped.

WP_CACHE constant set to false
The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command: define(‘WP_CACHE’, true);

Went to my ftp client and changed the last line to: define(‘WP_CACHE’, true); uploaded and now the same problem comes up. Line is set to false.

Any ideas?

I downloaded and tested the theme and calendar widget an all was fine, so it is specific to your setup!

Prehaps other members could have a look and add a comment??

Please edit your wp-config.php and add or edit the following line above the final require_once command:

Something Like lines 2 and 3 Before the include of the wp-settings.php!!

define('WP_DEBUG', false);

/* Added this line for WP-Super-Cache */
define('WP_CACHE', true);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

HTH

David

That was very helpful David, Thank you!!! I ran through the wp-content page and needed to move up above the require_once line. Now I am getting a warning, need I be worried about this?

Warning! /wp-content is writeable!

You should change the permissions on and make it more restrictive. Use your ftp client, or the following command to fix things: chmod 755

If I am working in a Windows server, there are not things like chmod 755 commands because I’ve been told is folder based access.

I am windows server and get the same message, I just ignore it as it is a Windows Server!

Regards

David

Great. Just one more hiccup in the process…
” Timestamps differ or were not found!”
Fetching https://www.sptrfa.org/ to prime cache: OK
Fetching first copy OK (1.html)
Fetching second copy OK (2.html)
The pages do not match! Timestamps differ or were not found!

So I followed these steps after testing the cached site:
Loaded homepage in IE9 to check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match. (Looked at the source, couldn’t even find the timestamp!!)

Enable logging on the Debug page here. That should help you track down the problem. (Enabled, looked at the ftp files created, found nothing helpful.)

You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself.

Checked page 1 and 2 saw no errors..

:/