GregMcAbee

Hi,

I was having this same issue. I couldn’t get the right CSS for the above the fold. So I did a speed test at WP-ENgine where I host and it came back stating

“Reduce page complexity

Your page has 1103 DOM elements (HTML tags). The “right” number is highly dependent on the length, purpose, and visual concept of your page. (This is especially true if the elements are deeply nested.) There are sometimes very good reasons to have many tags (structural HTML can improve search results, for example), but you should generally look to keep the number of DOM elements to a minimum.

Common reasons for this include a poorly coded theme, using a page builder plugin, or complicated page designs with lots of widgets and content.”

So I started taking a hard look at widgets and pulled the Archives which double linked all of my things. I had another widget I created for an Audio Book I did for Wayne Jacobsen, it had 21 additional links to mp3s on each page. I deleted that once because you can find it through another link. I probably got rid of 3 or 4 big widgets.

I emptied all my caches, then I was able to choose the right above the fold CSS and those errors went away.

That left me with a 91 on mobile and 97 on Desktop. Probably good enough but I’m not one to settle usually.

My last problem was “https://www.godsmessageontheweb.com/wp-includes/js/jquery/jquery.js?ver=1.12.4”

I went into autoptimize and selected “Also aggregate inline JS?” and erased the entry /jquery/jquery.js from the line Exclude scripts from Autoptimize:

I saved and emptied the cache, cdn, and cloudflare. Now 100% on Mobile and 100% on Desktop.

The only things I have set are:

Optimize JavaScript Code? Check
Also aggregate inline JS? Check
Exclude scripts from Autoptimize: seal.js

Optimize CSS Code? Check
Check this if you don’t need or want Google Fonts being loaded. Check

Inline “above the fold CSS” while loading the main autoptimized CSS only after page load. Check the FAQ before activating this option! Check and inlined.

Proof: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.godsmessageontheweb.com%2F

Thank you very kindly, sir! That puts me at ease. I think I caught the view out of CastFeedValidator and it stuck in my head at one point or another. Glad to have that answered before I set out to fix the unfixable. ??

I fixed this today finally. The error is dead correct. There is not enough room for the REDO logs to hold all of the changes. I had to log into my MYSQL server and execute a command to see how big the redo logs were.

Open your MySQLin linux shell and execute this command

show variables like ‘innodb_log%’;

The size returned is in Byres. Mine was 1048576 which = 1MB

I needed to bump the number to 6 MB or 6291456 and restart mysql to get the change to take effect. My host had a place to change InnoDB Log File Size and if you don’t. Call tech support and tell them to set InnoDB Log File Size to 6 MB and try another scan. If you see the error again keep bumping it up in small increments.

Warning. My host told me if you set the number too high. You can’t recover and your database won’t allow you to shrink that number. So please, bump the InnoDB Log File Size in small 1 MB increments until your scan finishes. ??

I hope this works for everyone.

I spent almost a month on this prior and I fixed it by excluding graphic files from the scan. It was excluding the .jpg and .png files that fixed it for me and allowed me to complete a scan.

In the options Menu – “Exclude files from scan that match these wildcard patterns. (One per line).”

*.sql
*.mp3
*.pdf
*.jpg
*.png

Sorry, wrong topic I responded to.

OK, I’m not sure I can explain how I fixed this but I’ll give it the old college try. I left the SSL certificate on my server, and deleted all the wordpress files. I reinstalled from scratch via command line.

After the re-install everything worked except my admin Panel. I then disabled my 1 plugin wordpress-https. Then I went to my host setup panel and turned off force everything to ssl. Then I was able to get into the admin panel and then re-enabled wordpress-https. The ONLY thing I did this time was next to the first entry labled SSL host which had my site name beginning only with www the box next to it was blank for the port. I put 443 in there and saved and everything came back. I don’t think it defaults to 443, you have to type it in the box and save it. I decided to leave force SSL off and went back to my site control and had everything from http: forwarded to https:

All seems well now.

In short, allow your site to do the forwarding, but also activate the wordpress-https plugin and put in 443 next to your site name. That did it for me.

All,

I fixed this error for my site https://www.godsmessageontheweb.net this evening. My issue started after my WordPress site was hacked. After my ISP did a restore it just would not work. I tried everything listed above.

My advanced-cache.php file in the wp-content directory actually was being represented as a folder instead of a file. I could not even delete it with my FTP software. So I used the File Manager on the ISP to delete and re-uploaded it from my last backup and it started working right away.

You might want to look through your structure and verify no other .php files are being represented as directories. I hope this helps someone out there.

God Bless,
Greg McAbee

All,

I fixed this error for my site https://www.godsmessageontheweb.net this evening. My issue started after my WordPress site was hacked. After my ISP did a restore it just would not work. I tried everything listed above.

My advanced-cache.php file in the wp-content directory actually was being represented as a folder instead of a file. I could not even delete it with my FTP software. So I used the File Manager on the ISP to delete and re-uploaded it from my last backup and it started working right away.

You might want to look through your structure and verify no other .php files are being represented as directories. In my case the file that looked like a direcory was 0k. I hope this helps someone out there.

God Bless,
Greg McAbee

That is great. Thank you for your time. It is greatly appreciated. The support around here “rocks” by the way.

Maybe I am putting too much attention to the point that PodcastAlley throws an error when I try to add it? It rejects it on the basis of a critical channel and error 1511.

It seemed to be some sort of vulnerability. But if the feed is ok I am fine with that.

I just validated again at https://www.feedvalidator.org/check.cgi?url=https://www.godsmessageontheweb.net/?feed=podcast
and still see the errors. It sounds like I can safely ignore them?

Thanks in advance.