I would worry more about the issues with your CDN setup, and redirects, etc.

Note that all those external “requests” refer to all the ad networks, pulls from CDN, pulls from local, pulls from FB, etc.

Only way to cut down on loading things is to use less things!

From the looks of it you need to “tune” your CDN stuff a bit for expiration headers, etc., which should help cut down on some things.

It’s like a train … the more cars you put on the end the longer it takes to get up to speed. You are pulling a lot of external train cars!.

Just for comparison, one of my example (BETA) pages using Newsmag, not yet fully optimized, no CDN:
http://gtmetrix.com/reports/musewire.com/KSBqjNGw

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

You can customize/modify the theme buttons by editing the core theme file that manages the CSS and image/font for each button. You can also over-ride any CSS with custom CSS.

Apparently the 3x version of plugin does not work well with WP 4.1 …
you may be able to get the older version 2x which reportedly *does* work with WP 4.1x from the plugin developer.

Did you try it with the default wordpress theme ?

Upload the theme files from the zip archive via ftp; or if installing zip file use only the theme file, not the larger “all files” .. as that won’t work. You don’t need to put in serial number until it asks for it in couple of days of use. Not needed for setup of theme, which you activate just like any theme in WordPress from the appearance > themes panel.

v1.8 will have option to turn off …
search forum for “fix” to turn off the lazy loading feature in 1.7.

G+ “scrapes” the image sometimes and doesn’t always use the meta data. Nothing you can do about that, except make sure the “featured” image you select at bottom right of the post panel matches the image you want them to grab. No guarantee they will … nothing you have 100% control over, unfortunately.

If using v1.7 this may be due to beta of the ‘lazy loading’ element … which is causing some issues on some servers.

you should “go back” to v1.6 and if you don’t have that, request from
contact@tagdiv.com

Can also be a caching issue.

Make sure you set a featured image and make sure you’re using a plugin like Yoast SEO or similar to ensure proper OG image tags are being added; otherwise Google may try to load the “first image” it sees on page above a certain size.

Weird. The regular Facebook button for me opens pop up with the photo, headline, first paragraph and space above to write a comment — FB no longer puts the words “comment on this …” … they just assume you want to if you click up there.

I’m using the regular theme FB button and *not* the “counter” button.

Also note re speed that using “child” theme is a CSS redirect and is actually slower than loading the main theme directly. Using ANY child theme increases chances of seeing “flash of unstyled…” issues.

Make sure you specify a featured image.

It might be a plugin doing that in your old theme or custom import function?

Wordpress.com supports embed of FB, but I wasn’t aware WordPress self-hosted supported OEMBED of Facebook content, and it’s not listed on the WP codex for embed support – https://codex.wordpress.org/Embeds

HOW exactly are you “embedding” something from Facebook?

One of these methods?
http://www.wpbeginner.com/wp-tutorials/embed-facebook-status-posts-wordpress/

You can also try this:
https://wordpress.org/plugins/wp-embed-facebook/

• This reply was modified 11 years by simchris.

Try my upgrade guide (see sticky topic top of forum).

And you will need to re-apply your changes/customizations to the new version files, of course.

apologies if I was the one ‘not getting it’ 😉

Make sure to clear cache; be sure to run regenerate thumbnails to have them built to match module sizes. In some cases make sure “crop” button is checked on the media page of main WP admin panel.

Also remember not to use high ascii characters in file names … like ” í ”

often you can look at your page source to identify such issues:

Manolo-Díaz-Yogome-fundadores-1024×628.jpg” alt=”Alberto Colín y Manolo Díaz fueron hasta Silicon Valley para proba…

One assumes you have replaced all your plugins and theme files and reinstalled WordPress to ensure any infected or compromised scripts and exploits have been scrubbed.

4.4.3 does not list any fixes for vulnerabilities and I’ve not seen any industry warnings on vulnerabilities for 4.4.2

https://wpbakery.atlassian.net/wiki/display/VC/Release+Notes

If you believe 4.4.2 is the flaw, you may want to contact the WP Bakery folks — or put in a support ticket with them if you have identified a flaw and WHY you think the plugin is causing your site to be hacked exclusive from other plugins and code you’re using.

Which version of V.C. are you using?

Have you checked security of your other plugins? Did you update Yoast SEO which had security flaw? Did you update/delete old version of Revolution Slider from early 2014?

Have you renamed your main login from “admin” and deleted that user? … did you change all user passwords to “strong” passwords after intrusion?

are you using “limit login attempts” plugin or similar?

Are you using WordPress 4.2 — 3.9 has security issues. Make sure you have latest version of WordPress.

Have you deleted old plugin folders and old theme folders you’re not using? Old insecure plugins with vulnerabilities can still be executed directly.

Have you tried using something like WordFence if your site is so vulnerable?

Is your server using CSF or other firewall to block port scans and flooding, to totally block bad hat IPs from multiple intrusion attempts?

You need to be aware of ALL such issues, and not just ONE plugin. You can also check the forum for VC on their website(s) for info on the “changelog” for any security issues, and also check SECURI to see if one of your plugins may be vulnerable “right now.”

http://blog.sucuri.net/2015/04

You may want to consider using a security system if you’re unable to lock down your system on your own:

https://wordpress.org/plugins/wordfence/

https://sucuri.net/wordpress-security/wordpress-security-monitoring

I just have mine empty in the widget so nothing appears there.

Roll back the theme, plugins and VC to the versions included with 1.6 — remove all the old (new) plugin folders; make sure you clear cache(s) etc.

1.6 works well; using on 3 sites with zero trouble, 1.7 has couple of things with lazy loading, and some php issue with some code not well used by older servers. And with some plugins that auto-generate thumbs, the lazy load seems to cause the thumbs to get re-written or some bizarre thing cause a loop of doom which will crash server or domain at some point (in our case anyway).

If you can clean house and roll back to 1.6, it’s great and stable.

Templates are built-in to the theme, which you specify in your preferences in the theme panel and when creating a post. You don’t need to import templates, they are included with the theme. A “style” and a “template” are two different things.

You can import the demo content which has fake stories, and uses the default layout of the theme.

I’m sure TagDiv will get back to you next business day to try to better answer your query.

Upshot – the layouts are included with the theme — open a post and note all the options for layouts; note the theme panel for layouts and note you can specify default template for posts and over-ride that on per-post basis.

Demo content with using layout 4, won’t make all your new posts layout 4, you need to specify that as your choice for default and/or CHOOSE which layout template you want to have when CREATING a post.

The layout for any post might be based on the actual content you post — a demo story with 3 photos would look different than a new post you create with 2 photos and no drop cap, etc. — as I’m sure you likely already know.

But wait for TagDiv to help, I guess you’re not “getting” my attempt to help on how to explore the built in LAYOUTS you already have — the demo content doesn’t add to that, it just uses the built-in LAYOUTS to populate dummy content. You already have all the LAYOUTS from the demo!

Enjoy! 🙂

Stick with version 1.6 — don’t use 1.7; wait for 1.8

Yes, so why not send the email to get the demo content download file?

I’m presuming you’ve already done that, so presumably a non issue.

All the demo styles are built-in you just activate from the “import styles” at bottom of theme panel, which presumably you’ve already played with.

Skip Newsmag 1.7 as it has a funky resource issue …

ask for 1.6 from Tagdiv, or wait for 1.8.

• This reply was modified 11 years by simchris.