Dave Naylor

Think of it the reverse way. Removing in-line styling from a part of WordPress core solves a problem for people who try their best to make the web more accessible by maintaining standards. Think of it from a business perspective, in-line styling can effect page speed and shock horror Google ranking.

WordPress is modular, so if you want to carry on creating web content in an inefficient way for ease of use, install the plugin that returns and actually improves the desired functionality.

OK that site is making use of a jQuery horizontal scroll plugin (not a WordPress one). If you Google for jQuery horizontal scroll you can kiss goodbye to a few hours as you play with them all.

There may be a WordPress slideshow plugin that can do a similar thing or you could make use of the jQuery plugin directly in a custom template. Of course, that involves getting you hands dirty in code.

The problem is, if you were to have your portrait images displayed in the slider at the same height as your landscape ones, you’re going to end up with the images not filling all the horizontal space. Your landscape images would look fine and the portrait ones would be slung over on the left if you obviously maintained the correct aspect ratio.

I think the mix of the two image formats is the real problem and you should try and just use landscape images, or cropped portrait ones.

By the way, you linked to a preview page, no-one else but you can see that.

@emg I don’t think this is actually an issue. On a vanilla 3.9 install, using the visual editor, if you highlight text, hit the anchor button and then provide a URL and title, the title attribute is placed before the href one. It’s not a case of plugin incompatibility or a badly installed update, it’s just the way it is.

Just found this page. I don’t use Jetpack so I don’t know how relevant it is:

http://jetpack.me/2012/01/17/how-to-view-your-email-subscribers/

Just found this at Google Developers

Write your web page content to make compression most effective.
To ensure that your content compresses well, do the following:
Ensure consistency in HTML and CSS code. To achieve consistency:
Specify CSS key-value pairs in the same order where possible, i.e. alphabetize them.
Specify HTML attributes in the same order , i.e. alphabetize them. Put href first for links (since it is most common), then alphabetize the rest. For example, on Google’s search results page, when HTML attributes were alphabetized, a 1.5% reduction in the size of the gzipped output resulted.
Use consistent casing, i.e. use lowercase wherever possible.
Use consistent quoting for HTML tag attributes, i.e. always single quote, always double quote, or no quoting at all where possible.
Minify JavaScript and CSS. Minifying JavaScript and CSS can enhance compression both for external JS and CSS files and for HTML pages containing inlined JS code and style blocks.
Don’t use gzip for image or other binary files.
Image file formats supported by the web, as well as videos, PDFs and other binary formats, are already compressed; using gzip on them won’t provide any additional benefit, and can actually make them larger. To compress images, see Optimize images.

So it would seem that the key is consistency and ordering should be alphabetic. The only reference to href is that it should be first, because it’s most common.

The ranking depreciation you experienced may have been due to inconsistent ordering rather than not having the href first.

The relevant part of that message is:

WordPress could not establish a secure connection to WordPress.org

Your site is failing to connect to WordPress.org over SSL which is usually indicative of a server configuration problem. Maybe curl isn’t compiled with SSL or the HTTPS root certificates are missing or invalid.