Search Results for 'pagespeed'

Usually this happens from both plugins adding some kind of code/hooks into the admin panel, which impact both. And possible loading conflicting jquery elements.

You may be able to fix by turning off the tagdiv speed booster — or adding the hooks for both plugins into the speed booster to add to the queue order for loading.

I have no issues with WooCommerce, but JetPack continues to be buggy and hit/miss unless using the most rudimentary WordPress themes, in my case. I have found I don’t use JetPack for anything, as there are better solutions for almost all of its tools, and they are terrible resource hog and load so much external crap it slows site down and hurts the PageSpeed score terribly. Just my opinion.

Not having any issues with the theme and mod_pagespeed running on Apache.

Obviously you should look at the rendered text and check for validation of closed CSS elements, which might be broken from a plugin or customization done.

Various tools can tell you if a bracket isn’t closed properly for some reason. Of course this might also show up in the audit function of Chrome’s developer tools, or check in Dreamweaver, etc.

Theme is not at fault for traffic changes. Google and Bing are constantly re-engineering how they show search results. If you use proper XML sitemap, and use white-hat SEO techniques, the site will do as well or better than another theme. PageSpeed, proper META data, original content, reduce use of content already on t he net, etc. all impact your placement in search. Your Google Webmaster tools account will also help with checking that.

However, robot traffic can go down if your internal links are setup differently; meaning if you have more/less links to related content, change your comment system, add any ad networks Google doesn’t like etc.

Only you can “solve your problem” with your own website.

Thanks for your response.

I think is not a slow connection, i have been testing in slow and faster connection and is all the same thing.

Im not using CDN / Caching plugin at this moment.

I was using Total Cache plugin before install this theme. I was looking in wp-config.php file and I deleted these lines:

/** Enable W3 Total Cache Edge Mode */
//define(‘WP_CACHE’, true); //Added by WP-Cache Manager
define(‘W3TC_EDGE_MODE’, true); // Added by W3 Total Cache

I disabled the speedbooster plugin and now the pages/post are loading fine: http://www.elversiculodeldia.com/ it is not showing me the links before showed. but pagespeed score now is lower.

Any suggestion?

You need to read the docs on how to optimize the site for pagespeed as you have numerous issues with the server setup, image optimization, etc. Please see the docs for the theme from the forum navigation bar on how to optimize your site for “speed.”

Yes, the instructions clearly say don’t use “minify” with W3 Total Cache with this theme, so that was a good choice 😉

Force gzip is not a good solution for simply having your hosting provider properly setup gzip/deflate for your hosting account. This is a normal “needed” option for all hosting. If they won’t do it, move to a better hosting company. Seriously.

You can minify the CSS pretty easily (I cover this in the PageSpeed sticky topic several times). It’s not hard to do with the main CSS file. Worth doing, frankly. Just keep backup. All it really does is remove all the extra spaces, line breaks, and un-necessary thing like ; before a } and stuff like that. But it can cut the “size” of the file by 25% or more in 5 minutes. Super easy to do once you do it.

Compression is managed on your server; and hard to believe you would have 92 with that turned off, as that is typically good for 20 points alone, unless your prior theme was all text.

Browser caching is also necessary for all high ratings on PageSpeed Insights.

If you properly set both of those up, your speed should improve by 30 points. No site will rate well with those two elements disabled. Period.

Quick help on both expiration headers for browser caching and also gzip/deflate which should be working on your server to get any decent pagespeed score.
https://forum.tagdiv.com/how-to-make-the-site-faster/

• This reply was modified 11 years by simchris.

on GTMetrix.com show me Page Speed Grade:(75%), but i am using PageSpeed Insights like on documentation, and there is speed 25, which is should look??

@Danijelmo
You don’t need to post the same thing over and over.

Try testing your site with GTMetrix.com as it will tell you specifically what your site problems are and classify them by things like “Server” “Images” etc., with explanations.

Did you setup gzip/deflate on your server? [looks like you did!]

Did you edit your htaccess file (if applicable) to add expiration headers (e.g., mod_expires settings)?

Did you install an optimization plugin for images/thumbnails or change the default setting in your functions.php file?

Are you using the tagdiv speed booster plugin?

