Performance concerns: First Contentful Paint delays reported from google pagespeed

Hey, this might not be the right place to post this, and I have no idea if this has anything to do with Netlify! So, I put my website on lighthouse (PageSpeed Insights), and it’s complaining about First Contentful Paint (and First Meaningful Paint). I inserted the website name without any https or http or www. If I put in https://www. … then it’s not complaining at all. Anything I can do about this? Thanks, and sorry if this is the wrong place!

|(Initial: http://categorybooks.com/) | 0 ms|
|https://categorybooks.com | 630 ms|
|https://www.categorybooks.com | 480 ms|

hi there, can you tell us your netlify instance name?

Do you mean this: heuristic-heisenberg-eaf2d9 ? Sorry I’m not quite sure what you mean. :sweat_smile:

great, thanks. So when I pull up your page: https://heuristic-heisenberg-eaf2d9.netlify.com/

I did see it load instantaneously, it says the full pageload was completed in 1.3 seconds:

can you say a little more about what the problem is?

Like I said, I’m not sure if this has anything to do with Netlify!
Searching for categorybooks.com in https://developers.google.com/speed/pagespeed/insights/ gives me this:

I tried heuristic-heisenberg-eaf2d9.netlify.com and it didn’t seem to present the same problem. Thanks. :slight_smile:

You can certainly preload things if you want; you’d have to configure that. (perhaps using a preload custom header, see https://docs.netlify.com/routing/headers/#custom-headers for some more details)

Our service does make multiple redirects; that’s intended as we comply with the HSTS spec mentioned here: https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security#HSTS_mechanism_overview . They’ll only affect the first visit to the page after which the local browser knows to redirect automatically.

If you enter the https://www url into the google pagespeed insight the error «avoid multiple page redirects» is gone, like so:

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.categorybooks.com

As @fool mentioned, this are just normal or expected redirects.

2 Likes

@fool @ndalliard Okay, thanks! :slight_smile:

Due to this link of @fool

  1. Automatically turn any insecure links referencing the web application into secure links (e.g. http://example.com/some/page/ will be modified to https://example.com/some/page/ before accessing the server).

The “no redirection scenario” is
https://categorybooks.com (with https, without www)