Search Results for 'pagespeed'

Note – the freezing happens on various sites to lesser degree I noticed the other night myself, even on my own website … only happened when I first turned it on — and I’m now thinking that maybe the iPad was doing some kind of background refresh like getting iCloud photos or something — but not sure on that.

On a simple page with 100/100 pagespeed score, two logos, one photo, and font awesome, I noticed the slight freeze going down page at a certain point. Odd. On my page all the above fold CSS loaded up front, and using native ipad fonts other than FA.

Not theme specific — I also noticed this issue on LA Times where the page just died, and went blank partway down.

Later on, both worked fine — so I suspect some background process on iPad, but I don’t have a fancy “activity monitor” installed, and have not turned on the developer mode on my new iPad (had that on for old one). Need to connect to my computer to activate that.

But it was temporary — then worked just fine. Very weird.

Just adding to the “bizarro world” topic … nothing to do with this theme specifically, as I notice the “twitchy” behavior on multiple sites the other night — all around the same time; but then no issues later on (and I have a smooth scroll jquery thing too, so yeah — super noticeable)…..

Might actually be an issue with jquery — hm.

But in the description on themeforest you advertise the website as ultra fast and light weight but a score of 30 on pagespeed is nothing like that…

Run your website through Google’s PageSpeed Insights for tips on how to optimize your website. Also put non-essential code at the bottom of your body, like Adsense and Analytics-code. 🙂

That should bring you a long way.

I just spoke to host (Godaddy) they said it’s not an issue with .

They recommend I optimize the database tables via php my admin, which includes compressing the tables as it may be a “resource issue” Would this work? I don’t want to waste time doing this since they had led me down the wrong path before.

Will using this tool help with optimizing the database tables or are these recommendations only to speed up the site?

https://developers.google.com/speed/pagespeed/insights/?url=jewishbreakingnews.com

Download the image from both sites, and compare in Photoshop to see what the bit difference is.

Upload an image to both sites named test-a-500×300.jpg and test-b-500×300.jpg or similar, then after live, compare both images ‘on page’ by re-download and compare in Photoshop.

For instance, one server might be using mod_pagespeed and converting images to WEBP format; one size might have higher compression setting set in wp-config.php — one site might be using jetpack or smushit; one site might be using http/2 compressing entire page into one packet.

Lots of possible causes — but you need to compare a fresh image put on both sites, then check the final file versions to see what changes are made to thumbs, to help debug the differential between the two.

Food for thought, anyway.

Actually, I’ve been doing SEO since 1995, and ran a leading company in that space from Jan. 1996 to Jan. 2005, and have 10 million impressions per month. But whatever… not wrong.

If you look at Google’s own information on their algo – you can have more than one h1 on the page with proper modern markup … the header section is separate from the article section, and the h1 for the site name on the logo is totally acceptable in the DOM for that.

Their algo looks at h1 for ‘content’ in the article area to match page content, and *that* h1 should match the meta tag for page title and be semantic to the content within the article area – the de-facto page content.

HTML5 specifically is engineered to support more than one H1 tag to identify the ‘header’ element per ‘section’ — h = header, not seo.

If your site is, for some reason on old HTML, xHTML, etc., then yes only *one* h1 tag per page is correct. Under HTML5, more than one h1 tag used within ‘sections’ is correct.

Again, anybody telling you otherwise doesn’t know what they are talking about and has not lived on Google’s dev site, or the HTML/W3C dev community as I do.

So, if your site is “Giant Killer Puppies” and you do a page about “Best Food for Brown Puppies” then you can have h1 tag on your logo with site name in the ‘header’ section, and this is *separate* than the h1 tag for “Best Food for Brown Pups” which would *also* be used for referential links within site, inbound and social links, meta tags, and possibly alt tag for the hero photo on page.

Duh.

If that doesn’t work for your site, you have some DOM / markup errors.

We use this methodology on 25+ sites with top ranking for all content, millions of page views, and we’ve been building sites for 23 years, doing marketing since 1981, and doing SEO longer than most folks on here had a web connection.

Share and enjoy!

Read up on HTML5, Google’s own help site, webmaster tools info (search console), PageSpeed Insights, etc.

Welcome to the ‘semantic’ web — using header tags in proper way, with good content helps SEO, doesn’t hurt it, and there is *no* penalty with Google for using h1 tags correctly in modern markup — where appropriate and not intended to ‘black hat’ the usage.

I won't be on this site anymore starting Sept. 1, so winding down my help here *forever* -- so take of it what you will.

• This reply was modified 8 years by simchris.

Howdy … I have no idea which site is on my profile here, sadly, so might have to peek at that 😉 I actually have a main business site which hasn’t been updated in years, as I’m building my own WP theme from scratch for first time since 2011 for various reasons, from Bootstrap 3.x. But I manage a news network which uses TagDiv themes, and our main news ‘parent’ online since 2000 is mix of static shtml with 100/100 pagespeed score, and then news platform running on WP, but with a semi-custom theme not running TD, due to fact we started that prior to TD being in business and way too much hacking to switch.

As general rule for hacks:
a) yes, if you update theme, they get over-written as common sense — if you edit functions.php and then update theme, it uploads new file, so old one is gone. So, common method is to keep track of changed files, and edits by line number, then re-apply to new theme, then upload new theme with the same hacks applied (FTP, and I use TextPad on Win10, or BBEdit on Mac).

b) what I’ve started to do, with this new theme from scratch project, is move all mods to a plugin. This allows me to keep hacks, security mods, speed mods, inserts, RSS hacks, etc. in “one place.” — This is useful for stuff you don’t want to change every time with TD or other themes, but can’t always address stuff you actually do hack. — For instance, I take out the login code from TD theme headers. Have to do that every time. I also remove the xmlrpc, pingback or any of that stuff. == but again, with WP, you can often create your own plugin with a function to ‘enqueue’ something to the WP header, and this gets inserted to WP header, same way the theme panel does, but if you put it in your own plugin (which is insanely easy to do), then it survives theme update.

Not sure that helps — but food for thought. Thanks for kind words.

Also, I stopped posting links to my sites here as they end up getting barrage of hack attempts due to popularity of TD themes and a few bad actors lurking here.

As to JSON, I’m just learning how to build that from scratch myself, for this new ‘in house’ theme project — so, guess what I’m doing this coming Saturday! 🙂

Google doesn’t like ‘resized with CSS’ images as the browser has to do the work, which is considered slow for mobile vs an optimized “serve images at actual size” methodology.

One trick is to change the 3 image sizes made by WordPress, separate from the theme to be your 3 most use sizes. Also consider cutting couple of modules.

Or, you could turn sizes off, and thumbs won’t be made, and will be resized in some instances (larger to small, but smaller to large will not fill boxes).

Try it; but then also check your Pagespeed Insights from Google for “make images right size…” warning.

If your server does mod_pagespeed, you can have it build temp cache images on the fly, including conversion to webp format. Again, something you’d need to test.

(I don’t work here; but we went through this. We ended up limiting “total number of sizes to 6” to keep thumb explosion down.)

ALSO: be sure to change the default compression for thumbs in your wp-config.php, as most small thumbs don’t need to be razor sharp, and so compression level of 50 works for most stuff!