Did you disable system hogs like jetpack? Disable all plugins you’re NOT using?

Are you using a caching plugin once all of the above is working?

————

based on this you have some issues:
http://gtmetrix.com/reports/crnjaci.com/fxrIs409

1) you’re loading images off wp.com instead of your own locale; using a CDN for un-optimized images doesn’t make them load any better
2) you need to add instruction to the functions.php file to remove query strings (see my help on that in the pagespeed sticky topic)
3) you have some ridiculously huge images….
•http://i2.wp.com/crnjaci.com/wp-content/uploads/2014/08/IMG_0380.jpg?fit=1024%2C1024 is resized in HTML or CSS from 768×1024 to 291×388. Serving a scaled image could save 253.5KiB (85% reduction).
•http://i0.wp.com/crnjaci.com/wp-content/uploads/2014/08/10250323_10152304836090758_9213683227347813057_n.jpg?fit=1024%2C1024 is resized in HTML or CSS from 1024×768 to 291×219. Serving a scaled image could save 245.6KiB (91% reduction).
•http://i1.wp.com/crnjaci.com/wp-content/uploads/2014/08/DSC03988.jpg?fit=1024%2C1024 is resized in HTML or CSS from 1024×768 to 291×219. Serving a scaled image could save 241.2KiB (91% reduction).
•http://i1.wp.com/crnjaci.com/wp-content/uploads/2014/08/IMG_0594.jpg?fit=1024%2C1024 is resized in HTML or CSS from 768×975 to 291×370. Serving a scaled image could save 238.1KiB (85% reduction).
•http://i2.wp.com/crnjaci.com/wp-content/uploads/2014/08/IMG_0213.jpg?fit=1024%2C1024 is resized in HTML or CSS from 1024×683 to 300×200. Serving a scaled image could save 228.1KiB (91% reduction).
•http://i1.wp.com/crnjaci.com/wp-content/uploads/2014/08/10568980_10150651663339953_7674800880872619968_n.jpg?fit=1024%2C1024 is resized in HTML or CSS from 960×720 to 291×219. Serving a scaled image could save 199.1KiB (90% reduction).

Looks like you need to seriously look at your image optimization problems as your images look to be way too big when actually served on the pages.

Wny would you have a 250kb+ image file? A 1024×768 image if properly optimized should be no more than maybe 75kb.

BTW: optimizing your server/site for PageSpeed is YOUR job, not the theme’s job. Good to learn how to do this by reading up on the topic on Google as well as the docs provided with the theme as a courtesy.

Try this:
1) make backup of your site files, as per usual good practices; use tools to export your database from WP panel. Backup images.

Clear cache.

2) make sure you’re running latest version of WordPress (4.1); v 3.9x has cross-site scripting vulnerability; v4.0 has bugs, fixed in 4.1.

3) switch to default theme (e.g., twenty-twelve); do this before disabling visual composer!!!!!

Clear cache again, as applicable.

4) disable ALL plugins

5) DELETE the original theme folder, delete the original plugins for theme (TD speed booster, TD social, Visual Composer)

Then follow my posts on best way to install theme:

================================================
Make sure you upload only the main theme files; don’t install the “all files” zip from ThemeForest… that has docs, psd files, plugins, etc.

You want to install the smaller of the two files on Themeforest, if you’re installing via theme panel with .zip.

BEST WAY TO INSTALL WP THEMES:
Ideal way is still to
1) unzip theme folder “Newsmag” on your HD
2) upload via FTP/SFTP to your /wp-content/themes/ folder
3) upload the plugins unzipped to /wp-content/plugins/
4) switch to default theme from your old theme [should already be done for migration]
5) turn off *all* running plugins [should already be done for migration]
6) clear your cache(s), turn off caching (!),
7) activate the Visual Composer plugin
8) activate the new Newsmag theme
9) launch the theme panel
10) reactivate only the plugins you 100% need to make sure they work (some plugins WILL NOT WORK properly with WP 4.01 until you update the plugins!).

Clear the cache in your WEB BROWSER FULLY and restart web browser; this clears any CSS/Java used by your previous theme admin, and theme, so that you see the new CSS/JS properly (seriously, this is cause for huge number of “my new theme doesn’t load right” or “admin panel doesn’t have any boxes!” errors).

