WebsiteBaker Support (2.12.x) > General Help & Support
Core Web Vitals problem with FCP and LCP
svsanchez:
Hello everybody!
As you know, Google will start taking into account the Core Web Vitals (CWV) for ranking websites from May. I couldn't find any information about optimizing Website Baker for CWV, the only thread in the forum was in German but it didn't offer much advice (I don't speak German)
I am trying to get my main Website Baker site to the green zone, but I am failing miserably because the FCP and LCP are taking too long.
Here is an example test via Google's PageSpeed Insights:
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.deguate.com.gt%2Fguatemala%2Fagricultura.php&tab=mobile
The main problem seems to be the Server Response Time, which leads to the bad grades that I am getting, BUT the strange thing is that I am getting very good scores on THIS SAME server for my main site, which is NOT using WB. You can notice that when you click on any internal link on the site, it takes more than 6 seconds to "respond", which is not normal (when I upgraded to WB 2.10.x or 2.12.x I had to wait for up to 1 minute so I had to revert to 2.8.3).
So, I guess it is NOT a server issue, but something maybe something regarding the Database? (My site has more than 3000 pages).
Some of you had tried to help me with the slowliness of the pages when I upgraded to 2.10.x / 2.12.x but we were only able to accelerate the backend with a modified index.php file which only loads the current section instead of loading the whole site's tree.
svsanchez:
Hello again, I was able to get a 100 perfect score with one of my pages using the BLANK template:
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.deguate.com.gt%2Fguatemala%2Flimpieza%2Fpapel-higienico.php&tab=mobile
So, we can confirm that the problem is NOT the server NOR WebsiteBaker. There seems to be *something* in the template that is causing the site to respond so slowly at first.
svsanchez:
Ok, so it seems I found the main problem regarding the slow server response: as soon as I add the categories menu (SM2), the grades of the page go down to 91 / 92 with a server response time of almost 4 seconds before showing anything on the screen :-(
Is there a way to make the categories respond faster?
svsanchez:
One new test, with the main template but WITHOUT the SM2 menus and without the ads. I am getting grades 88 and above on Mobile and 98 and above on Desktop.
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.deguate.com.gt%2Fguatemala%2Flimpieza%2Fmantenimiento-de-limpieza.php&tab=mobile
It is normal for ads to degrade the performance of a page, but the menus shouldn't be causing this huge server response time problem.
ALSO, I am not being able to lower the LCP.
Any suggestion to fix these 2 things would be greatly appreciated!
hgs:
Actually, all measures are in the analysis.
Here is just an example, unfortunately in German, that should see you but then in English.
--- Quote --- Aufwand für Hauptthread minimieren 10,6 s
Versuchen Sie, die Zeit für das Parsen, Kompilieren und Ausführen von JavaScript zu reduzieren. Die Bereitstellung kleinerer JS-Nutzlasten kann dabei helfen. Weitere Informationen
Kategorie
Zeitaufwand
Script Evaluation
6.846 ms
Other
1.422 ms
Style & Layout
822 ms
Script Parsing & Compilation
742 ms
Parse HTML & CSS
361 ms
Garbage Collection
232 ms
Rendering
209 ms
--- End quote ---
--- Quote --- Aufwand für Hauptthread minimieren 10,6 s
Versuchen Sie, die Zeit für das Parsen, Kompilieren und Ausführen von JavaScript zu reduzieren. Die Bereitstellung kleinerer JS-Nutzlasten kann dabei helfen. Weitere Informationen
Kategorie
Zeitaufwand
Script Evaluation
6.846 ms
Other
1.422 ms
Style & Layout
822 ms
Script Parsing & Compilation
742 ms
Parse HTML & CSS
361 ms
Garbage Collection
232 ms
Rendering
209 ms
--- End quote ---
On these things, loading external scripts, WebsiteBaker has no influence.
That WebsiteBaker works, you have proven with the last post itself.
Navigation
[0] Message Index
[#] Next page
Go to full version