[Resolved] Unable to reduce LCP/FCP for mobile homepage

[Ying]

I did a lighthouse test for mobile performance, the most obvious thing is the Initial server responding time:
https://www.screencast.com/t/ipgzil9sZ

Here’s the documentation from Google on how to reduce server responding time:
https://developer.chrome.com/docs/lighthouse/performance/time-to-first-byte/?utm_source=lighthouse&utm_medium=devtools

This includes server speed, themes, plugins, and custom functions/scripts.

So try using fewer plugins, functions and scripts, and also check with your host to see if there’s any improvement can be done on their side.

[Robert]

Ying – one quick thing that came to mind:

I’m noticing this discrepancy between desktop and mobile exists on every page (of course). So, would it be fair to say that, to correct this issue across the board, I’d need to make this sort of individual adjustment to every page?

In other words, does GeneratePress not serve mobile-ready photos when needed, i.e., according to the device browsing the page? Or, is this a Ezoic/cache plug-in issue?

Thanks again – Robert

[Ying]

to correct this issue across the board, I’d need to make this sort of individual adjustment to every page?

The performance issue is mostly site-wide, there might be some differences between pages, it will depend on the different scripts/functions running on individual pages, and different layouts, pages with more elements like images will be slower to load natrually.

I’m noticing this discrepancy between desktop and mobile exists on every page (of course).

The lighthouse test for mobile is simulated in a slower internet/device performance environment, so in most cases to get a higher score for mobile is much more difficult than getting it for desktop.

In other words, does GeneratePress not serve mobile-ready photos when needed,

GP does not, as it is done by WordPress. But in your case, it’s a background image, the background image is a CSS property, and it’s not an HTML element, so the responsive image feature would not apply, and that is why GB pro offers the advanced background feature.

[Robert]

Ahh got it, got it. Sorry for bombarding you with another question!

Is it possible to turn it into a non-background image? I’m sure it’s due to the template I’ve configured the page with, but either way, even with GB Pro, I’m not sure it’d be time efficient for me to configure the resolution of every featured image I end up uploading.

[Ying]

No worries 🙂

It seems only the hero section is using the background image, the featured posts are using actual images.

FCP (First Contentful Paint) only calculates the content load within the viewport, which includes the hero section but does not include the featured posts section.

[Author]

Posts