Also make sure you are not blocking that stuff with robots.txt — which it seems a lot of people have been doing incorrectly. You can’t block the main elements loaded by your web pages from google or the page won’t load all the elements.

I think shortcodes may only work with certain types of content boxes — I think it will only work in either a pure content box (like a post box), or into a widget area; it was so long ago I don’t recall .. sorry … likely best to wait for somebody else to chime in who has done it recently… (doh).

Use the Chrome web browser, hit F12 for console view to see just WHAT is not loading securely on your website. Remember if you have direct URLs to stuff like logos, those need to be secure URLs in the theme panel, also.

You do have one console error, btw
The resource https://pagead2.googlesyndication.com/pagead/js/r20180618/r20180604/show_ads_impl.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate <code>as value and it is preloaded intentionally.

main errors are also clearly noted:
https://search.google.com/test/mobile-friendly?id=4LuGR3wMtBMNR1YOeduvYw

Fix the following 2 issues

Clickable elements too close together

Content wider than screen

So, you need to make sure your ads and logos are responsive; you need to use responsive ad units to be mobile friendly. The reason elements are not rendered properly is you are blocking your style.css and other elements via robots.txt which is really bad!

You also had 15 page items that could not be loaded:
https://search.google.com/test/mobile-friendly?view=fetch-info&id=4LuGR3wMtBMNR1YOeduvYw

Note the *blocked by robots.txt* — only you can fix that. You should never block Google from accessing elements loaded on the page.

e.g.,

	https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js	Script	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/plugins/jetpack/css/jetpack.css?ver=6.2.1	Stylesheet	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/plugins/jetpack/modules/widgets/social-icons/social-icons.css?ver=20170506	Stylesheet	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/plugins/js_composer/assets/css/js_composer.min.css?ver=5.4.5	Stylesheet	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/plugins/td-multi-purpose/style.css?ver=4.9.6	Stylesheet	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/plugins/ytsubscribe/ytSubscribe.js?ver=2016.10.2.3	Script	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/themes/Newspaper/mobile/js/tagdiv_theme.min.js?ver=8.7.2	Script	Googlebot blocked by robots.txt
	https://www.tricksbykabir.com/wp-content/themes/Newspaper/mobile/style.css?ver=8.7.2	Stylesheet	Googlebot blocked by robots.txt

It’s important when using testing tools to read the “why” and “solutions” noted on the checker, as in my pasted in stuff above.

Hope that helps!

(I don’t work here.)

• This reply was modified 8 years by simchris.

I think the way we did that on couple sites was using an RSS feed widget in custom sidebar, then placed that custom sidebar into a layout as a “widgetized sidebar” … if that makes sense. Some widgets have shortcodes, so there may be a content block that allows for shortcodes to render.

Whatsapp is a mobile first app and requires the actual whatsapp installed on mobile device to work, which is why its hidden on desktop.

Tagdiv might have a hack to change that for you, but that is why you dont see whatsapp option on any major site when viewing on desktop.

Basically, when you change themes, or do a major update to WP and to caching plugins, etc., Google might be loading your sitemap or following a link, or your sitemap might actually stop working due to plugin, etc., and briefly Google is following links to whatever it can load via the regex/rewrite rules from WP in the htaccess file, and this can cause Google to try to load the /site/wp-content/themes/theme/index.php file which it should really never do. I’ve poked the WP folks numerous times the past decade to consider changing that to default.php vs index.php as it’s NOT actually an index for that directory, and should never be loaded by anybody.

Technically, one solution — for those who have the time and patience — is to go into the folder, and rename the index.php file as a copy to all the missing ‘default’ templates that WP would normally fall back on, so that WP has no need for ever using that file; then inside the index.php file put a redirect to http://yoursite.ooo — or simply remove the file entirely.

Also keep in mind getting a server error for that URL is actually correct — it’s an internal file and should never be loaded anyway; so Google is just letting you know that it temporarily got directed there during a crawl of your sitemap while the system was updating and it couldn’t go anyplace else and generated an error.

If you get one of these errors once in a while, no biggie; mark fixed and get on with your life. If you are getting them daily, you have a serious issue with your permalinks and configuration. If you see the errors in your domain/hosting error log, it may be people trying to hack the site and you can block those IPs from ever visiting your site again.

Upshot – nobody should be trying to access files directly in that folder, nor should Google, so a 500 error is just that; it’s just like getting a 404 error when you remove a page — it doesn’t hurt anything, or ruin your rankings, or anything else. That page is not part of your site, and not part of your navigation or site links or content.

It’s really a minor flaw in WP using ‘index.php’ for something that should be ‘default.php’ as default template when no other template exists. If there were no index.php file there, you’d get a 404 instead.

Not sure that helps; but I’ve posted about this topic several times the past 4+ years on here (I don’t work here, just a webdev dinosaur). 🙂

Have you tested your site in Google’s mobile friendly tester? Optimized your site for speed, not just mobile compatibility, and resubmitted your sitemap to Google to have them load the mobile friendly versions into SERPS?

If you’re using visual composer, you need to have the plugin running, or replace the tags if no longer using VC, I believe.

(I don’t work here; I just had a bunch of that when moving from VC to the TagDiv Composer.)_

Make sure you are viewing on mobile, as whatsapp doesnt show on desktop view intentionally…

Obvious, i know but some folks forget that.

I dont work here, just some feedback.

Well, memory limit and other php limits set by server are done from hosting panel. WordPress has its own limit which defaults to 40mb which is fine for default theme and blog, but not big page builders, sliders, etc., so only a web admin can edit the config file.. many other useful wp settings you can do in there too.

Learn to export your wp database from wp panel, backup php dbase via your hosting panel, and backup entire site via ftp.

See my security guide from Simions post above.

