November 4, 2013 at 9:47 am #70846
I have a site that’s well suited to a theme like Magazine Pro, but it seems to be much slower than some of the other StudioPress themes. I’m basing that using tests from tools.pingdom.com, relying upon their New York server as a common test site. Also, I’m testing the themes on the StudioPress demo site, e.g., demo.studiopress.com/magazine.
Most StudioPress themes that I’ve tested have sub-second responses. Magazine Pro seems to jump well above into the 2 second range when I run the tests.
Is this because it uses a number of Featured Post widgets, or is there something else I can do to make it load faster?
November 4, 2013 at 10:47 am #70860
nutsandboltsModeratorPost count: 3130
The demo seems to be loading slowly because of the number of images on the page, but honestly, it’s impossible to know how a theme will perform until you use it on your site with your content. Different hosts and server configurations, as well as the number of requests on the page, will impact how quickly a site loads much more than what theme it uses.
November 4, 2013 at 12:00 pm #70876
That’s why I’m using the theme demo as a source. The assumption is that it’s hosted in its most favorable configuration and may only get slower as a user loads my stuff onto the theme.
Right now, it’s slower than the other models on the showroom floor. I’m trying to understand what elements are slowing it down, considering that it likely has the same hosting and underlying architecture.
November 5, 2013 at 12:41 am #71017
worldviewprParticipantPost count: 48
I am really happy using Sythesis hosting. Mag Pro is routinely loading at around 1.0-1.2 secs with page speed score 600-800, depending on images. per
But I am using CDN, Smush.it and W3TC. So it really is going to depend on your host, dom files, cache regimen, etc.
My biggest beef is that the chief bottlenecks are not the theme or host bu google font api and cloudfront and quantserve each costing anywhere from 200 to 400ms to load. I hope google fonts installed somehow is a way to mitigate this but rough going for me understanding best approach to that.November 5, 2013 at 11:48 am #71066
Thanks, that’s encouraging. My own site is on WP Engine and it needs a lot of optimization before I’m pleased. However, I’ve found the same issue with TypeKit or Google Fonts being a drag on the load times.
I still need to activate my CDN for my site and tweak a few other things. That’s why I was testing on the demo site to see a baseline compared to other themes. Magazine Pro is still slower than the other themes there.
November 5, 2013 at 9:00 pm #71180
OK, working with Pingdom showed me where to find my bottlenecks. I learned something that many others already know. JetPack is a huge suck on performance. While I like the Stats module, I can do without most of it. Since I have Google Analytics, I deactivated JetPack (though I do like its statistics better than Google’s).
Short story, now I’m getting better performance on my site with Magazine Pro than the demo site on StudioPress. It’s still a heavier child theme than some of the others, but just killing JetPack was a major improvement in performance.
November 5, 2013 at 10:14 pm #71194
worldviewprParticipantPost count: 48
That’s great news, William. I obsess about this all the time. I have a love-hate relationship with Jetpack and am entering a new hate cycle. I need to solve the google font api latency. Will also jettison jetpack and alexa/quancast apis. worhtless for a site like mine. If there is any clue out there on how to make cloud front and google font servers not be such a drag let us know.
You must be logged in to reply to this topic.