Calin thank you for your reply.

Lazy load is already excluded for that image, so this is not the source of the issue.
The real problem is that the LCP element in Newspaper is generated as a background-image inside a <span> (.entry-thumb) instead of a proper tag.

Because of this:

Google PageSpeed Insights reports that the image is “not immediately discoverable in the HTML”, and it keeps recommending that fetchpriority=”high” should be applied.

This recommendation cannot be satisfied as long as the LCP element is a CSS background and not a native . Preloading helps partially, but PageSpeed still flags the issue, because the image is not directly represented in the DOM as an .

Could you please provide a solution or option within Newspaper to render the LCP image as an (with fetchpriority=”high”) instead of only as a background image? This seems to be the only way to properly fix the LCP problem reported by PageSpeed.

Best regards,
Antonio

Hi Calin,
we have the same problem, only for mobile. We use LightSpeedCache. How we can solve the problem?
the site is http://www.sport24h.it.
Thank

Hi Calin,

Thanks for your reply. As requested, here’s a summary of the main blocks used on our site:

Home

Flex Block 1 / All categories / 6 posts / offset 0 / cache 1h

Flex Block 4 / Editoriali / 3 posts / offset 0 / cache 1d

Flex Block 4 / Ciclismo / 3 posts / offset 0 / cache 1d

Flex Block 4 / Basket / 3 posts / offset 0 / cache 1d

Flex Block 4 / Cultura / 3 posts / offset 0 / cache 1d

Post page

Flex Block 1 / All categories / 1 post / offset 0 / cache 1d

Flex Block 1 / All categories / 3 posts / offset 1 / cache 1h

Flex Block 1 / Related / 3 posts / offset 0 / cache 1d

👉 Our site: https://www.sport24h.it

We hope this will help you investigate why we are seeing over 10,000 transients created in a short period.

Thanks for your support.

Hello Calin

Thank you for your reply. We would like to provide more context. Please see the attached screenshot https://imgur.com/a/MVy57MR : as you can see, our site currently has over 9,000 td_query_ transients, and all of them appear to be generated by tagDiv components — mainly the Flex Blocks.

If what you mentioned is correct (that this number of transients is a sign of too many unique, uncached queries), then we must be misconfiguring something in our setup.

✅ We have already:

Assigned long cache durations to our Flex Blocks (1 hour to 1 day).

Reduced unnecessary offsets and unique combinations.

Enabled LiteSpeed Cache page caching.

We kindly ask for your guidance:
👉 What exactly could we be doing wrong?
👉 Could there be a setting or a known issue causing Flex Blocks to create so many unique transients despite our efforts?

We appreciate your support to help us identify what needs to be adjusted.

Calin

I’m experiencing a problem with the solution you recommended to optimize image loading: unfortunately, the new format prevents (Single Post Bg Featured Image) featured images from appearing in Google News snippets, and this is a significant drawback in terms of CTR and visibility.

I’d like to know if it’s possible to keep the previous format for featured images (or at least a format compatible with Google News) while still optimizing loading speed. Is it really impossible to improve loading times for featured images without losing compatibility with the Google News bot?

Looking forward to your feedback.

Thanks,
Antonio

Ok Calin, now the image loading times have improved. However, in the photo height section, I would like the height to be automatic based on the width of the photo I upload. But if I enter 0 or auto, the images don’t display. What can I do?

Hi Calin,

Thank you again for your help.
Even though the lazy load is disabled in the theme panel and no data-lazyloaded or data-src is present in the HTML source (as you confirmed), when I run a PageSpeed test on an article — like this one: https://www.sport24h.it/laura-rogora-a-campitello-vince-la-prima-prova-di-coppa-europa-lead

I see that the featured image is still reported as lazy loaded. It appears with:
(see https://ibb.co/RTBmB3k8)

This image is also marked as the Largest Contentful Paint (LCP) element, and the loading time is above 3.5 seconds.

Could you please help me understand:

– Why is the image still being marked as lazy-loaded?
– Is this due to some remaining control by the theme, or LiteSpeed Cache?
– What would you recommend to optimize LCP, specifically for the featured image in articles, while using your theme?

Thanks again for your time and support,
Antonio

Calin,

Thank you for your reply.

I have already disabled the Lazy Load option from the Theme Panel as shown in your screenshot. However, even after doing this, the featured image on my articles still includes attributes like data-lazyloaded=”1″ and data-src, which suggest that lazy loading is still being applied by the theme’s internal JavaScript.

You can verify this directly here:
👉 https://www.sport24h.it/laura-rogora-a-campitello-vince-la-prima-prova-di-coppa-europa-lead/

I am trying to optimize LCP and need the featured image (which is the LCP element) to load immediately, without any lazy loading. Can you please clarify:

Where exactly the script applying data-lazyloaded=”1″ is coming from?

How I can fully disable lazy loading on the featured image only?

Thank you for your support.

Best regards,
Antonio

Someone can replay?
regards

Hi,
I have the some problem: 1304 options sizes: 1.017 KB.
I have decrease the backup limit, but the problem dont resolve.
The site: http://www.sport24h.it
regards

Hi Bettina
I fixed it by disabling litespeed; then I rewrote the code on the theme panel; in the last one I reactivated litespeed.
Now everything seems ok.

JQMIGRATE: Migrate is installed, version 3.4.1
219712072_103930691980500_8318029660069272118_n.jpg:1

Failed to load resource: the server responded with a status of 403 ()
profilepic/:1

Failed to load resource: the server responded with a status of 404 ()
jquery-migrate.min.js?ver=3.4.1:2 JQMIGRATE: Migrate is installed, version 3.4.1
complianz.min.js?ver=6.5.5:1 opt-in
card:1 Invalid ‘X-Frame-Options’ header encountered when loading ‘https://leggi.amazon.it/&#8217;: ” is not a recognized directive. The header will be ignored.
Error with Permissions-Policy header: Unrecognized feature: ‘ambient-light-sensor’.
Error with Permissions-Policy header: Unrecognized feature: ‘ambient-light-sensor’.
Error with Permissions-Policy-Report-Only header: Unrecognized feature: ‘document-domain’.
Error with Permissions-Policy-Report-Only header: Unrecognized feature: ‘document-domain’.
Error with Permissions-Policy header: Unrecognized feature: ‘ambient-light-sensor’.
Error with Permissions-Policy header: Unrecognized feature: ‘ambient-light-sensor’.
Error with Permissions-Policy-Report-Only header: Unrecognized feature: ‘document-domain’.
Error with Permissions-Policy-Report-Only header: Unrecognized feature: ‘document-domain’.

“Also, please chech the console…” I don’t know what you mean!
I try again, but che code isn’t saved.

I try to saved in Theme Panele, Analitics/JScodes, footer.

Can you help me?

To monitor site contacts for insertion of non-Google Adsense advertising

please respond!

I have the same problem with Open Graph: the photos of the posts on facebook and twitter are not published. Also facebook debugger give me error “og:image” and other tag.
Before I installed newspaper theme the open graph function of yoast seo was working. The uploaded photos are less than 300kb.
What should I do?