Check the changelog when new theme version announced to see if its a security fix or just feature updates.

You need to update your wp-config.php file to specify the new memory size also! See the wordpress.org docs on how to edit your config file for the custom setting. No other way to change that.

Whew! That was lucky. That’s good basic WordPress knowledge a lot of folks forget; as that sort of thing not managed by the theme in any way.

But yes! If still in the trash and not deleted, that is how to get them back.

Over here, I run the WP-Optimizer after doing a lot of updates, but that also empties the trash, which is why that didn’t even occur to me to suggest. (doh)

I usually go and work through the previews (I do it on my iPad, actually), and kind of pick some font combos I like; then I got try those in the theme to see how they look “everywhere….” quick way to at least determine which ones *not* to preview 🙂

I’ve moved to only using the web safe font stack, as all modern browsers have builtin fonts so that you don’t have to load any fonts at all from site or CDN, and look good everywhere, and no load time at all.

Nope. You can recreate them if you have them saved in archive.org. I had to do that once. Good way to learn a lesson to save a backup from the WP panel before doing major updates to site. And periodically, out of paranoia….

most often it’s the out of sync caching of the “lazy load animation” … just disable that from the theme panel.

(I don’t work here.)

There are some great tools online to preview fonts, easily enough:

Google has an entire site where you can preview fonts, and font combinations very easily.

Same with “web safe” groups, aka “font stacks.”

SEE:
https://fonts.google.com/

and
https://www.cssfontstack.com/

Welcome to web dev!

(I don’t work here, just annoying webdinosaur ! )

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

Hi. .. sorry …
got major sidetrack due to being diagnosed with type II diabetes in 2014; then spent 2 years getting that under control, and 2 years “curing” it — I am now cured and drug free as of Jan 1, but I was moving a bit slowly on all fronts due to taking drugs several times a day, losing 50 lbs, hour of cardio every day, blah blah ….

Finally got around to moving our web server to HTTP/2 on May 12, 2018 (that’s how far behind I was on THAT…) …

Right now, I’ve been working through the different strategies for optimizing website based on:

A) HTTP/2
B) mod_pagespeed “on” – but tuned for bandwidth by default, then turning on select elements; optimizing config to load images via /server/path/ vs http in order to auto-generate webp format images for mobile; necessary for removing comments dynamically including stuff like TagDiv still putting in the theme version in the comments readable by bots which is invitation for hacking for edge issues with XSS and whatnot (BAD!).
C) changing approach to above the fold, due to the way HTTP/2 works; testing whether or not “front loading critical CSS” inline is needed or not; so far, using Lighthouse in Chrome, it seems to matter after all…
D) big trick is optimizing CSS to remove “unused” CSS entirely; using an online tool to scan pages, then basically generate a CSS file that is 40% smaller prior to anything else; Google’s Lighthouse now counsels on this issue, quite nicely — problem with *all* themes out there, sadly.

Since I have my own server, my optimizations are based on running number of daily updated news portals; and trying not to use external CDN and trying not to use static caching beyond opcache for PHP 7.2x and HTTP/2 et al.

Since this subject has been changing so quickly the past couple of years, the whole book thing became a bit pointless as the landscape keeps shifting.

So, again – I kind of moved over to seeing how far we could go with
– https
– php 7.2x with opcache on
– no cdn, or caching plugin in WP
– mod_pagespeed for dynamic optimizations; static /paths/to/images/
– optimized CSS and JS files
– HTTP/2 for nextgen page delivery
– yes/no above the fold critical CSS testing (still in progress!)
– yes/no placement of css/scripts header or footer (still testing!)
– yes/no on combining css and js into single files or not

disable the ‘lazy load’ animation

relative to what? Store, business site?

Depends on whether you want everything together, or setup a separate entity. Neither is truly better nor worse. you could certainly put a blog about the trucking industry at blog.yoursite.000 and your main corp site at yoursite.000 — if, say you were writing about general topics not related to your specific company offerings and didn’t want to pollute your main company data.

Only other benefit SEO wise is similar URLs … e.g.,

company-site.000/trucking-services/
company-site.000/choosing-a-trucking-service/

you would want those to rank higher related to your business than

company-site.000/blog/choosing-a-trucking-service/

so, in instances like that it would work better to have

blog.company-site.000/blog-choosing-a-trucking-service-in-2018/

some great tutorials in the docs section > tutorials, and also the diy/best of forums sub section

Sadly, that’s how AMP works. The browser, referrer, and source origination usually determine if AMP version loaded. Meaning, if somebody comes from FB or SERPS and the link itself is not an AMP link, the normal page is loaded, as expected. If on mobile connection, and browser and Google have identified as AMP compatible using AMP enabled browser, then the AMP page loads, or if followed from AMP enabled link in SERPS.

If you forced all traffic to AMP, defeats purpose of having non-AMP pages, and you might as well just setup a REGEX in your system to redirect all traffic to /amp/ endpoint, but outside scope of the theme.

I don’t work here. But been using AMP since it was in beta in 2015.

I’m assuming you read up on Google copious notes on what AMP is for, when and when it doesn’t work, how to serve, etc. ?

WHAT THE HELL IS AMP: https://www.ampproject.org/

(( sorry if that didn’t help … ))

Usually best to turn off the lazy load thing as I found when running opcache with PHP 7 that it sometimes had empty spaces as the “document loaded” never fully got parsed in some browsers, so you’d get blank spots. It’s really on animation anyway.

So, make sure ‘with opcache on’ is running for PHP 7, and turn OFF the ‘lazy load effect’ in theme panel. Fixes it.

🙂

(I don’t work here just webdev dinosaur and TagDiv lurker since 2013)

and of course, my ‘classic’ thread here good read:
https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/