If you’re running WordPress older than 4.0 be aware there is a very serious cross-site scripting vulnerability (e.g., WP 3.9.2). You should be running WP 4.0+ to use this theme properly.

This is standard practice for switching to a brand new theme and good habit to get into doing it this way to ensure you clear cobwebs on old, and cleanly move to new.

Hope that helps! 🙂

Chris

==========
ADVANCED USERS:
if you or somebody else optimized your site for better PageSpeed score and increase dbase efficiency, by editing the wop-config.php file to add absolute paths to the theme folder, you will need to remove that line prior to doing any theme switch. Some people forget this step and immediately get a server error trying to change themes in the WP admin panel. You should be making backups of your wp-config.php folder periodically anyway and never hurts to open it and view from time to time.

• This reply was modified 11 years by simchris.

You may want to read up on how to use WordPress from the WordPress Codex; you *can* simply rename the theme folder and CSS name for the theme; which is how it’s done for web development, such as for a client, or better security (we do that here, changing theme name to sitename). If you’re comfortable editing the functions.php file, then changing the theme name is done simply by editing the style.css file which is where WP picks up the theme “name.”

Note it won’t change the theme style classes so somebody can very easily “figure out” which theme you’re actually using, if not the version.

Are you removing all the versioning from your site using the commonly available code to put at bottom of functions.php? That is also recommended to hide versions of WP, and also visual composer (see my separate post on how to also hide that code).

TO THE POINT (sorry!):
You can remove that “theme credit” code from functions.php without anything breaking, but be aware it makes it harder if you ask for tech support in the future if the admin here can’t figure out which version of theme you’re using when looking at your page source to debug any of your possible problems with CSS, customizations or running plugins, etc. If you’re comfortable in remembering to always “state” which version you’re using (and keep track of that somewhere), when needing support, you should be fine. 🙂

We actually use mod_pagespeed which just removes *all* commenting for faster page loading, which is recommended if your hosting provider offers that.

You can also further optimize the install by placing the explicit paths to the new name theme folder in your functions.php folder once you’re “set in stone” (obviously if you switch to another theme from admin, it may break) and also the site name URL, but that’s a bit advanced. Research the WP Codex on how to do many things like this (some of that is in my long winded comments in the Newspaper forum under the “Pagespeed” sticky topic).

Hope that helped, versus annoyed 🙂

We do use mod_pagespeed, thanks to both. 😀

Note the “remove_action” section is always useful… note it refers to “visual composer” and “meta data” … this removes the comment printed in the rendered page where it shows “created with visual composer 4.3” or whatever. Annoying.

So, basically that code I posted has (3) sections
1) remove general versioning from normal version strings; might not work on all the tagdiv speedbooster enqued stuff
2) change default thumbnail compression level (default in WP is 90, which is for quality, not speed or best practices, which is the WP mindset — better vs fast …. where 70 would be better default, frankly). 50 works. I think we ended up with 60 on some sites for some odd reason (I think ’60’ worked better with mod_pagespeed on our server for WebP conversion or something). Anything is better than 90!
3) hide the visual composer comment string.

You can actually find all my various pagespeed rantings from the past year on the Newspaper forum in the pagespeed sticky post if you want the whole shebang of stuff I do. Luckily TagDiv put a bunch of that into the standard theme docs now, and they already knew most of that from optimizing the demo sites anyway.

If you want an extra little boost you can also locally host gravatars and also optimize your wp-config file; see the Newspaper forum sticky topic, and simply start at end and work backwards to see all my special tweeks, if curious. I think later in the hundreds of posts I would often “resummarize” things, as well as add tweaks for the gravatars, and such. No point in repeating all of that here again. 🙂

• This reply was modified 11 years by simchris.

That’s what I thought. I don’t think slider is able to do “double loading” — meaning it’s doing ajax or whatever to load each “slide” as an image, but cannot also do “media query check” as each slide loads, as that would mean reloading the slide every time to check for viewport. Horribly complicated and almost means having to do a viewport check, THEN load “desktop slider” vs “mobile slider” with two different setups; meaning loading both large and small images like is done with logo. Problem there, however, is what size would somebody load for mobile since the viewports vary, and traditionally loading larger image and “scaling” it was fine since you’d get benefit of more pixels for retina without having to actually load a denser image.

