Search Results for 'pagespeed'

But Lazy Load is useful for pagespeed, right?

And even if I disable I cant be sure if it fixed.

Hi Chris

Found that consolidated URL to speedup things https://forum.tagdiv.com/topic/tutorial-pagespeed-2015/

Yes, except with major WP core and structural changes, this means some things change in the child themes, too.

Also I’m an SEO nut going on 20 years now, so technically a child theme is a CSS redirect every page load, which isn’t a great idea … e.g., load CSS file, but wait, please redirect to the REAL css file now ? Google specifically recommends not doing that.

I usually look at the changelog to see WHAT files change — if it’s just some basic stuff, I can replace those couple of files and be done. For MAJOR upgrades they often have changes to child theme, too.

Been caught by that .. upshot – up to you. I just find it safer to work off main files, and this also removes some gremlins I run into with mod_pagespeed, caching, blah blah.

Having two sets of files in theme folder annoying to me. 🙂

Yeah… still hopefully the folks who make WordPress will blaze the trail and then everybody else will be able to use it from trickle down effect.

I’m particularly curious how it will work with those of us already using things like mod_pagespeed and mod_SPDY on our servers.

You can minify the style.css file by following my tips in my pagespeed optimization sticky post, as well as other tips/tricks for speeding up/optimizing your site — including a new method of compressing .js files without breaking them, recommended by Google. 🙂

Make sure you change the “name” of the theme in the style.css file, which will also appear in the appearance > themes panel. Basically you might do:

a) change theme folder /Newspaper/ >> /mysitename/ (be sure not to name same as a category or post!)
b) in your style.css, change the “name” of the theme (which populates the appearance data)

(might have to ‘reselect’ the new theme name in appearance > settings — might delete some settings, be sure to backup!!)

c) use something like mod_pagespeed or other system which removes all “comments” from HTML (plugin, CDN, etc.)
d) view page source in text editor, do search for old theme name
e) clear all caching on server/CDN, browser, if not done so already

That would change the “basic” name of the theme in the HTML to your new theme name.

Again, this won’t change the name of modules, plugins (e.g., speedbooster, td social plugin, etc.), or CSS elements with “td_classname” …

However it would fix things like

/wp-content/themes/mynewname/style.css

to show /mynewname/ in place of orig theme name.

• This reply was modified 10 years by simchris.

Thanks, it worked. Great theme. It increased pagespeed on my shitty Dreamhost shared server; ads CTR, pageview went up while having a cleaner design.

Also, you can see that the page is broken on mobile here too.

https://developers.google.com/speed/pagespeed/insights/?url=vrux.co&tab=mobile

-steve

theme works fine with mod_pagespeed …

you just need to setup a proper config file either at server level with dedicated box, or by manually specifying in htaccess file what to turn on explicitly — for example I found that CSS and JS minification does not work well — so it’s a “tuning” process for what is compatible with WordPress and what is not, a bit by trial and error, and also see my posts on this topic the past 18 months in forum as I have used it on our server since Jan. 2014 with TagDiv themes.

e.g.,

<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>

see the docs for mod_pagespeed on which settings you may wish to activate other than the default “safe” batch of MPS settings.

• This reply was modified 10 years by simchris.
• This reply was modified 10 years by simchris.

Thanks for the advice Chris! Not to add a layer of complexity but my hosting provider is wpengine and they supposedly do a lot of the server configuration to maximize the speed potential (mod_pagespeed is not available in their environment)

Just some input; I’d be cautious with autominify as that has caused problems with various folks; in many cases auto-minify of HTML is fine (we use mod_pagespeed for this); but for CSS and JS, I personally have found it’s better to MANUALLY do that (see my sticky optimization post topic on how to); as this ensures you know it works, and it’s not an “on the fly” issue but static from get-go.

Just some input on that one item 🙂

Well… it works for some folks and not for others — no idea why. I ran into this same issue using mod_pagespeed (which has built-in lazy load function option) on our site 15 months ago, and chose not to use it for same reason. I’d see randomly no images loaded. Meaning, the top of page items might load, but if somebody waited then scrolled down, there would be no images at all … super annoying.

The trade off with lazy loading is that some browsers and some setups just don’t exactly work consistently since it’s kind of an ajax load on demand thing — much like some of those long parallax one page website sometimes just crash the web browser which is super annoying (most folks have given up on that, thankfully).

I’ve disabled it on all our sites for this same “inconsistent” issue.

TagDiv support might have better answer … but that’s been my WTF? experience 🙂

• This reply was modified 10 years by simchris.

Did you
a) increase default memory in your wp-config.php file ?
b) turn off all plugins except visual composer to try to debug what might be causing overload?
c) optimize site for fewer queries, optimized photos, pagespeed, etc.

(a) is best thing to start with.

Any theme framework using Visual Composer will have that file – it’s not technically part of theme; so hundreds of themes using VC will have that payload, but it’s the plus and minus to this kind of fancy site.

You can minify the main css file per my suggestions in my sticky post on optimization, which helps quite a bit.

Also, luckily this stuff actually gets zipped/compressed when sent to browser and cached so not being loaded over and over.

There is also code in my optimization sticky on topic of disabling VC loading on post pages where it’s not used (at least in my case).

Sadly, for highly complex and “lots of features” sites, there *is* a big payload, but not so bad — some themes make it seem smaller by loading 10 diff CSS files, where here it’s all combined.

Standard size CSS for most complex themes is actually about 550KB — not 75KB. It’s not apples to apples, it’s apples to watermelons — footprint is quite different.

But you can optimize stuff quite a bit for speed and Google pagespeed rating, which should be the main target for using large complex “feature-packed” themes like this one.

That might not have helped, but some feedback (I’ve been doing webdev 20 years and using WP 10 years, so not totally nuts over here… at least most of the time) 😉