Google Pagespeed Performance Loss - Possible issue with GatsbyCloud Plugin

Hi all, I’m going through the migration and have my current GatsbyCloud hosted project, on a temporary domain on Netlify, and when testing, I’m finding differences in headers, FOUT, that are pretty disappointing.

The current Gatsby Cloud site receives 98-100 performance scores, whereas Netlify it’s been 85-90.

    {
      resolve: `gatsby-plugin-gatsby-cloud`,
      options: {
        allPageHeaders: [
          "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload",
          "Cross-Origin-Embedder-Policy: credentialless",
          "Cross-Origin-Opener-Policy: same-origin",
        ],
        headers: {
          "/fonts/*": [
            "Cache-Control: public,max-age=31536000,s-maxage=31536000,immutable",
          ],
          "**/*.eot": [
            "Cache-Control: public,max-age=31536000,s-maxage=31536000,immutable",
          ],
          "**/*.svg": [
            "Cache-Control: public,max-age=31536000,s-maxage=31536000,immutable",
          ],
          "**/*.ttf": [
            "Cache-Control: public,max-age=31536000,s-maxage=31536000,immutable",
          ],
          "**/*.woff": [
            "Cache-Control: public,max-age=31536000,s-maxage=31536000,immutable",
          ],
          "**/*.woff2": [
            "Cache-Control: public,max-age=31536000,s-maxage=31536000,immutable",
          ],
        },
      },
    },

Specifically, when viewing the headers, I don’t see Cross-Origin-Embedder-Policy or Cross-Origin-Opener-Policy; I know this changes how connections occur, which could impact the loading of assets such as fonts and contribute to FOUT, but I’m not sure.

Hi @findcanary! We see that you have an open ticket in our helpdesk with our team, so we will continue the conversation over there. Thanks!