Google pagespeed shows low results?

Google pagespeed insights https://developers.google.com/speed/pagespeed/insights/ shows lowish results for Worpress websites on my apache server. When I look at the pages on my workstation they load very fast, one second about. Pagespeed shows several seconds for speed index. Is this because the server doing the pagespeed measurement is overseas and long delays increase load times?
Anyway, users want better scores on pagespeed. I have found Apache Pagespeed module, by Google. I found installation instructions for Ubuntu 20.04 on Howtoforge. Does the Pagespeed module installation go the same way on Debian Buster? Does it really help in getting better score?
Are there other or better ways to get better results in Google Pagespeed Insights?

 

I just took one of my wp site under ISPConfig 3.2.3 Ubuntu 20.04.2 Nginx web server. Seems like it is rated good so far.

 

Have you done something special to get full 100? I have static websites created with Hugo and they get 99. Never got full 100 yet.

 

I feel the pagespeed page index is misleading. It may be the page takes 6 seconds to load from overseas, but the page users are in Finland and here the page loads in about 1 second.
I tested also with tool.pingdom.com, it allows testing from Germany (closest to Finland from the available alternatives). It shows load time 788 ms, which seem about right comparing to what I see when using that pages. But it gives performance grade 76, which seems unfair when the page loads under 1 second.

 

Related question:
I tested on my test ISPConfig server enabling HTTP/2. Gives better score in Pagespeed. Is there any downside to using it? I recently updated my OS and ISPConfig to Debian 10 and ISPConfig 3.2.x, so I think all is up-to-date for HTTP/2.
https://www.howtoforge.com/how-to-enable-http-2-in-apache/

 

I mainly am using these. I am not using nginx pagespeed module.

 

I think @till is right, Wordpress plugins doing cache and optimization are better than Google Pagespeed module. Google Pagespeed module might help for static sites, but I get pagespeed score 99 for my static sites without any tricks so there is little need.
HTTP/2 on the other hand is a good idea. I followed the instructions in #7 and pagespeed score got better. Worth noting is (I think caused by php mode change) php_value is not allowed in .htaccess. Two websites had lines like these in .htaccess:

Code:

php_value upload_max_filesize 20m
php_value post_max_size 20m

The symptom is website no longer works, only shows error message and log has:

Code:

/web/.htaccess: Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration

 

In addition to checking the .htaccess files, before enabling HTTP/2 check for websites that ISPConfig panel has configured to use PHP: MOD-PHP. That mode writes php_admin_value lines to the .vhost configuration, and that breaks apache2 after switching to HTTP/2. So ISPConfig panel no longer works. Check

Code:

systemctl status apache2

to see which website is broken. Comment out the offending lines or something, then try starting apache and check status, until you have found all broken websites.