Search Results for 'pagespeed'

Why would the theme have anything to do with URLs posted on Facebook ?

The theme has nothing to do with how URLs are parsed. Meaning, if the URL you share to FB is correct and actually works, and somebody clicks that link – it will work if the site is accessible.

That is handled by your DNS, web server, and the ISP being able to resolve the DNS pointing at the IP where your website is hosted.

It might be a setting you have for Android users, or it may be that the caching of your CSS is mismatched on server and some android users or chrome users where chrome caches websites, is loading old CSS and not the new CSS and page will not load properly.

In those cases you need to clear server cache quite completely, where applicable; and a visitor who has a browser which doesn’t reload the CSS properly would need to hit “refresh” in their mobile browser to get the new CSS.

Sometimes you can force this by setting a very short TTL just for the CSS, like one hour, and let it be that way for a week — bad for pagespeed, but can “force” some browsers to make sure they only see new site CSS.

Might not be your issues; just a thought 🙂

Hi,

did you find any solution? I like to use WPtouch too, because it’s much faster than the responsive feature. Google Pagespeed 49 points to 73.

Or do you have any plans to speed up the Newsmag responsive feature?

Thank you!

1) turn off all plugins except VC
2) increase memory via the wp-config.php to 128MB or more (this is in addition to memory setting for php.ini in your hosting account – you need to do BOTH for WordPress to actually use more than 40MB)
3) be sure to turn off/clear all server caching to debug; turn off mod_pagespeed if using; if using CMS then you need to fully expire old files and refresh new ones.
4) create new page, save it; then EDIT it to add VC features.

Might help!

For basic minification of the CSS and possibly main js files, see my optimization guide.

Be aware that there is really no 100% way to fully optimize loading the above the fold content with any commercial theme like this one — this is because there are many options and functions being loaded in order to render the page at all, and to provide folks to create totally different designs.

Many articles have been written online about getting a perfect score with PageSpeed and WordPress and that requires custom building a theme from scratch and setting up regions where CSS and js are loaded conditionally and in series based on the content sections. Very complex and outside the scope of commercial themes.

Limiting things like mega menus can help, making sure any external resources load via async (we used to use addthis for social buttons on our sites and had to ‘hack’ that to add async loading of their js, because they were too stupid to do it with one line of code in their WP plugin).

Often to get the best “real world” score for your site, you need to disable any/all things which load externally (ads, etc.) and then test that. Optimize. Then switch on external things, optimize “if possible” and then realize the “real score” doesn’t count the Google ads stuff.

You can’t control caching of external elements (time to live), or minification of external resources. With Google fonts you can load the CSS locally in your own style sheet, then simply “draw” the fonts from their CDN. Now that “Roboto” is open source, one could in theory even load that font off your own server and bypass Google entirely. Or just use “web safe” fonts, to eliminate any external font loading.

For the above the fold render blocking blah blah. If your mobile score is above 85 you’re fine; if your desktop is above 90 you’re fine. But there is a notable “tuning” process to this, and again — it’s almost impossible to eliminate the “render blocking” or “above the fold stuff” entirely with *any* commercial theme.

Not sure any of that helps… just some feedback on my own suffering using commercial WordPress themes, and also building my own bootstrap 2 templates which are running our main business portal (using .shtml and custom page builder CMS; not WP).

You can’t cache things hosted on other people’s websites.
So none of those things you mention can be cached.

Welcome to stupid Google PageSpeed Insights 😉

(They penalize you for their own sites in the “rating,” but not in the real world.)

I personally “tune” my sites, with the ads disabled.

I don’t use child themes myself for two reasons (keeping in mind I’ve been building wordpress sites for 9 years now; both for our company and clients — and 20 years as of March 1, 2015 doing websites by hand):

1) it’s a CSS redirect; bad for Google, bad for pagespeed, and introduces some oddball gremlins with things loading from two places at once … seriously; have some weird gremlin? often it’s caching or child theme issue

2) often with many themes these days, the child theme gets updated along with the main theme for major security patches, feature updates; etc. (e.g., if you move to Newspaper ‘5’ next month, there will be new child theme — so, defeats the purpose of not editing the main files)

3) better to simply edit the main files and keep track of what you’re doing. This allows you to have fewer elements to keep track of overall and easier to back-up; easier to manage renaming folders for customization, etc.

