Clear your cache, resave permalinks, clear transients with wp-optimize.
Heh. Im usally a pest from time to time here as i adopted tagdiv themes back in 2013 when i was rebuilding one of our in house themes, usimg bootstrap, and just decided had to be something out there to do what i wanted, and how i ended up here after buying theme.
I also ran a hosting company for 10 years. Built my first web site march 1995, and started using wordpress for some things in 2004. While i still prefer shtml, ive started moving just about everything to wordpress. But man the hoops ive gone through.
Anyway, glad you got a handle on it!
Heh. Been there. ?
Glad you got it sorted!
-
This reply was modified 9 years by
simchris.
Sadly i dont use the mobile theme so cant really help with that.
Um, if you block wp* in robots.txt then everything in wp-content – including themes css, images, etc. won’t load properly, hence why the “preview” in the Google mobile speed tester shows broken layout.
Even YOAST says not to do this, as it breaks how Google views your pages – as in this case.
https://yoast.com/wordpress-robots-txt-example/
Simply remove the blocks from robots.txt — which you don’t need to do as anybody can still go there — they don’t actually stop anybody from doing anything, from a security point of view.
Google needs to load the “dependencies” for WordPress in order to load the pages — so if it cannot load the mobile CSS, then it can’t actually load the mobile version properly hence the errors.
Have you tried “fetch as Google” in your webmaster tools account to see EXACTLY what Google sees when scanning your page?
e.g.,
https://support.google.com/webmasters/answer/6066468?hl=en
anyway — I’m out on this topic, but hopefully my ramblings have provided some pointers on where to look. 🙂
I would seriously try removing the stuff in your robots.txt file and retry.
-
This reply was modified 9 years by
simchris.
(sigh)
see the docs and the “how to update” sticky post top of the forum index.
You only get the new version of the plugin when the THEME is updated, as it’a a “bundled” version and has to be tested to ensure it doesn’t break things.
So, no reason to get the latest version just because it’s the latest version, unless there is a major security fix.
Upshot – don’t panic! 🙂
I’ve never seen ? added to a filename as that would not even work on a web server properly. That may be loaded as part of the URL to the image to indicate the size being loaded, but not part of file name.
Also good habit to start naming your images based on size … like
image1-600x450.jpg
image-about-puppies-640x480.jpg
090916-joe-announce-500x275.jpg
etc.
You might look at your actual files upload folder on your domain to see what the files are actually called, via FTP or your hosting account file manager.
I doubt ?=600 is being added to file names. Not happening on my sites running Newsmag.
If you are using some external plugin to auto-optimize images (photon, smush-it pro, etc) that would be an issue with that plugin and not the theme, btw.
(( I don’t work here … ))
You don’t need license code. Ignore the ‘nag’ screen box from Visual Composer.
https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
Application: WordPress 4.5.4
WordPress versions 4.6 and earlier are affected by two security issues: a cross-site scripting vulnerability via image filename, reported by SumOfPwn researcher Cengiz Han Sahin; and a path traversal vulnerability in the upgrade package uploader, reported by Dominik Schilling from the WordPress security team.
Check your site with Securi malware scanner — note if you have not updated your site with latest versions of WordPress, your site is at risk of security flaws in WP, not the theme.
https://www.google.com/transparencyreport/safebrowsing/diagnostic/
ISSUE DETECTED DEFINITION INFECTED URL
Website Malware malware-entry-mwjs6525?web.js.spam-seo.redirect.021 http://alacatiplus.com/ ( View Payload )
Website Malware malware-entry-mwjs6525?web.js.spam-seo.redirect.021 http://alacatiplus.com/haberler/ ( View Payload )
Website Malware malware-entry-mwjs6525?web.js.spam-seo.redirect.021 http://alacatiplus.com/yeme-icme/ ( View Payload )
Website Malware malware-entry-mwjs6525?web.js.spam-seo.redirect.021 http://alacatiplus.com/eglence/ ( View Payload )
Website Malware malware-entry-mwjs6525?web.js.spam-seo.redirect.021 http://alacatiplus.com/alisveris/ ( View Payload )
Website Malware malware-entry-mwjs6525?web.js.spam-seo.redirect.021 http://alacatiplus.com/konaklama/ ( View Payload )
Wow, we so need a plugin for that!!
( oh, and you do want caching/TTL running for your site, so that the directives to cache stuff work using the server’s opcache/memcache; but do all the optimizations without using any caching plugins, in order to see changes, make changes, etc. — what these do is tell the browser not to keep re-loading things like your logo every time the page loads, or the style sheet, etc., and if they come back tomorrow, page loads quicker as the ‘time to live’ is longer than 24 hours or whatever — this speeds up pages, separate from the gzip/deflate stuff … )
Put another way:
server caching helps the server serve up re-used files quickly without reloading the single files over and over and over.
Caching plugins create a “static” copy of your page for short period of time, so that the whole page can be downloaded as a much quicker element as there are not dbase queries waiting on php processes for 20 things on the page.
Not sure that helps, just anecdotal.
You’re very welcome 🙂
I accept gingerbread cookies in my virtual tip jar!
I accept gingerbread cookies as tips 🙂
Also note with mod_pagespeed, generally there needs to be a custom line added to the pagespeed.conf file pointing to your static folder, such as /site/wp-content/uploads/ or where your images are, to let mod_pagespeed load https static files via /server/path/ vs via http/https.
If your host isn’t running mod_pagespeed, that is non issue.
Based on your page source it does not appear mod_pagespeed is installed or running for your content.
REF:
https://developers.google.com/speed/pagespeed/module/configuration
Gzip/Deflate must be properly setup and enabled at the SERVER level; above the domains, above your website; not from htaccess, theme, or WordPress. Two different things. From my test it looks like it is partially setup, but some setting you have is not compressing javascript and css files, it would appear.
a) gzip/deflate must be ON and working; then the directives tell it what to do.
b) for mod_pagspeed — that won’t work unless your host is running mod_pagespeed — and if they don’t have gzip/deflate properly setup it’s highly doubtful that mod_pagespeed is running.
As noted in various places in my long long long thread; you need to go research what some of my things DO to see if they apply to your server setup, otherwise they won’t do anything.
So, again – YOU need to contact your HOST provider, and
a) have them properly setup gzip/deflate — as right now it’s not compressing ALL your content, only some if it, which is not normal.
Your page does show this:
Results
Url : https://tomatoheart.com/aishwarya/10-p-v-sindhu-first-indian-woman-win-olympic-silver/
Parameter Value
Gzip/Deflated enabled ? YES - The url is serving compressed content.
Compressed Size 41.45 KB
Original Size 327.66 KB
Savings 87.35 %
Response header
Content-Encoding: gzip
But as it clearly shows on GTmetrix; and you should provide this to your host –as I stated — to get them to fix, along with the vary accept encoding:
Enable compression for the following resources to reduce their transfer size by 401.2KiB (80% reduction).
Compressing https://tomatoheart.com/wp-content/themes/Newspaper/js/tagdiv_theme.js could save 391.9KiB (80% reduction).
Compressing https://tomatoheart.com/wp-content/plugins/ytsubscribe/ytSubscribe.js could save 4.0KiB (69% reduction).
Compressing https://tomatoheart.com/wp-content/plugins/wp-facebook-login/public/js/facebook-login.js could save 2.3KiB (66% reduction).
Compressing https://tomatoheart.com/wp-content/plugins/akismet/_inc/form.js could save 382B (54% reduction).
That is what is hurting your site speed/rating.
So, that’s about all the help I can provide there
In our setup, we have the server setup to serve gzip/deflate and vary accept encoding without having to add the <IfModule mod_deflate.c> section you have in your file.
Sorry not a better answer 🙂
I think you can disable this in theme panel.
Probably good idea to do what I just did this past weekend after upgrading from 1.71 to 3.1 — just go through EVERY screen in the theme panel to see where everything is, and get a sense of what options are there to turn stuff on/off; that’s how I knew about the sidebars thing for categories. Was just there 🙂
(( I don’t work here; but sometimes I should get some cookies or something… ))
I think you can specify a custom sidebar for each category on the categories section in the theme panel.
FYI — and I know you don’t care about my opinion — With one of my sites, running latest Newsmag – no caching plugin, no CDN — it passes mobile friendly, just like all our sites running TagDiv theme:
https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fcalifornianewswire.com%2Fsambrailo-packaging-launches-certified-organic-fruits-and-vegetables-packaging-for-ccof-certified-growers%2F
I suspect your robots.txt file is messing up your site, regardless of theme.
Of course this *is* noted on the mobile friendly test page.
Even with the ENFOLD theme, and with the “mobile friendly” okay badge, you still have some notable problems.
How Googlebot sees this page
This page uses 28 resources which are blocked by robots.txt.
Looks like you might have a bad config in your robots.txt blocking things, which is why I see a broken layout with missing CSS/JS even with this theme in the preview image.
Issue with Facebook; check developer tools for post with that author for error.
Also, check to see if the author’s FB page is private or public.
And, make sure you check the LINK to the author page on FB that isn’t linking is actually there.
Note the link will not work when SHARING to FB, but then turns on AFTER the post is live and they then rewrite the “name” shown to match the FB version.
For example we shared something where on our site author was (made up example) Whacky Widgets Corp. and not linked to their FB page; then when actually posted to FB, the link was active, but name changed to Whacky Widget Inc. which was the actual name ON Facebook.
They seem to be messing with this lately, and I only noticed that behavior this week for Sept. 2016.
Welcome to the Internet! 🙂
Also, your host really should be serving up this one properly:
The following publicly cacheable, compressible resources should have a "Vary: Accept-Encoding" header:
I had to get this setup properly on our new server that went live Aug 5, also. SO, have your host fix that; and send them that section with the files — basically the css and js should be serving the “vary …” thing. And that is also part of the proper setup of the gzip/deflate.
Hey party people!
Remember that the gzip/deflate settings on both web server and in htaccess (remember that settings for my stuff is based on Apache servers; needs to be different for NGINX boxes, which are becoming more and more common) are good for 20 points or more alone. That is always first thing you need to address. This is what the server compresses before it sends something to the web browser. It’s mission critical, step one.
For example first item in your GTMetrix test:
Enable compression for the following resources to reduce their transfer size by 424.8KiB (79% reduction).
Also for image compression; re checking any image that can be compressed more than 2KB is good idea as it adds up on image heavy layouts;
eg.
Optimize the following images to reduce their size by 31.8KiB (5% reduction).
Generally you can kind of ignore stuff that says optimize by 322bytes as that is 1/3 of a kb. Unless you want to really go nuts on optimization score (I leave that stuff to last myself).
ALSO; to stop yourself from waking up in the middle of night screaming (oh wait, that’s me), test one of your post pages and not your home page; the home page will always initially have worst score due to so many images being loaded. An “average” post page, is best to tune with as that is 90% of your site traffic and what Google is focused on.
And as an anecdote; my original thread on the optimization was actually for the 2014/15 versions of Newspaper, then I switched to Newsmag when it first came out as it better fit my news portals which get updated daily.
Stuff for htaccess and functions.php are “generally” going to be same between the two themes.
So, I’d tackle the gzip/deflate thing first – as that is your biggest gotcha right now.
Theme supports the plugins, but you need to add them. The plugins are not made by tagdiv, so they cannot include them with the theme.
Perhaps i didnt understand your question.
You obtain the plugins at wordpress.org
***URGENT**** URGENT **** URGENT
You can try couple of things
a) clear your cache on site if using plugin, or reset CDN if used
b) clear your web browser cache/history fully to reload new CSS used in WP
c) resave permalinks
d) clear transients with wp-optimize plugin
e) go to your menus settings and just resave them
f) disable conflicting plugins (use F12 in console view to see if ‘errors’)
Good luck! Your menus load just fine for me.
(( I don’t work here ))