It did the same thing to mine. I’m not able to revert back to last version and my site is a powerhouse so something definitely went awry for this update.
I’m getting the same message also and I’ve had this theme for years.
hello,
would you be able to include an example of how you did this as all I can see is Div Class for the featured image and the JS Path is this
document.querySelector("#tdi_45 > div > div > div > div.td_block_wrap.tdb_single_bg_featured_image.tdi_56.td-pb-border-top.td_block_template_1 > div")
I can’t figure out how to put this in the way the PHP file is.
Any help on this would be greatly appreciated.
Thank you.
I’ll let you know as I’ve had to hire a coder for the 4th time now with this theme. On here they tell you to take it to the e-mail so as not to share problems we’re having that aren’t getting fixed on here…
@usacarry Nothing got fixed. Very frustrating as I keep having to hire a coder to fix the problems the developers have created for us with this theme.
Thank you too! Getting a tech person to fix this has cost us over $600, and it’s things in the theme development that are causing this.
Since Google is now demanding these changes, it only behooves the developer to update as more people will continue using and buying it.
As these definitely fall within the theme structure, will you all be doing another update to deal with this soon?
I do wish that they could respond as quickly as you. I e-mailed them 5 days ago and am still waiting. My error log continues growing quickly with that one error from Line 209.
Still waiting on support team and the PHP error (the only one) keeps growing over 1 GB every day. I have to keep deleting it every 12 hours so your team can even open it, but they’ve still not looked or done anything.
Basically, it’s trying to get the featured images and home page images above the fold to preload as that is affecting the Largest Content Paint scores for most people.
It’s just trying to get the code you all use to preload, that’s it. Otherwise, everything else is fine.
https://movietvtechgeeks.com/storms-hit-on-walkers-fine-is-a-four-letter-word-108-in-multiple-ways/
If you use a caching plugin like WP Rocket, it can minify. ANother great site is Unused-CSS (dot) com as it will run a full analysis of your site and take out all the code you’re not using so you just download their CSS file and replace the one you have with that one. That will easily get your Unused CSS score way down.
JS is much harder as many plugin use that.
Google is the pain since they love to do these massive algorithm changes and expect all of us to it…or else. But they fail to let us know how to make these changes properly. This is why so many sites keep going under as they can’t keep up with Google’s demands and suffer in the rankings.
When it comes to the LCP thing, I truly think the developer of this theme is responsible as it’s their code that is keeping us from being able to properly preload the featured images. I can pretty much guarantee they will have another update by May 1 since Google’s new algorithm kicks in then.
Thefeedski:
Now you just have to focus solely on Mobile as Google is literally letting go of Desktop analysis and focusing 100 percent on Mobile. Sadly, the desktop doesn’t transfer to mobile, and one of the best test settings is to run for 3G phones as it’s better to run tests on slower bandwidths to see what needs to change on your site as the majority of phones out there still run on those.
Google will test on that basis also so while it’s great to run on the fastest bandwidths, reality shows that we need to test at the low end too.
Basically, you optimize your theme as every theme out there is going to have issues since how many plugins you have also determines this along with how many blocks, extra things you use.
Our Newspaper site has gotten up to the 77, 96, 93, 98 score, but it’s been two months of researching everything that is suggested. There are a lot of factors including server, which version of PHP you are running, which caching programs you use, if your using webp, etc.
It seems overwhelming at first, but if you just break it down one by one, it’s all easier to deal with.
As Google is going into full mobile mode in May, website owners will be required to pay attention mainly to their mobile number. Desktop numbers usually show good for most sites, but with Google making bigger requirements for mobile page speed (especially with the dreaded Largest Content Paint) we have to do research on what to make these numbers go lower to keep the big G happy.
Yes, we have all the things on the list so I’m sending over to the support team. As several people have had this issue, it might be good to actually list the solution for others that will surely have this problem.
Hey aamirmehmood7000,
Was this able to be fixed for you as I’m getting the same error and only PHP error being thrown about Line 209.
Thank you!
It seems like there would be a way to Preload the container as it is
tdb_single_bg_featured-image
And be able to just have that done. With Google really pushing for this, I have to imagine the developer is trying to get this one right as it will affect everyone with this theme.
Thank you for bringing this up! I’ve been trying to figure out how to Preload the homepage featured images along with the article featured image only. Google is really focusing on these aspects, and I had assumed the theme would be updated with this in mind.
I did find this code for preloading featured images and wanted to let the Newspaper developer see if it would work with this one.
It would be great to have this figured out before May hits with Google’s changes.
Thank you.
/**
* Preload attachment image, defaults to post thumbnail
*/
function preload_post_thumbnail() {
global $post;
/** Prevent preloading for specific content types or post types */
if ( ! is_singular() ) {
return;
}
/** Adjust image size based on post type or other factor. */
$image_size = 'full';
if ( is_singular( 'product' ) ) {
$image_size = 'woocommerce_single';
} else if ( is_singular( 'post' ) ) {
$image_size = 'large';
}
$image_size = apply_filters( 'preload_post_thumbnail_image_size', $image_size, $post );
/** Get post thumbnail if an attachment ID isn't specified. */
$thumbnail_id = apply_filters( 'preload_post_thumbnail_id', get_post_thumbnail_id( $post->ID ), $post );
/** Get the image */
$image = wp_get_attachment_image_src( $thumbnail_id, $image_size );
$src = '';
$additional_attr_array = array();
$additional_attr = '';
if ( $image ) {
list( $src, $width, $height ) = $image;
/**
* The following code which generates the srcset is plucked straight
* out of wp_get_attachment_image() for consistency as it's important
* that the output matches otherwise the preloading could become ineffective.
*/
$image_meta = wp_get_attachment_metadata( $thumbnail_id );
if ( is_array( $image_meta ) ) {
$size_array = array( absint( $width ), absint( $height ) );
$srcset = wp_calculate_image_srcset( $size_array, $src, $image_meta, $thumbnail_id );
$sizes = wp_calculate_image_sizes( $size_array, $src, $image_meta, $thumbnail_id );
if ( $srcset && ( $sizes || ! empty( $attr['sizes'] ) ) ) {
$additional_attr_array['imagesrcset'] = $srcset;
if ( empty( $attr['sizes'] ) ) {
$additional_attr_array['imagesizes'] = $sizes;
}
}
}
foreach ( $additional_attr_array as $name => $value ) {
$additional_attr .= "$name=" . '"' . $value . '" ';
}
} else {
/** Early exit if no image is found. */
return;
}
/** Output the link HTML tag */
printf( '<link rel="preload" as="image" href="%s" %s/>', esc_url( $src ), $additional_attr );
}
add_action( 'wp_head', 'preload_post_thumbnail' );
As this didn’t get fixed in the latest update, is there a way to keep the featured images from lazyloading as that is what is causing the Largest Content Paint Image to run high. WP Rocket actually has a section to list the files not to lazy load, and I’m assuming there must be code to do that on here. Thanks!
That did it perfectly! Thank you so much.
Hopefully this will help others too.
I’ve been trying to get it running, but I can’t get it going either.
Thank you, but inserting that into the Custom CSS area made all my pages and homepage go completely blank white.
When I refreshed, you could see the page for a second, but then it would go to a blank white page.
After I took the code out, it went back to normal.
Curt
I’ve followed the steps for the CSS Analyzer, but the dropdown won’t show on my desktop with Chrome. I’ve turned off caching also. Just a little stumped on this one.
Thanks!
Thank you for bringing this up as I’m having the same issue after updating. Thankfully, the update went without a hitch. Using Newspaper Pro Default Template.
Has anyone else encountered this yet? I’ve tested with other themes, and Newspaper is the only one I’m finding having this issue after updating to Google AMP 2.0.8
