I would suspect auto poster, jetpack, polls, and anything running in wordpress seo that doesn’t need to ….

You might also try using some good plugins like wp-optimize, make sure your images are optimized (e.g., not loading 5MB image for home page vs 50kb), check to see if you have a member sign up script or contact form being abused (e.g., do NOT use “send auto reply” for forms as they can be used for people to send spam, by simply putting in somebody else’s email and putting spam topic on form, boom it gets sent to somebody from YOUR system); check the error logs for your domain via your web hosting account to see if you can narrow down a specific plugin causing the issue.

Some “third party” plugins are *not* fully compatible with WP 4.0 and sometimes you may two plugins doing same thing … I often see people using Yoast to make sitemap while also running a sitemap plugin, etc.

That might not apply to your situation, but just some feedback. Not having any issues with theme and the “recommended” plugins on our server, and we’re running some high usage stuff like auto thumbnail and thumbnail upsize, etc.

I should get my new iPhone 6 (not PLUS) today …. and will be checking my 4.2.2 site once I have a spare brain cell. Note the iPhone 6 I think defaults to some kind of zoom mode or larger pixels mode or something; not sure if that impacts Safari, but it might be something you can adjust, although have not played with that yet. Friend is supposed to stop by this weekend who has the gold (LOL) iPhone 6, so may be able to check then.

Well… with some templates the only way to show a gigantic image at top outside the post is with a featured image …. so, maybe that is normal.

@Bichareh

A “lazy loading” function for images might help; to “lazy load” the images until you scroll down on page to view gallery, meaning it loads some of the images, then loads the rest as one scrolls. A plugin might do that for you in the interim.

I kind of miss the days of LOWSRC b/w images we’d load prior to progressive back in the day.

Looks like something is trying to access the /js/ file by an index, which isn’t there. Nothing should be looking in that directory or navigating there on the web.

Meaning people should not be going to
yoursite.xyz/wp-content/themes/Newspaper/js/index.html

Might be a hacker, or you could be using a plugin which is trying to send requests to that directory without specifying the actual element to load from the folder.

You could try just putting an empty index.htm file there to stop errors, then perhaps use referrer data to see WHERE the requests for index.htm are coming from.

Probably a much better way to do that … but I’m not getting those errors myself.

It moves my styles to bottom; might be a conflict with a plugin you’re using; but maybe not. Moving them to bottom doesn’t remove the render blocking warning; it just moves stuff to footer.

• This reply was modified 11 years by simchris.

You would likely need to remove the CSS from the theme for the responsive @media viewports.

Responsive design is better for SEO, and Google actually dings you for not having mobile friendly site now, and with more and more people doing their web surfing on mobile devices, it isn’t advisable to “turn it all off….”

But you can hack the style.css sheet to remove the @media points for other sizes, and see if that works for you.

Since the theme is sold as designed for responsive design, you could also look for a fixed layout theme, perhaps; but I’d try hacking the style.css sheet first 🙂

They do this normally unless you put in a background color from the theme panel to create boxed layout 🙂

@ctomlin
the theme actually has a section where you can put in your Google analytics code to print at bottom of your pages/posts.

I think it’s in the admin panel under “post template” …

I think would annoy people to have that appear right no top of the article, personally, vs sliding into the sidebar area.

You could likely edit the module to have it slide from left to right vs right to left; just edit the DHTML/CSS for that.

Yeah, theme is pretty good about loading larger logo. I did the same thing, and went ‘duh’ … I had wider but not as tall logo, and worked just fine. I had ‘expected’ it to be distorted, but seems you can just upload the logo the size you want and it works, which is awesome. 🙂

As to the “most efficient” way to load the images; you’d have to play with that yourself and figure out what works the best for “all uses” … I don’t know how much of a tradeoff it would be to have to constantly do if/then loading of different images based on the mobile size with gallery type layouts. Lot of queries.

But, my personal thing would be to actually turn off the images for mobile except for the single featured image on the page, and for home page just show tiny thumbnails 100×100 or whatever for the list of stories.

So, on posts you’d see ONLY the single small 300px image and no other images, much like the Apple “reader” mode except with a single image (featured image).

I never test speed of “home page” as that isn’t relevant for most SERPS anyway, since the content is changing and you want your posts found under the topics not the home page anyway.

Still cracks me up that response time of 0.22 seconds is “slow” …. sheesh.

Well, basically it is serving up an image at smaller size and so caches the “scaled” size as part of the “rewrite” images module.

Sometimes it doesn’t work if the optimized image would be larger in size than the original, which is funny since I usually optimize stuff very much in the extreme.

But:

ModPagespeedEnableFilters resize_images

This attempts to resize any image that is larger than the size called for by the width= and height= attributes on the tag or an inline style= attribute. The original image is replaced only if the image file is smaller after resizing. Image resizing is lossy by nature, regardless of image file format.

Note: It also strips color profiles and metadata even if strip_image_color_profile and strip_image_meta_data are disabled.

Note: If both resize_images and resize_rendered_image_dimensions are enabled then resize_rendered_image_dimensions takes precedence.

Partnered with:

ModPagespeedEnableFilters insert_image_dimensions