In our case to this issue, the solution was running mod_pagespeed on the server as this optimizes and caches the most common “rendered size” — so if 80% of your audience was coming in on iPhone, viewing in portrait, and the 1073 image was loading as 573, then mod_pagspeed would make an optimized 573 size image and cache it; which would speed things up AND help with the “resize image” technical “problem” with mobile.

I cannot stress any more highly the benefit of mod_pagespeed for this kind of issue; and the fact it can generate optimized images for Chrome and other WebP image capable platforms (WebP more efficient than jpg).

If you can use a web hosting company using mod_pagespeed you will be amazed. Of course some CDN providers are now offering this, too, if your hosting provider doesn’t yet do so.

Yes. But if you dont have the smaller sizes, then the larger sizes are loaded. Reread the pagespeed page to see the actual problem.

Size is the problem…. Dimensions.

A.. You should not have images that need 100kb size reduction.

B. You should not ideally be loading the 1000 pixel wide images on iphone.

Try testing with gtmetrix as another option for better explanations of problem.

• This reply was modified 11 years by simchris.

Not sure this is the answer, but check to see if the optimized sizes are actually being created; possibly add those sizes as the default sizes under WP > media settings so they are made in addition to the theme sizes. Problem with “mobile” images is they are responsive but no specific phone uses the same “sizes” for the viewport “width” so technically I suppose images will always end up being resized larger or smaller.

Google mod_pagespeed helps with this issue if your server/hosting company offers that.

But try the media sizes being served added to your media settings, regen thumbnails, then retry. Not sure that will solve it, but worth a try.

I admit I have not yet tested my install of Newsmag for page speed as still messing with the home page and logos today 🙂

Okay… as promised, here is some help for this based on what I’ve done in past for Newspaper, translated for what works with this theme. It may be that the italics are not loading properly due to the enqueue method; dunno. I posted this in your other thread, but will also post here for completeness.

(admin – correct me if wrong on any of this !)

Note that in the td_fonts.php file it does appear italic is specified to be loaded from line 889 (this whole block was found in functions.php in Newspaper theme for those who are moving over).

e.g.,

wp_enqueue_style('google-font-rest', td_global::$http_or_https . '://fonts.googleapis.com/css?family=PT+Sans:400,700,400italic|Ubuntu:400,400italic|Open+Sans:400italic,400|Oswald:400,700|Roboto+Condensed:400italic,700italic,400,700'); //used on menus/small text

That “should” be loading the “normal” body font (400 weight) in both normal and true italic (vs oblique/slanted non-italic font).

Check your page source for a post to see if that is actually there.

Similarly at line 902 this is found; presumably this would be enabled and enqueued if selected from the theme fonts selectors:
if(!in_array('g_438', $td_user_fonts_list)) {//'g_438', //Open Sans
wp_enqueue_style('google-font-opensans', td_global::$http_or_https . '://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700&subset=latin,cyrillic-ext,greek-ext,greek,vietnamese,latin-ext,cyrillic'); //used on menus/small text

This has the light, normal, semi-bold, and bold weights, however does not have the italics, which I am not sure appends or replaces the main element at line 889.

Likely if one were so inclined they would edit the line 889 to add all the weights desired for Open Sans, remove the fonts and languages not being used, following the schema spit out from the Google Fonts website font builder:
http://www.google.com/fonts#UsePlace:use/Collection:Open+Sans

e.g., Open+Sans:300italic,400italic,600italic,700italic,400,300,600,700

so, you could edit this code like so:
wp_enqueue_style('google-font-rest', td_global::$http_or_https . '://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,400,300,600,700'); //used on menus/small text

For expert users, one might actually remove that block from the td_fonts.php file entirely, edit the style.css to search/replace all fonts to Open Sans, then grab the CSS from Google’s server by loading the above URL in a browser, and putting all the styles at bottom of the style.css sheet (I actually did this for Newspaper on one site, for better PageSpeed Insights score).

I only provide these examples as possible solutions and they may not apply to you. Hope that helps somebody on this topic.