• Home
  • Get help
  • Ask a question
Last post 1 hour 39 min ago
Posts last week 118
Average response time last week 14 min
All time posts 70818
All time tickets 10917
All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#10838 – Google Speed: LCP warnings

Posted in ‘4SEO’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Thursday, 22 February 2024 15:56 UTC
ClaudioRomeo

The two pages shown in the image have a bad LCP score.
The pages are quite simple, but do you think that the presence of multiple modules called up on the pages and the use of Conditional Content conditions from Regular Labs (regarding the type of device or today's date) could cause the bad LCP score?
Can you suggest a resource for understanding the reasons for this unsatisfactory score?

Thursday, 22 February 2024 16:14 UTC
wb_weeblr

Hi

Can you suggest a resource for understanding the reasons for this unsatisfactory score?

The first resource is just your browser. Assuming you're using a Chrome derivative, the developer tools will give you information about what is the LCP element on that page and more details. Similarly, Google Page Speed will conduct an analysis about the page in question and give you information about what's causing the problem in their eyes.

The one important thing to understand about Core Web Vitals is that the score you see in Google Search Console and in 4SEO are real scores. They were measured when one or more visitors loaded a page from your site on their device.

A consequence is that if you look at the Page Speed analysis in your browser deve tools or at Google Page Speed, the LCP may be just fine there - because it's measured in different circumstances (device, network speed,...).

But what counts for SEO is not what you see in your browser or on Google Page Speed. What matters is the measurements taken with real visitors.

The information you get on  Google Page speed or in your dev tools is still useful though, because if it tells you that the LCP on this page is this particular image or

, then it's always the same and that's the one you want to understand and optimize.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Thursday, 22 February 2024 16:57 UTC
ClaudioRomeo

The first resource is just your browser. Assuming you're using a Chrome derivative

No. I work under Linux and use Firefox. Firefox also has analysis tools: I often use them to understand which CSS rules to work on. I will just have to learn how to use them to optimise web pages.

Thank you for suggesting Google PageSpeed. I just used it on https://example.it/ and noticed that the problems are mainly on the mobile version.
But I also saw that many improvements are recommended for computers as well.
I will try to find the best compromise between web page speed and my sanity...
Thanks again!

 

Thursday, 22 February 2024 17:27 UTC
wb_weeblr

Hi

No. I work under Linux and use Firefox. Firefox also has analysis tools: I often use them to understand which CSS rules to work on. I will just have to learn how to use them to optimise web pages.

Firefox is great but as far as I know, it does not provide indication on Core Web Vitals, so it's unlikely to help you here - aside from general optimization of the web page of course, which are always good.

So Google Page Speed is your best bet, or just use Chrome/Edge or similar for that purpose.

Even with 

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Sunday, 24 March 2024 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.