This flag inserts width= and height= attributes into tags that lack them and sets them to the image’s width and height. Note that this can cause image stretching or shrinking if CSS rules specify only one image dimension (see Risks below).

So, one of those things to play with for super advanced users, like removing width=500 height=375 and simply using style=”width:90%;height:auto” can do some interesting things.

Eventually this stuff will be built in to everything, since rewrites on the fly solve numerous responsive design issues.

AND: we just now got mod_spdy and mod_pagespeed working together!!!! WOOHOOOOO!!! Doom will ensue! (kidding)

Normally with theme licensing to create multiple CLIENT / CUSTOMER websites with a theme, you would get a developer license or a quantity discount / rebate from TagDiv, for say buying 10 licenses. Generally a single license for a WordPress theme applies to your own use only, meaning sites you own, such as a blog, company site, project site, family site — all owned/operated by you (such as you owning the domains, sites related to your own activities).

This is standard industry practice.

Obviously reading what “regular license” means on Themeforest might be a good place to start:
http://themeforest.net/licenses/terms/regular/5.1

(quote)

The low-down! The nuts and bolts of this license

1.The Regular License grants you, the purchaser, an ongoing, non-exclusive, worldwide license to make use of the digital work (Item) you have selected. Read the rest of this license for the details that apply to your use of the Item, as well as the FAQs (which form part of this license).

2.You are licensed to use the Item to create one single End Product for yourself or for one client (a “single application”), and the End Product can be distributed for Free.

So, if you create three client sites, you would get three (3) additional licenses, and charge the client for a license fee for each of their single sites.

Not too confusing. 🙂

• This reply was modified 11 years by simchris.

Not sure why you would; it’s actually somewhat required by Google and Bing now to identify which page is the defacto page for indexing and to avoid duplicate content penalties.

I think you can remove it from header.php

@tcdraper
the general reason themes don’t make multiple thumbnails for the sizes you’re talking about, is that when an iPad changes from portrait to landscape it’s not technically reloading the page, just refreshing the viewport and the cached stylesheet is applied; otherwise it would be *worse* for mobile since the images would need to actually be reloaded — ever carry an iPad across the room in unlock mode and have it flip back and forth from portrait to landscape; well, you’d be reloading the images in different sizes more than once.

So, one aspect of “responsive” design (good and bad), is that it’s better to load a 25kb image once than load the 25kb image once and the 12kb image together and switch those out on viewport. Better to load the 25kb image ONCE, then resize to fit the aspect you’re looking at when you look at it.

The other benefit of using the larger image is for retina/HD displays on a mobile device which have higher pixel count than desktop; so again, if you do the pixel math, a 700×500 image on a screen with double the pixel count, loaded half size, would still provide the same number of pixels when shown half size — without having to load alternate retina/HD version of image or use “image stacks.”

This is actually one of the cool things about mod_pagespeed … if you have an image loading over and over at 80% size, it will cache the image at THAT SIZE and serve up the smaller image to people who keep requesting it vs loading the larger image and scaling it.

That was mostly anecdotal … but just some techie crap in case you were curious 🙂

@tcdraper
we’re running PHP Version5.4.22; apache, centos 6x, plesk/parallels, all the built in modern accelerators, apc/memcache, mod_pagespeed, and just last night got “mod_spdy” working on Plesk, which was fun since my data folk had never done it before and was team effort.

We’re right now (literally) working to connect mod_pagespeed to SPDY properly so we can have mod_pagespeed load and compress/cache images and other https elements when the pages are loaded 100% https.

Not using Amazon S3 CDN at moment as I can’t mentally deal with the sharding setup when all of us working on this project have never done this before and there is *NOT* a simple “how to” book on this!

I think we were getting something like 330 msec or something, and Google thinks initial response should be under 200-300. (Sigh.) We have a 300kb static page with 10 elements loading dynamically via server side includes in 1.3 seconds total, and pagespeed of 96 without CDN or caching application, and that’s not good enough? BAH!

So, far the https optimizations built into server seem to work fine for desktop, lose a point, page load goes from 1.4 to 1.5 seconds total. So, will be testing that with mod_spdy active, and then with mod_spdy PLUS mod_pagespeed to see if we can enhance the times overall.

ANyway… kind of rambling there. No real advice for you. We have a dedicated multicore XEON server, 32GB RAM, with its own gigabit switch so we don’t have to deal with a lot of the shenanigans of VPS and shared hosting. But, $650/mo. isn’t exactly cheap, either.

That wasn’t a very good answer, was it ? 🙂

• This reply was modified 11 years by simchris.

At least apache now doing spdy updates

I believe you can use it multiple times for your own sites, but you would get new license for each client site

YAY!!! Hate those pesky gremlins which hang out for a day then leave. At least they left! 😉

(This usually indicates a caching issue someplace, btw.)

You simply need to select it from the theme panel, at bottom of main screen — import styles.

You’re welcome 🙂

I cc’d that over to the page speed sticky, since I realized bunches of things I’ve answered more than once were NOT actually in that sticky!

One of these days I’ll do an updated “ONE POST” with all my fixes, but in midst of doing the migration to mod_SPDY for the server which is pain in the butt.