Jump to content


Photo
- - - - -

Jigoshop vs WP e-Commerce


Best Answer Rob , 12 February 2013 - 10:35 PM

Pingdom says your site loads in 1.85 seconds from Dallas - a speed at which most would be jealous.

 

There's a .08 second delay loading the domain (server issue, not PageLines) then the CSS delays due to two plugins: Shadowbox and Jigoshop. PageLines CSS is the fourth CSS to load.

 

Still, out of these four CSS loads, they're cumulatively only adding about 530 milliseconds. Nothing to complain about there. So actually, your site is pretty quick.

Go to the full post


  • Please log in to reply
6 replies to this topic

#1 lakersalex

lakersalex

    Super Member

  • Members
  • 102 posts
  • LocationLos Angeles
  • Country: Country Flag

Posted 11 February 2013 - 09:25 PM

just wondering how many people are using either Jigoshop vs WP e-Commerce with Pagelines. I like Jigoshop but it seems to crawl. I've tried many speed tricks and it seems like nothing really helps. Will WP e-Commerce be any better?



#2 Rob

Rob

    One Smart Egg

  • Members
  • 13575 posts
  • LocationEast Coast, USA
  • Framework Version:The Latest, of course
  • Country: Country Flag

Posted 11 February 2013 - 09:55 PM

Hi,

 

I'm not sure this is an issue with JigoShop or simply with your server. I'd go with the server first as it's the easier solution at hand.  Contact your host and ask them how much RAM is available for PHP processes.  If the value is less than 32Mb, then ask for an increase to at least 64Mb to see if this improves the condition; 128Mb is better.  The host can make the necessary changes for you.

 

I'm not sure what kind of hosting package you're on, but some, less expensive packages may not have suitable resources for eCommerce plugins.

 

Let us know what the host says.



#3 lakersalex

lakersalex

    Super Member

  • Members
  • 102 posts
  • LocationLos Angeles
  • Country: Country Flag

Posted 11 February 2013 - 11:02 PM

Hi Rob,

 

I'm on a bluehost reseller account.

 

I updated to PHP 5.3 with 256mb memory. the time to first byte is still poor, around 1100ms.

 

When I test a php page that simply views the php info "<?php phpinfo(); ?>" the time to first byte is 500ms



#4 Rob

Rob

    One Smart Egg

  • Members
  • 13575 posts
  • LocationEast Coast, USA
  • Framework Version:The Latest, of course
  • Country: Country Flag

Posted 12 February 2013 - 02:41 AM

Which site is this?

 

Did you test the site on Pingdom.com?



#5 lakersalex

lakersalex

    Super Member

  • Members
  • 102 posts
  • LocationLos Angeles
  • Country: Country Flag

Posted 12 February 2013 - 04:56 PM

heathertaylorhome.com

the last pingdom test showed a 1.3 second lag right off the bat, then lags on retrieving css files and some js files.

here's a list of what i've done:

1. Add to wp-config.php
define( 'LESS_FILE_MODE', true )

2. Increase PHP memory limit to 128mb, add to wp-config.php

define('WP_MEMORY_LIMIT', '128M');

3. Disable the Revisions, add to wp-config.php

define('WP_POST_REVISIONS', 2 );

4. Change autosave interval, add to wp-config.php

define('AUTOSAVE_INTERVAL', 240 );

5. disable ET Tags in .htaccess

Header unset ETag
FileETag None

6. Browser Caching in .htaccess

# BEGIN Expire headers
<ifModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 5 seconds"
ExpiresByType image/x-icon "access plus 2592000 seconds"
ExpiresByType image/jpeg "access plus 2592000 seconds"
ExpiresByType image/png "access plus 2592000 seconds"
ExpiresByType image/gif "access plus 2592000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2592000 seconds"
ExpiresByType text/css "access plus 604800 seconds"
ExpiresByType text/javascript "access plus 216000 seconds"
ExpiresByType application/javascript "access plus 216000 seconds"
ExpiresByType application/x-javascript "access plus 216000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</ifModule>
# END Expire headers

# BEGIN Cache-Control Headers
<ifModule mod_headers.c>
<filesMatch "\.(ico|jpe?g|png|gif|swf)$">
Header set Cache-Control "public"
</filesMatch>
<filesMatch "\.(css)$">
Header set Cache-Control "public"
</filesMatch>
<filesMatch "\.(js)$">
Header set Cache-Control "private"
</filesMatch>
<filesMatch "\.(x?html?|php)$">
Header set Cache-Control "private, must-revalidate"
</filesMatch>
</ifModule>
# END Cache-Control Headers


7. set memory limit in php.ini in root

memory_limit = 128M

8. cloudflare

#6 Rob

Rob

    One Smart Egg

  • Members
  • 13575 posts
  • LocationEast Coast, USA
  • Framework Version:The Latest, of course
  • Country: Country Flag

Posted 12 February 2013 - 10:35 PM   Best Answer

Pingdom says your site loads in 1.85 seconds from Dallas - a speed at which most would be jealous.

 

There's a .08 second delay loading the domain (server issue, not PageLines) then the CSS delays due to two plugins: Shadowbox and Jigoshop. PageLines CSS is the fourth CSS to load.

 

Still, out of these four CSS loads, they're cumulatively only adding about 530 milliseconds. Nothing to complain about there. So actually, your site is pretty quick.


  • lakersalex likes this

#7 lakersalex

lakersalex

    Super Member

  • Members
  • 102 posts
  • LocationLos Angeles
  • Country: Country Flag

Posted 19 February 2013 - 01:10 AM

OK I'll live with it then. The speed reported doesn't seem to jive with my actual experience, but perhaps I'm being too obsessive. If there are other speed tips listed in the forums, please let me know. Thank you for your attention Rob!