Thanks Mike for going above and beyond.

I think this is caused by a mod I made to the search script. Using a snippet from another forum post.

I’ll check the file and report back.

EDIT: See resonse below. Custom Code is fine. No custom JS in fuctions file. This is caused by Enfold see my latest reply for location of problem.
Your fix seems to work though but needs adding to the 4.9 release of Enfold

• This reply was modified 2 years, 11 months ago by thinkjarvis.

@yigit
Im going to try the following
Bulk edit all products. Mark as Draft, Then Bulk edit Publish again.

Needs to be done out of hours I think!

Hi Ismael,
This shows just how little time I spend with a WordPress default theme enabled.

The Post Formats are a WordPress function and not specifically Enfold so outside of your scope. Sorry for reporting this as an issue.

Please close this issue as solved.

I have fixed this after reading through the JS with a bit more care.
I changed the custom JS script to look for .blog-meta a instead of .read-more-link a. This grabs the custom post link instead of the read more link solving the issue.
ORIGINAL

	// News Page JS
	window.addEventListener('DOMContentLoaded', function() {
	(function ($) {
	    if ($("body.news-page .template-blog article").length == 0) {
	        return;
	    }

    // Whole Article Clickable
    $("body.news-page .template-blog article").each(function (elem) {
        var thisElem = $(this);
        var newsPostLink = thisElem.find(".read-more-link a").attr("href");
        thisElem.append('<a href="' + newsPostLink + '"></a>');
    });
}(jQuery)); 
 });

CHANGED TO

	// News Page JS
	window.addEventListener('DOMContentLoaded', function() {
	(function ($) {
	    if ($("body.news-page .template-blog article").length == 0) {
	        return;
	    }

    // Whole Article Clickable
    $("body.news-page .template-blog article").each(function (elem) {
        var thisElem = $(this);
        var newsPostLink = thisElem.find(".blog-meta a").attr("href");
        thisElem.append('<a href="' + newsPostLink + '"></a>');
    });
}(jQuery)); 
 });

I’ll speak to the client about getting Debug turned on so we can investigate.

Like you said – It might be one of the posts needs re-publishing on Page 3 – Causing the Post loop to get stuck.
A bit of trial and error is required to test this theory. We could change these posts to draft and see if we can get it to work still.

Will get back to you here if we discover anything this end.

Hi Gunter,

Thanks for getting back to me.

I’ll save this for a rainy day. If I have any success I’ll report back. Going to be a while before I can pick it all apart!

I’ll raise this as an issue after I have done some more testing. No action required at the moment
The LCP seems to be heavily affected by custom fonts. I need to investigate further before I raise this as an issue. Even with SWAP enabled on fonts, the First element on the page is not fully loading until the fonts have downloaded (looking at the waterfall). I had a site recently where I accidently uploaded a font that after compression was still 500kb WOFF2. The LCP was extremely high. I used Font Forge to bring the size down to about 40kb and the LCP score started passing. Wev vitals is therefore waiting for the font to download and processed before LCP is calculated.

I was then thinking. Is there an event listener in the JS files delaying things like “DOMContentLoaded” Specifically related to the fade in on the first element or slider titles and captions.

I’ll have a look when I get the chance. I think it might just be the way Chrome handles Preload of Fonts rather than anything else.

Cheers Gunter,

I wasn’t chancing for immediate release :) I’ll keep my eye out for it and apply it to the client’s site.

Looking forward to seeing the new Post CSS file changes as well!

All the best,
Tom

Thanks Mike,

I’ll try changing the settings js was set to load in the footer on my test site.

is the issue that the script must run after the main js file has loaded or before? I may still be able to load scripts in the footer and add the code snippet but adjust the priority that they load. Like setting wp_head functions to -1 priority so they are loaded before other critical css generators.

This error also applies to the main menu in the header when desktop tests are ran.

But only occurs in the socket during mobile testing.

Both need investigating if you can.

Thanks,

Tom