Your mileage may vary, but that has been my experience. Especially if you use any kind of caching or systems like mod_pagespeed (as we do). Having a CSS redirect (where you’re essentially saying … load my CSS in one folder, but oh wait, NOW go load the real CSS from this other folder) — is NOT recommended by Google, but that is a basic precept of WordPress usage — started by WP, but not necessarily the best way to actually manage a site and content.

So, it’s up to you.

I don’t work here; it’s not my theme. I have been using Newspaper since Fall 2013; and this is just MY way of doing it. So, it’s only a “suggestion” on my part. Up to you. If you can live with some gremlins in how WP works, possibly pagespeed penalty from Google, and loading two sets of style sheet for the site every time the page is loaded … then enjoy. Nothing inherently wrong with it — but TIME magazine isn’t using a child theme when running WordPress; nor do I.

• This reply was modified 11 years by simchris.

Clearing cache worked for me when that happened.

Be sure to clear cache on your server and/or CDN also, *and* the web browser. With Chrome you have to clear history, with IE you obviously need to clear cache; FF sometimes cache doesn’t clear properly.

If using mod_pagespeed you have to turn it OFF to clear cached copies of CSS files.

You can also try editing your menu and resaving it to “reset” it.

Some suggestions
a) don’t use child theme, as it’s a redirect
b) ensure you have caching running on server like opcache, etc.
c) be sure to use normal WP optimizations (as per my own optimization sticky) — enough memory allocated to php, and upgrade default RAM for WP in wp-config.php -etc.
d) limit queries on post pages — meaning, avoid “most popular 7 days” kinds of things, try one query of “latest 5 stories” vs having three sidebar queries of 3 latest posts from 3 categories; try not using mega-menu to query dbase for story elements .. limit queries in footer
e) remove CSS over-rides in theme panel, move to style.css
f) consider using things like mod_pagespeed and or mod_SPDY if you serve all pages via https
g) turn off image thumbnail sizes you don’t actually use; plan layouts to limit total number of sizes for thumbs to no more than 5 or 3 if really going for speed
h) check server response time — which has nothing to do with theme and needs server to be optimized (our pages respond in 0.31 secs on avg., regardless of theme with only minor optimizations)

And of course look at some of the theme docs for suggestions from TagDiv on speed/performance.

Food for thought 🙂

• This reply was modified 11 years by simchris.

Issue is not with theme — all themes using Visual Composer as a “drag and drop page builder” are having this issue. And this only impacts some servers. We’re using NewsMag on two high traffic sites right now; one which gets a lot of traffic every day, the other gets large hits “depending on the content.”

Not sure what “SmartMag” is as this is the “NewsMag” forum, but if you read my thread then you don’t need to worry …

a) use the theme with current Visual Composer; might not impact your site/CPU depending on how your server is setup.

b) if you have a large CPU hit you will know immediately, and you can switch to using the SHIM plugin.

c) if you have a VERY high volume traffic website (e.g., millions of page views per day) you should be building a “lean framework” which doesn’t have all the pre-built options baked in, as this is not as efficient as a lean framework where you have as little as possible — e.g., TIME magazine is running on a version of twenty-fifteen theme with some custom plugins to manage editorial matters. No page builder, but lots of stuff running via cloud for fast “edge loading” via the Automattic premium platform. In that situation you would be custom building a theme to fit your needs not buying a $50 off the shelf product.

d) in our case we chose the TagDiv folk to redo our news network sites because 16 months ago when looking around they were one of the VERY few who had some clue about pagespeed optimization beyond so-called “SEO READY” … meaning, some thought given to page speed and not just “feature bloat” with some meta tags built in. We had built our own lean framework which was a pain pre-bootstrap, in 2011; went to Woo Canvas in 2012; went to TagDiv end of 2013 (has it been that long?).

But like all CMS platforms where you have a platform running on top of php, then theme(s) running on top of that, then plugins and hooks going into that, there is always a dev/test process on your end to see what works, what needs to be massaged, and what won’t work at all in your particular environment.

If you’re starting a NEW news site, I don’t think you need to worry about high traffic at this stage, as it takes awhile to build that unless you’re using bots or entirely click-bait with paid adwords per story to drive that.

————–
so, if you reads my thread you know
a) they have a fix NOW that works for those with high CPU issues
b) not all users of Visual Composer have an issue
c) the folks who make VC (not TagDiv) may optimize or fix memory issues in future version; TagDiv has NO control over that beyond working with the WP Bakery developers on the issue.
d) they may “roll their own” sideways version of a page builder which is more ‘lean’ at some point, but obviously that takes a bit of time to develop.

So, have fun and build your site 🙂