Search Results for 'optimize'

hi,

I am using auto optimize plugin for minifying javascript, html and css. I will remove it but please suggest me a plugin for the same purpose that have been tested with the site. Or if you have a manual code to accomplish this task do send it to me and I will copy paste it into my site.

Thanks

I tried deactivating of all plugins and used wp-optimize – the paths in question are still accessible and index-able. These urls are not included in the sitemap. I hape only post sitemaps, post-tag sitemap and category sitemap. In the meantime duplicated content issues in the search console are counting.

I don’t have a caching plugin but use memcache and litespeed on the server (it’s a shared hosting). However I don’t think this has something to do with the problem.

I see that many sites have a similar issue:
https://www.google.bg/?gfe_rd=cr&ei=Gl1zWer0LqGz8weAj5eQBg&gws_rd=ssl#q=/wp-content/uploads/revslider/templates/

Any help will be much appreciated!

clear cacbe.

clear transients with wp-optimize

resave permalinks

You need to set the minimum RAM for WP to 64M in your wp-config.php file.
Check the ‘settings’ checkup in theme panel for more info.

This is most common issue. Also possibly some bad plugins not updated (e.g., Yoast SEO had bugs breaking things; make sure updated, etc.).

Also try clearing transients with wp-optimize plugin.

AND: consider using the ‘limit logins’ plugin to stop hackers; *and* also consider disabling XMLRPC — as this can cause hackers to overload your server trying to post pingbacks or spam comments, etc.

All that stuff impacts ability for PHP to ‘work’ for your site — unrelated to the theme specifically.

Not sure any of that helps — but been suffering this stuff over here with WP for 12 years now, so kinda been hit by everything at one point or another.

🙂

Dunno. Try changing your category template settings?

Clear transients with WP-optimize — resave permalinks.

Then try disabling any plugin that adds stuff like cookie popups, or similar that might be interfering with page render.

Often it’s a typo in something added to theme panel.

Most of it should be, assuming you’re running Apache/Linux. Note that the nice formatting of my code got kind of whacked when they moved to the new forum template…. soo.. might not be super readible/legible.

Kind of multiple threads going in my old mega thread — so, perhaps useful to work ‘backwards’ ?

a) some basic wp-config cleanups (add direct paths, memory change, image compression)
aa) htaccess stuff for common time to live, file type, redirect xmlrpc queries, etc.
b) some basic functions.php stuff to clean needless stuff in header of WP pages, remove stuff like XMLRPC stuff, some security stuff; remove ‘?’ queries on stuff (versioning);
c) optimize style.css with minifcation; compress main .js file per Google tool
d) consider moving to web-safe font stack and not loading ANY google fonts; have to hack out section in the main them booster function file, then search/replace the ‘font-family’ elements in the style.css (easier prior to minification, obviously)
e) put custom CSS bottom of style.css vs theme panel

advanced stuff included – un-enqueueing the main style.css, loading in footer; after generating “critical CSS’ with the critical CSS generator online; putting above the fold CSS in header.php (only way to remove render blocking css) ** not needed if moving to http/2 platform.

Super advanced peeps might choose to use mod-pagespeed, https, php 7, and http/2.

So, basically.. kind of a “test your speed,” (with *no* ads running); then make some mods; then retest couple of times, etc., rinse repeat.

I’m no longer using Newspaper – moved to NewsMag 3x last year entirely. Not yet on 4x. But also using TagDiv’s WPION thing as a beta test. (actually re-rendering thumbs for one test of that right now in other browser tab!).

Soooooooo….. basic Apache stuff, and WP-config.php stuff, and common sense thing for functions.php that do specific things — all useful. Good to research WHAT things do before using them.

• This reply was modified 9 years by simchris.

Make sure you deleted old folder; then uploaded new folder; not merging old/new theme folders via over-write. Common issue of mixing old/new code in same theme folder.

If you are loading the *old* theme panel for Newspaper and not the current one, that is often the culprit, in my own experience.

If you did clean install of 8x vs “overwrite/merge” …

You can also try
a) clear all caching
b) clear transients with wp-optimize
c) resave permalinks

TD composer is not a 1:1 replacement for VC — it’s not the same thing and doesn’t have all the same features, but runs much faster and optimized for mobile etc., less overhead, more secure, etc.

Keep using VC if you like it. Switch to TDC if you want to optimize site, faster response, lower overhead, better security.

(I don’t work here.)

so, you’ve debugged by disabling all your plugins to see if those files are still there after doing so? To determine how they are being created?

cleared all transients with wp-optimize ? resaved permalinks ?

Anyway — can’t help any more than that. Good luck!

Hey Bogdan, I think it was caused by another caching plugin I was using – Autoptimize. Everything works perfectly now when i disabled it. Why didn’t I try it before, haha, geez. Thanks a lot and have a nice day!

Might have been the PHP cache or another caching thing in WordPress.

One of my other secret tricks is to clear transients by
a) use WP-Optimize plugin
b) resave permalinks

this both will clear stuck ‘transients’ which are micro-caching done by WordPress (like, oh, say you make change to your RSS, but the RSS not updating when you look at it- this is why).

But for us – seriously, going to PHP 5.6 from 5.4 solved a million little dumb weird things!

As it says, disable the image sizes you’re not using from the theme panel.

Also, consider using the built-in compression features of your web server, so that when WP adds items to the media system you have higher compression level than default; and perhaps optimize images in Photoshop prior to upload.

Not sure that helped, but it’s what we do here.