{"id":102058,"date":"2025-02-21T19:50:59","date_gmt":"2025-02-21T19:50:59","guid":{"rendered":"https:\/\/peraltafinancing.com\/analytics\/audit-multiple-sites-with-lighthouse-and-write-results-to-bigquery\/"},"modified":"2025-02-21T19:50:59","modified_gmt":"2025-02-21T19:50:59","slug":"audit-multiple-sites-with-lighthouse-and-write-results-to-bigquery","status":"publish","type":"post","link":"https:\/\/fivemor.com\/?p=102058","title":{"rendered":"Audit Multiple Sites With Lighthouse And Write Results To BigQuery"},"content":{"rendered":"


\n<\/p>\n

\n

Google Cloud Platform<\/a> is very, very cool. It\u2019s a fully capable, enterprise-grade, scalable cloud ecosystem which lets even total novices get started with building their first cloud applications. I wrote a long guide for installing Snowplow on the GCP<\/a>, and you might want to read that if you want to see how you can build your own analytics tool using some nifty open-source modules.<\/p>\n

But this guide will not be about Snowplow<\/a>. Rather, it will tackle Google\u2019s own open-source performance audit tool: Lighthouse<\/a>.<\/p>\n

With this guide, you\u2019ll be able to build your own Google Cloud project, using Lighthouse to audit any number of sites you like, and write the results into storage and a BigQuery table<\/strong>!<\/p>\n

\n

<\/p>\n

\"Lighthouse\"\/<\/p>\n

<\/a><\/p>\n<\/div>\n

You can try Lighthouse in your Chrome browser right now. Just follow the instructions here<\/a> to see how you can enable the Audit<\/strong> tool in DevTools.<\/p>\n

One of the limitations of the DevTools feature is that you can only run it on one site at a time, and only through your web browser. I wanted to build something that lets me audit a whole bunch of sites, and automate it as well. For that reason, I wrote an extremely<\/strong> simple Node.js<\/a> app, multisite-lighthouse<\/a> which fulfils these requirements. Simply by editing a configuration file and then running the script, you can run an audit against multiple sites, and the results will be written in a local folder.<\/p>\n

So that was fun. But then I got a bit more ambitious. Would it be possible to run this app in a serverless<\/em> cloud environment, and have the results be written in a database or storage somewhere, where they can be queried and fetched at leisure?<\/p>\n

\n

<\/p>\n

\"BigQuery<\/p>\n

<\/a><\/p>\n<\/div>\n

Well, sure! In this guide, I\u2019ll walk you through how to run a Node.js application in a GCP Cloud Function<\/a>, which writes the results into a BigQuery<\/a> table, and stores the reports into a Cloud Storage<\/a> bucket. Oh, and it\u2019s practically free.<\/p>\n


\n X<\/span><\/p>\n

\n
\n The Simmer Newsletter<\/strong>\n <\/p>\n

\n Subscribe to the Simmer newsletter<\/a> to get the latest news and content from Simo Ahava into your email inbox!\n <\/p>\n

<\/span><\/p>\n

How it works<\/h2>\n

First, check out my mad Powerpoint-driven design skills:<\/p>\n

\n

<\/p>\n

<\/p>\n

<\/a><\/p>\n<\/div>\n

Let\u2019s step through what goes on here.<\/p>\n

    \n
  1. \n

    The Cloud Function<\/strong><\/a> is a piece of Node.js<\/strong><\/a> code running in the Google Cloud. It\u2019s called \u201cserverless\u201d because the setup is fully self-contained. The environment itself takes care of running the code and<\/strong> the infrastructure necessary to do so.<\/p>\n<\/li>\n

  2. \n

    The Cloud Function<\/strong> is triggered by a message pushed into a Pub\/Sub<\/strong><\/a> topic. Pub\/Sub is short for Publish\/Subscribe, which means you can publish<\/strong> messages into a topic, which will then alert any subscribers<\/strong> of that topic. In other words, it can be used as a simple real-time messaging queue, where published messages can trigger services within the Google Cloud.<\/p>\n<\/li>\n

  3. \n

    The message itself can be published by you manually<\/strong>, by using the Google Cloud SDK<\/a> in your local terminal, or by other applications which have been authorized to communicate with the topic. A nice use case would be to have your site\u2019s build pipeline trigger the audit as soon as the new release of the site has been deployed.<\/p>\n<\/li>\n

  4. \n

    The message can also be published by Cloud Scheduler<\/strong><\/a>, which is a Google Cloud service that lets you schedule certain actions such as the publishing of a Pub\/Sub message. You can set the scheduler to trigger your Cloud Function every night, or every week, or every month, for example.<\/p>\n<\/li>\n

  5. \n

    When the Cloud Function is triggered, it fires up an instance of the Google Chrome<\/strong> browser in headless mode, using a piece of software called Puppeteer<\/a>.<\/p>\n<\/li>\n

  6. \n

    The Lighthouse<\/a> audit tool is run in this browser instance, and it will perform the audit on any URLs you have defined in a special configuration file.<\/p>\n<\/li>\n

  7. \n

    Once the audit is complete, the results are written into Google Cloud Storage<\/strong><\/a>, which functions as a file archive in the cloud, allowing you to store and fetch items from it at will (and at low cost).<\/p>\n<\/li>\n

  8. \n

    The results are also written into a BigQuery<\/strong><\/a> table. BigQuery is a scalable data warehouse, where records are stored in table format (as opposed to a more traditional relational database). Due to its flat nature, it\u2019s fast, scalable, and extremely responsive. We don\u2019t need its full potential in this project, but having the data stored in BigQuery opens up opportunities in e.g. Google Data Studio<\/a> for visualization of the results.<\/p>\n<\/li>\n<\/ol>\n

    The cost<\/strong>? Next to nothing. With just one or two URLs you\u2019re facing practically zero cost<\/strong>. At most, it will be a handful of cents per month thanks to Google Cloud Storage.<\/p>\n

    Preparations<\/h2>\n

    To be able to follow this guide, you\u2019ll need to install some tools and create a Google Cloud Platform project.<\/p>\n

    Install command line tools<\/h3>\n

    First, install the following command line tools:<\/p>\n

      \n
    1. \n

      Node.js and npm<\/a>.<\/p>\n<\/li>\n

    2. \n

      Google Cloud SDK<\/a>.<\/p>\n<\/li>\n

    3. \n

      Git<\/a>.<\/p>\n<\/li>\n<\/ol>\n

      To verify you have these up and running, run the following commands in your terminal (example from OS X):<\/p>\n

      \n
      $ node -v\nv11.0.0\n\n$ npm -v\n6.4.1\n\n$ gcloud -v\nGoogle Cloud SDK 228.0.0\n\n$ git --version\ngit version 2.19.2<\/code><\/pre>\n<\/div>\n
      Naturally, you might see some other version numbers, and that\u2019s OK. Just try to work with recent releases.<\/p>\n
      Set up a new Google Cloud Platform project with Billing<\/h3>\n
      The other thing you\u2019ll need to do is create a GCP project<\/strong>, and you\u2019ll need to enable billing<\/strong> for this project. The things you build with this guide will most likely cost you absolutely nothing<\/strong>, or, at worst, just a handful of cents a month. But you still need to provide a credit card to enable some of the services we\u2019ll need.<\/p>\n
      To set up a new project, you can follow Step 1<\/a> and Step 2<\/a> in my Snowplow + GCP guide.<\/p>\n
      Once you\u2019ve created the project, make sure you copy its Project ID<\/strong> – you\u2019ll need it when walking through this guide.<\/p>\n
      \n
          <\/p>\n
          \"GCP<\/p>\n
          <\/a><\/p>\n<\/div>\n
      Once you\u2019ve got the command line tools running and the GCP project created, it\u2019s time to get to work!<\/p>\n
      Set things up in GCP<\/h2>\n
      We\u2019ll need to enable some services<\/strong> in your Google Cloud Platform project. Also, we\u2019ll need create a BigQuery dataset<\/strong>, a storage bucket<\/strong> in Cloud Storage, and we\u2019ll need to configure a Cloud Scheduler<\/strong> job to run the audits periodically.<\/p>\n
      Enable the services<\/h3>\n
      First, make sure you\u2019ve got the correct project selected while in your GCP console dashboard<\/a>.<\/p>\n
      \n
          <\/p>\n
          \"GCP<\/p>\n
          <\/a><\/p>\n<\/div>\n
      Then, go to https:\/\/console.cloud.google.com\/apis\/library\/cloudfunctions.googleapis.com<\/a> and click the blue ENABLE<\/strong> button to enable the Cloud Functions API<\/strong>.<\/p>\n
      \n
          <\/p>\n
          \"Enable<\/p>\n
          <\/a><\/p>\n<\/div>\n
      Once enabled, go to https:\/\/console.cloud.google.com\/apis\/library\/cloudscheduler.googleapis.com<\/a> and click the blue ENABLE<\/strong> button to enable the Cloud Scheduler API<\/strong>.<\/p>\n
      The other services we\u2019ll need (BigQuery API<\/strong>, Cloud Storage API<\/strong>, and Pub\/Sub API<\/strong>) are already enabled in your project.<\/p>\n
      Create the BigQuery dataset<\/h3>\n
      Now, browse to https:\/\/console.cloud.google.com\/bigquery<\/a>, and click your project ID in the list of availabe projects.<\/p>\n
      \n
          <\/p>\n
          \"Create<\/p>\n
          <\/a><\/p>\n<\/div>\n
      We need to create a dataset<\/strong> which will soon contain a table<\/strong> where the audit results will be loaded to.<\/p>\n
      Type lighthouse<\/code> as the dataset ID, like this:<\/p>\n
      \n
          <\/p>\n
          \"Dataset<\/p>\n
          <\/a><\/p>\n<\/div>\n
      You can set the location of the dataset to somewhere in your geographical vicinity, if you wish. Once done, click Create dataset<\/strong>.<\/p>\n
      Create the GCS bucket<\/h3>\n
      We\u2019ll need to create a bucket<\/strong> in Google Cloud Storage. You can think of it like a storage drive, where the bucket represents a specific root directory to which the audit reports will be written.<\/p>\n
      We\u2019ll also use the bucket to handle state<\/strong> in the Cloud Function. This is necessary to prevent unintentional retries from writing your data over and over again into BigQuery and storage.<\/p>\n
      Browse to https:\/\/console.cloud.google.com\/storage\/browser<\/a> and click Create bucket<\/strong>.<\/p>\n
      You\u2019ll need to edit some options.<\/p>\n
        \n
      1. \n
        Name<\/strong>: Give the bucket a name that\u2019s globally<\/em> unique. -lighthouse-reports<\/yourname><\/code> should work nicely. You\u2019ll need this name when configuring the application, so you might as well make note of it now.<\/p>\n<\/li>\n
      2. \n
        Default storage class<\/strong>: Choose an applicable storage class. The storage class determines how much it costs to store and query the data. You\u2019ll be doing a little bit of fetching and a little bit of storing, so the Regional option is typically a good one to go with.<\/p>\n<\/li>\n
      3. \n
        Location<\/strong>, choosing the location will impact costs and latency, so find one that suits you best. Honestly, the costs will be so low you might as well just take the one which is geographically closest to you.<\/p>\n<\/li>\n<\/ol>\n
        \n
            <\/p>\n
            \"Google<\/p>\n
            <\/a><\/p>\n<\/div>\n
        Once happy with the settings, click Create<\/strong>.<\/p>\n
        Set up the scheduled job<\/h3>\n
        Finally, browse to https:\/\/console.cloud.google.com\/cloudscheduler<\/a> and click Create job<\/strong>. We\u2019ll use the Cloud Scheduler to fire up our Cloud Function periodically.<\/p>\n
        In the first screen, you\u2019ll need to choose a region. You might as well choose one that\u2019s geographically close to you. Click Next<\/strong> when ready.<\/p>\n
        \n
            <\/p>\n
            \"Scheduler-region\"\/<\/p>\n
            <\/a><\/p>\n<\/div>\n
        Next, after some deliberation, you\u2019ll need to give your job a name. Just use something descriptive.<\/p>\n
        Then, you need to establish the frequency<\/strong> of the job. Cloud Scheduler uses UNIX\u2019 cron<\/code> format, which can be a bit of a mystery, but it does have a nice logic to it. You can read how it works here<\/a>, but here are some examples you can input into the field.<\/p>\n
          \n
        1. \n
          Every day at 04:00 AM (daily): 0 4 * * *<\/code><\/p>\n<\/li>\n
        2. \n
          Every Monday at 04:00 AM (weekly): 0 4 * * 1<\/code><\/p>\n<\/li>\n
        3. \n
          First day of every month at 04:00 AM (monthly): 0 4 1 * *<\/code><\/p>\n<\/li>\n<\/ol>\n
          Next, choose a Timezone<\/strong> with which the \u201c04:00 AM\u201d part is calculated.<\/p>\n
          Then, choose Pub\/Sub<\/strong> as the Target<\/strong> of the job.<\/p>\n
          Type launch-lighthouse<\/code> into the Topic<\/strong> field, and all<\/code> into the Payload<\/strong> field. Don\u2019t worry, these settings will become more apparent as we trod along.<\/p>\n
          In the end, the setup should look something like this:<\/p>\n
          \n
              <\/p>\n
              \"Cloud<\/p>\n
              <\/a><\/p>\n<\/div>\n
          Once ready, click Create<\/strong>.<\/p>\n
          Good job! That\u2019s it for the Google Cloud Platform<\/strong> preparations. Now we\u2019ll need to actually build the application<\/strong> itself.<\/p>\n
          Build and configure the application<\/h2>\n
          In this part of the guide, you\u2019ll install application source from my GitHub repo<\/strong>, update its configuration<\/strong>, and deploy it<\/strong> to GCP\u2019s Cloud Function environment.<\/p>\n
          Clone the repo and install dependencies<\/h3>\n
          Open your terminal (or other command line) application, browse to a directory you\u2019re comfortable to work with, and type the following command:<\/p>\n
          git clone https:\/\/github.com\/sahava\/multisite-lighthouse-gcp.git<\/code><\/p>\n
          This will download and install the source files from my GitHub repo<\/a> into the directory multisite-lighthouse-gcp\/<\/code> in the folder where you ran the command.<\/p>\n
          \n
              <\/p>\n
              \"Git<\/p>\n
              <\/a><\/p>\n<\/div>\n
          Next, type cd multisite-lighthouse-gcp<\/code> and press enter. You should now be in the folder with the source files.<\/p>\n
          Now, type npm install<\/code> to install the dependencies<\/strong> of the project:<\/p>\n
          \n
              <\/p>\n
              \"npm<\/p>\n
              <\/a><\/p>\n<\/div>\n
          This will take a while, depending on your internet connection. The dependencies include some heavy pieces of software (such as puppeteer<\/code>, which I use to launch a headless Google Chrome instance for the audits). Once it\u2019s done, you should see a note that a bunch of packages were successfully installed.<\/p>\n
          Modify the configuration file<\/h3>\n
          While in the multisite-lighthouse-gcp<\/code> directory, the next thing you\u2019ll need to do is edit the config.json<\/code> file. So open the file with the text editor of your choice. This is what the default configuration looks like:<\/p>\n
          \n
          {\n  \"source\"<\/span>: [\n    {\n      \"url\"<\/span>: \"https:\/\/www.google.com\/\"<\/span>,\n      \"id\"<\/span>: \"googlesearch\"<\/span>\n    },{\n      \"url\"<\/span>: \"https:\/\/www.ebay.com\/\"<\/span>,\n      \"id\"<\/span>: \"ebay\"<\/span>\n    }\n  ],\n  \"projectId\"<\/span>: \"multisite-lighthouse-gcp\"<\/span>,\n  \"pubsubTopicId\"<\/span>: \"launch-lighthouse\"<\/span>,\n  \"datasetId\"<\/span>: \"lighthouse\"<\/span>,\n  \"minTimeBetweenTriggers\"<\/span>: 300000<\/span>,\n  \"gcs\"<\/span>: {\n    \"bucketName\"<\/span>: \"lighthouse-reports\"<\/span>\n  },\n  \"lighthouseFlags\"<\/span>: {\n    \"output\"<\/span>: [\"html\"<\/span>, \"csv\"<\/span>],\n    \"emulatedFormFactor\"<\/span>: \"desktop\"<\/span>\n  }\n}<\/code><\/pre>\n<\/div>\n
          Please see the following list of fields and possible values, and edit the configuration file accordingly.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
          Field<\/th>\nValues<\/th>\nRequired<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
          source<\/code><\/td>\n{url, id}<\/td>\nYes<\/td>\nAn array of objects, each object representing one URL to audit. Type the full URL into the url<\/code> field, and give a unique, descriptive id<\/code> value into the respective field. For each additional URL you want to audit, add another object into the array.<\/td>\n<\/tr>\n
          projectId<\/code><\/td>\ntemp-test-simo<\/code><\/td>\nYes<\/td>\nThe Project ID<\/strong><\/a> of your Google Cloud Platform project.<\/td>\n<\/tr>\n
          pubsubTopicId<\/code><\/td>\nlaunch-lighthouse<\/code><\/td>\nYes<\/td>\nSet this to launch-lighthouse<\/code>. It\u2019s the name of the Pub\/Sub topic<\/strong> that will be used to trigger the audits.<\/td>\n<\/tr>\n
          datasetId<\/code><\/td>\nlighthouse<\/code><\/td>\nYes<\/td>\nThe Dataset ID<\/strong> of the dataset you just created<\/a> in BigQuery.<\/td>\n<\/tr>\n
          minTimeBetweenTriggers<\/code><\/td>\n300000<\/code><\/td>\nYes<\/td>\nThe minimum time in milliseconds to wait before a Pub\/Sub trigger can start the Cloud Function for any given ID. This is to add some idempotency<\/em> to the function (more on this below).<\/td>\n<\/tr>\n
          gcs<\/code><\/td>\n{bucketName}<\/td>\nYes<\/td>\nThe name of the Google Cloud Storage bucket you created earlier<\/a>.<\/td>\n<\/tr>\n
          lighthouseFlags<\/code><\/td>\nSee here<\/a>.<\/td>\nNo<\/td>\nIf you want to store the reports in Google Cloud Storage, set the output<\/code> field to have an array of the formats you want to write the reports in. Available values are \"csv\"<\/code>, \"json\"<\/code>, and \"html\"<\/code>. For each value in this array, a report will be written for every URL audited.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
          The only optional field is lighthouseFlags<\/code>. If you don\u2019t set lighthouseFlags.output<\/code> to an array of available filetypes, no reports will be written to Google Cloud Storage. The other field provided by default is emulatedFormFactor<\/code>, which specifies that the performance audit should emulate a desktop browser.<\/p>\n
          The minTimeBetweenTriggers<\/code> flag is used to add a wait time before you can audit any given ID again. The Cloud Functions service doesn\u2019t guarantee that a function is run just once per trigger. This means that any code that\u2019s run should aim to be idempotent<\/em>; that is, multiple executions of the code in a short amount of time should not result in additional state changes (e.g. BigQuery loads).<\/p>\n
          I ended up using a simple stateful mechanism in Google Cloud Storage. A file named states.json<\/code> is written into the root of the GCS bucket, and this contains timestamps for when each trigger last activated its respective event. If this activation was less than 300 seconds ago (or whatever you specify in the configuration file), the function will abort.<\/p>\n
          Once done with the configuration, save the changes you made.<\/p>\n
          Deploy the function and test<\/h2>\n
          You\u2019re almost done! Now you\u2019ll need to just deploy<\/strong> the function, and then run a simple test<\/strong>.<\/p>\n
          The Cloud Function itself is the launchLighthouse()<\/code> method you can find if you browse the source code of index.js<\/code>. This function is what your Pub\/Sub trigger will launch when your Cloud Scheduler job goes off, or when you manually instruct the trigger to fire.<\/p>\n
          The Cloud Function will run in Google Cloud\u2019s serverless environment, launching instances of headless Google Chrome to perform the audits on the URLs you provide in the configuration file. The results will then be written into a BigQuery table, as well as stored into the GCS bucket if you so wish.<\/p>\n
          Deploy the Cloud Function<\/h3>\n
          While in the multisite-lighthouse-gcp<\/code> folder, type the following command:<\/p>\n
          gcloud auth login<\/code><\/p>\n
          This should open up a browser window where you need to enter your Google ID credentials. Make sure you log in with the same Google ID you use to manage your Google Cloud Platform project with<\/strong>! You\u2019ll see that Google Cloud SDK wants to access a bunch of things in your name, so click Allow<\/strong> to let it do just that.<\/p>\n
          It\u2019s Google – what evil could they do?<\/p>\n
          If successful, you should see this screen:<\/p>\n
          \n
              <\/p>\n
              \"gcloud<\/p>\n
              <\/a><\/p>\n<\/div>\n
          Now, open your terminal window again, and type the following command in the multisite-lighthouse-gcp<\/code> folder:<\/p>\n
          gcloud config set project <\/code><\/p>\n
          Type your GCP Project ID<\/strong> in lieu of <\/code>, and press enter.<\/p>\n
          \n
              <\/p>\n
              \"Set<\/p>\n
              <\/a><\/p>\n<\/div>\n
          Now that you\u2019ve authenticated against Google Cloud, and now that you\u2019ve switched the project to your GCP project, it\u2019s time to finally deploy the function with (type it all in one line):<\/p>\n
          gcloud functions deploy launchLighthouse --trigger-topic launch-lighthouse --memory 2048 --timeout 540 --runtime=nodejs8<\/code><\/p>\n
          If you want to run the function in a specific region, you can add --region=<\/code>, e.g. --region=europe-west1<\/code> to the command.<\/p>\n
          It will take a minute or two for the function to be deployed to the cloud. Once done, you should see this as a result:<\/p>\n
          \n
              <\/p>\n
              \"Function<\/p>\n
              <\/a><\/p>\n<\/div>\n
          The deploy should fail in an error if you have mistakes in the configuration file config.json<\/code>, so make sure you follow the instructions above<\/a> for how to configure the function.<\/p>\n
          The initial deployment creates the launch-lighthouse<\/code> Pub\/Sub topic and subscriptions<\/a> automatically.<\/p>\n
          So now that the Pub\/Sub topic has been created, you can actually test the whole thing.<\/p>\n
          Test with Pub\/Sub<\/h3>\n
          The Cloud Scheduler will send the message all<\/code> to the Pub\/Sub topic launch-lighthouse<\/code> using the schedule you defined earlier. The topic all<\/code> will, in turn, trigger the Cloud Function you just deployed as many times as it takes to audit all the URLs in the source<\/code> field of the configuration.<\/p>\n
          You can test this in two ways.<\/p>\n
            \n
          1. \n
            You can browse to https:\/\/console.cloud.google.com\/cloudscheduler<\/a> and click Run now<\/strong> next to the schedule job.<\/p>\n<\/li>\n
          2. \n
            You can use the command line to publish the all<\/code> message.<\/p>\n<\/li>\n<\/ol>\n
            Since the first is so easy, I\u2019ll show you how to do the second.<\/p>\n
            Open the terminal, and make sure you have your Google Cloud Platform set with:<\/p>\n
            gcloud config set project <\/code><\/p>\n
            Just remember to replace <\/code> with your actual project ID.<\/p>\n
            Now, run:<\/p>\n
            gcloud pubsub topics publish launch-lighthouse --message all<\/code><\/p>\n
            \n
                <\/p>\n
                \"Pub\/Sub<\/p>\n
                <\/a><\/p>\n<\/div>\n
            You should see a messageIds<\/code> response – that means the message was published successfully.<\/p>\n
            Check logs<\/h3>\n
            Now, browse to https:\/\/console.cloud.google.com\/functions\/list<\/a>, where you should see details about your Cloud Function, hopefully with a green checkmark next to its name.<\/p>\n
            Click the action menu at the end of the row, and choose View logs<\/strong>.<\/p>\n
            \n
                <\/p>\n
                \"View<\/p>\n
                <\/a><\/p>\n<\/div>\n
            You\u2019ll see a bunch of log results here. Here are the entries you should see (in approximately, but not definitely, this order):<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
            Message<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
            Function execution started<\/td>\nThe Cloud Function starts. If you sent the message all<\/code>, it now sends a new<\/strong> Pub\/Sub message for all the IDs in your configuration file, thus starting new Cloud Functions by itself (one for each source<\/code> entry in the config).<\/td>\n<\/tr>\n
            {id}: Sending init PubSub message<\/td>\nThis is the initialization message for source ID {id}.<\/td>\n<\/tr>\n
            {id}: Init PubSub message sent<\/td>\nThe initialization message was sent successfully.<\/td>\n<\/tr>\n
            Function execution took N ms, finished with status: \u2018ok\u2019<\/td>\nThe Cloud Function triggered with all<\/code> has now completed its task.<\/td>\n<\/tr>\n
            Function execution started<\/td>\nThe Cloud Function triggered by the initialization message now starts.<\/td>\n<\/tr>\n
            {id}: Received message to start with URL {url}<\/td>\nMessage to start audit received.<\/td>\n<\/tr>\n
            {id}: Starting browser for {url}<\/td>\nA headless browser is started for the audit.<\/td>\n<\/tr>\n
            {id}: Browser started for {url}<\/td>\nThe browser startup is successful.<\/td>\n<\/tr>\n
            {id}: Starting lighthouse for {url}<\/td>\nBeginning the actual audit.<\/td>\n<\/tr>\n
            {id}: Lighthouse done for {url}<\/td>\nLighthouse audit complete.<\/td>\n<\/tr>\n
            {id}: Browser closed for {url}<\/td>\nBrowser instance shut down.<\/td>\n<\/tr>\n
            {id}: Writing {output} report to bucket {bucketName}<\/td>\nIf you\u2019ve defined the output<\/code> Lighthouse flag, then a report for each filetype listed in output<\/code> will now be written into your GCS bucket.<\/td>\n<\/tr>\n
            {id}: Writing log to bucket {bucketName}<\/td>\nThe full log of the audit is written to storage, too.<\/td>\n<\/tr>\n
            {id}: BigQuery job with ID {UUID} starting for {url}<\/td>\nThe BigQuery job starts and signals the end of the Cloud Function.<\/td>\n<\/tr>\n
            Function execution took N ms, finished with status \u2018ok\u2019<\/td>\nFunction complete.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
            \n
                <\/p>\n
                \"Sample<\/p>\n
                <\/a><\/p>\n<\/div>\n
            If you had multiple URLs defined in the source<\/code> of the configuration file, then you\u2019ll see parallel entries for all the URLs. Each URL is treated in its own Cloud Function, so there will be a lot of overlap in the logs.<\/p>\n
            If you see permission errors then they are almost certainly because you\u2019ve either forgotten to enable the required services, or because you haven\u2019t filled in the configuration file<\/a> correctly.<\/p>\n
            Check BigQuery<\/h3>\n
            Now, browse to https:\/\/console.cloud.google.com\/bigquery<\/a>. Here, click open your project in the left navigation, and choose the dataset you created. You should see a new table under it, named reports<\/code>. Click it.<\/p>\n
            In the main console, you should now see a bunch of column definitions. Above those definitions is the link titled Preview<\/strong>, so go ahead and click it. This will \u201cPreview\u201d the BigQuery data stored in the data, and thus not cost you a penny.<\/p>\n
            \n
                <\/p>\n
                \"BigQuery<\/p>\n
                <\/a><\/p>\n<\/div>\n
            Feel free to scroll around the columns.<\/p>\n
            Do note that the BigQuery schema only contains those audits that have a \u201cweight\u201d in determining the total score<\/strong>. I did this purely out of convenience. I might update the schema at some point to simply contain all the audit fields, but this made more sense to start with.<\/p>\n
            Check Cloud Storage<\/h3>\n
            Browse to https:\/\/console.cloud.google.com\/storage\/browser<\/a> and click the bucket name you created earlier. You might see some .appspot.com<\/code> buckets there, too. Don\u2019t worry – they were created automatically when you deployed your Cloud Function.<\/p>\n
            You should now see new folders within the bucket – each named after an id<\/code> value in your configuration file\u2019s source<\/code> array. You\u2019ll also see the states.json<\/code> file, which makes sure your function only runs when it\u2019s supposed to.<\/p>\n
            \n
                <\/p>\n
                \"Folders<\/p>\n
                <\/a><\/p>\n<\/div>\n
            Click one of the folders to see the contents.<\/p>\n
            If you defined an output<\/code> array in the Lighthouse flags of the configuration file, you will now see a file prefixed with report_<\/code> for each file type you added to the array. Remember, there were three possible reports Lighthouse can provide you: CSV, HTML, and JSON.<\/p>\n
            \n
                <\/p>\n
                \"Storage<\/p>\n
                <\/a><\/p>\n<\/div>\n
            You\u2019ll also see a JSON file prefixed with log_<\/code>, which will contain the full audit object for you to peruse.<\/p>\n
            Feel free to download the files and explore them. The HTML report is especially interesting (and visually pleasing) to read.<\/p>\n
            Things to note<\/h2>\n
            Cloud Scheduler<\/h3>\n
            Don\u2019t forget that you have a Cloud Scheduler<\/strong> running! Periodically, it will push the all<\/code> message into your Pub\/Sub topic, thus auditing each URL in your source<\/code> list, writing the results into BigQuery, and storing the logs in Cloud Storage.<\/p>\n
            Manually trigger the audit<\/h3>\n
            You can always trigger the audit manually with<\/p>\n
            gcloud pubsub topics publish launch-lighthouse --message all<\/code><\/p>\n
            or, if you want to trigger an audit for a specific ID only, the command is<\/p>\n
            gcloud pubsub topics publish launch-lighthouse --message <\/code><\/p>\n
            where <\/code> is the ID of the URL you set in the source<\/code> array of the configuration file.<\/p>\n
            Cloud Functions don\u2019t have the best performance<\/h3>\n
            Unfortunately, running the headless browser in the Cloud Function is not the most efficient thing in the world. In fact, the Performance<\/strong> report (which is, for many, the most interesting one), will most likely under-report the load times quite severely.<\/p>\n
            There\u2019s not much to do about this currently. Cloud Functions simply do not have the CPU power required to perform complex or expensive tasks like this.<\/p>\n
            This has been identified by the developers (see here<\/a>), and it\u2019s possible that in the near future either Cloud Functions, Puppeteer, or Google Chrome will enable the processes to run smoother and faster.<\/p>\n
            Updating the configuration file is a bit annoying<\/h3>\n
            Due to how the configuration file has been bundled with the Cloud Function itself, any update to the configuration file requires you to redeploy<\/strong> the Cloud Function itself. This is annoying, since deployment always takes a couple of minutes.<\/p>\n
            I\u2019m probably going to update the application so that the configuration file is stored in a Google Cloud Storage bucket. That way when you want to update the file, all you need to do is upload it to the bucket using the Google Cloud Console user interface. And that\u2019s really fast.<\/p>\n
            Other ideas<\/h3>\n
            You can follow the GitHub project<\/a> to see where things are heading. Especially the Issues<\/a> page should be of interest, since it\u2019s essentially a to-do list for me.<\/p>\n
            Final thoughts<\/h2>\n
            This was a fun exercise, and I hope you managed to complete it following the guide above. If not, please let me know in the comments where you had trouble.<\/p>\n
            I\u2019m not too happy with the fact that Chrome is just too slow when run through a Cloud Function. It\u2019s possible that the whole thing is quite useless until the browser\u2019s performance in the sandbox is improved. I might have to add the option of using an AppEngine or Kubernetes Engine instance instead. This way you could scale the environment as much as you like to improve the accuracy of the performance audit. Naturally, this will incur some costs not present in the current setup.<\/p>\n
            On the other hand, I love the fact that the data is being collected in BigQuery, since I can create a nice dashboard with Data Studio that shows the performance progress of the URLs I\u2019ve selected for auditing.<\/p>\n
            Cloud Functions themselves are simply wonderful. Total game-changers. Running serverless applications with almost no cost at all, and triggering them in different ways (HTTP requests, Pub\/Sub triggers) has huge potential for the future. Thanks to some background service magic, it\u2019s so refreshing not having to worry about authentication and access control levels – the Cloud Function has all the required access levels for performing a wide variety of tasks.<\/p>\n
            Check the Cloud Function documentation for inspiration: https:\/\/cloud.google.com\/functions\/docs\/tutorials\/<\/a>.<\/p>\n
            As always, please let me know in comments if you have questions about this setup, or if you have suggestions for improvement.<\/p>\n<\/p><\/div>\n\n","protected":false},"excerpt":{"rendered":"
            Google Cloud Platform is very, very cool. It\u2019s a fully capable, enterprise-grade, scalable cloud ecosystem which lets even total novices get started with building their first cloud applications. I wrote a long guide for installing Snowplow on the GCP, and you might want to read that if you want to see how you can build […]<\/p>\n","protected":false},"author":1,"featured_media":102059,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12033],"tags":[16404,28608,8343,1025,4955,11405,4012],"dealstore":[],"offerexpiration":[],"class_list":["post-102058","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analytics","tag-audit","tag-bigquery","tag-lighthouse","tag-multiple","tag-results","tag-sites","tag-write"],"yoast_head":"\nAudit Multiple Sites With Lighthouse And Write Results To BigQuery - Som2ny Network<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fivemor.com\/?p=102058\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Audit Multiple Sites With Lighthouse And Write Results To BigQuery - Som2ny Network\" \/>\n<meta property=\"og:description\" content=\"Google Cloud Platform is very, very cool. It\u2019s a fully capable, enterprise-grade, scalable cloud ecosystem which lets even total novices get started with building their first cloud applications. I wrote a long guide for installing Snowplow on the GCP, and you might want to read that if you want to see how you can build […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fivemor.com\/?p=102058\" \/>\n<meta property=\"og:site_name\" content=\"Som2ny Network\" \/>\n<meta property=\"article:published_time\" content=\"2025-02-21T19:50:59+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1413\" \/>\n\t<meta property=\"og:image:height\" content=\"462\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"21 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fivemor.com\/?p=102058#article\",\"isPartOf\":{\"@id\":\"https:\/\/fivemor.com\/?p=102058\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\/\/fivemor.com\/#\/schema\/person\/b85e3c3dc0e1daea076524dc8810c371\"},\"headline\":\"Audit Multiple Sites With Lighthouse And Write Results To BigQuery\",\"datePublished\":\"2025-02-21T19:50:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fivemor.com\/?p=102058\"},\"wordCount\":4036,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fivemor.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/fivemor.com\/?p=102058#primaryimage\"},\"thumbnailUrl\":\"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg\",\"keywords\":[\"Audit\",\"BigQuery\",\"Lighthouse\",\"Multiple\",\"Results\",\"Sites\",\"Write\"],\"articleSection\":[\"Analytics\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fivemor.com\/?p=102058#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fivemor.com\/?p=102058\",\"url\":\"https:\/\/fivemor.com\/?p=102058\",\"name\":\"Audit Multiple Sites With Lighthouse And Write Results To BigQuery - Som2ny Network\",\"isPartOf\":{\"@id\":\"https:\/\/fivemor.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/fivemor.com\/?p=102058#primaryimage\"},\"image\":{\"@id\":\"https:\/\/fivemor.com\/?p=102058#primaryimage\"},\"thumbnailUrl\":\"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg\",\"datePublished\":\"2025-02-21T19:50:59+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fivemor.com\/?p=102058#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fivemor.com\/?p=102058\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/fivemor.com\/?p=102058#primaryimage\",\"url\":\"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg\",\"contentUrl\":\"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg\",\"width\":1413,\"height\":462},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fivemor.com\/?p=102058#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/fivemor.com\/?bp_activities=1\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Audit Multiple Sites With Lighthouse And Write Results To BigQuery\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fivemor.com\/#website\",\"url\":\"https:\/\/fivemor.com\/\",\"name\":\"Som2ny Network\",\"description\":\"Daily Deals\",\"publisher\":{\"@id\":\"https:\/\/fivemor.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fivemor.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/fivemor.com\/#organization\",\"name\":\"Som2ny Network\",\"url\":\"https:\/\/fivemor.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/fivemor.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/fivemor.com\/wp-content\/uploads\/2026\/07\/4a0953c4-logo-300x86-1.png\",\"contentUrl\":\"https:\/\/fivemor.com\/wp-content\/uploads\/2026\/07\/4a0953c4-logo-300x86-1.png\",\"width\":300,\"height\":86,\"caption\":\"Som2ny Network\"},\"image\":{\"@id\":\"https:\/\/fivemor.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/fivemor.com\/#\/schema\/person\/b85e3c3dc0e1daea076524dc8810c371\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/fivemor.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/729ae85bf62b9917e93538db2f2688ca?s=96&r=g&default=https%3A%2F%2Ffivemor.com%2Fwp-content%2Fplugins%2Fbuddypress-first-letter-avatar%2Fimages%2Fdefault%2F96%2Flatin_a.png\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/729ae85bf62b9917e93538db2f2688ca?s=96&r=g&default=https%3A%2F%2Ffivemor.com%2Fwp-content%2Fplugins%2Fbuddypress-first-letter-avatar%2Fimages%2Fdefault%2F96%2Flatin_a.png\",\"caption\":\"admin\"},\"sameAs\":[\"https:\/\/fivemor.com\"],\"url\":\"https:\/\/fivemor.com\/?author=1\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Audit Multiple Sites With Lighthouse And Write Results To BigQuery - Som2ny Network","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fivemor.com\/?p=102058","og_locale":"en_US","og_type":"article","og_title":"Audit Multiple Sites With Lighthouse And Write Results To BigQuery - Som2ny Network","og_description":"Google Cloud Platform is very, very cool. It\u2019s a fully capable, enterprise-grade, scalable cloud ecosystem which lets even total novices get started with building their first cloud applications. I wrote a long guide for installing Snowplow on the GCP, and you might want to read that if you want to see how you can build […]","og_url":"https:\/\/fivemor.com\/?p=102058","og_site_name":"Som2ny Network","article_published_time":"2025-02-21T19:50:59+00:00","og_image":[{"width":1413,"height":462,"url":"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg","type":"image\/jpeg"}],"author":"admin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"admin","Est. reading time":"21 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fivemor.com\/?p=102058#article","isPartOf":{"@id":"https:\/\/fivemor.com\/?p=102058"},"author":{"name":"admin","@id":"https:\/\/fivemor.com\/#\/schema\/person\/b85e3c3dc0e1daea076524dc8810c371"},"headline":"Audit Multiple Sites With Lighthouse And Write Results To BigQuery","datePublished":"2025-02-21T19:50:59+00:00","mainEntityOfPage":{"@id":"https:\/\/fivemor.com\/?p=102058"},"wordCount":4036,"commentCount":0,"publisher":{"@id":"https:\/\/fivemor.com\/#organization"},"image":{"@id":"https:\/\/fivemor.com\/?p=102058#primaryimage"},"thumbnailUrl":"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg","keywords":["Audit","BigQuery","Lighthouse","Multiple","Results","Sites","Write"],"articleSection":["Analytics"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fivemor.com\/?p=102058#respond"]}]},{"@type":"WebPage","@id":"https:\/\/fivemor.com\/?p=102058","url":"https:\/\/fivemor.com\/?p=102058","name":"Audit Multiple Sites With Lighthouse And Write Results To BigQuery - Som2ny Network","isPartOf":{"@id":"https:\/\/fivemor.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/fivemor.com\/?p=102058#primaryimage"},"image":{"@id":"https:\/\/fivemor.com\/?p=102058#primaryimage"},"thumbnailUrl":"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg","datePublished":"2025-02-21T19:50:59+00:00","breadcrumb":{"@id":"https:\/\/fivemor.com\/?p=102058#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fivemor.com\/?p=102058"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fivemor.com\/?p=102058#primaryimage","url":"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg","contentUrl":"https:\/\/fivemor.com\/wp-content\/uploads\/2025\/02\/lighthouse.jpg","width":1413,"height":462},{"@type":"BreadcrumbList","@id":"https:\/\/fivemor.com\/?p=102058#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/fivemor.com\/?bp_activities=1"},{"@type":"ListItem","position":2,"name":"Audit Multiple Sites With Lighthouse And Write Results To BigQuery"}]},{"@type":"WebSite","@id":"https:\/\/fivemor.com\/#website","url":"https:\/\/fivemor.com\/","name":"Som2ny Network","description":"Daily Deals","publisher":{"@id":"https:\/\/fivemor.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fivemor.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/fivemor.com\/#organization","name":"Som2ny Network","url":"https:\/\/fivemor.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fivemor.com\/#\/schema\/logo\/image\/","url":"https:\/\/fivemor.com\/wp-content\/uploads\/2026\/07\/4a0953c4-logo-300x86-1.png","contentUrl":"https:\/\/fivemor.com\/wp-content\/uploads\/2026\/07\/4a0953c4-logo-300x86-1.png","width":300,"height":86,"caption":"Som2ny Network"},"image":{"@id":"https:\/\/fivemor.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/fivemor.com\/#\/schema\/person\/b85e3c3dc0e1daea076524dc8810c371","name":"admin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fivemor.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/729ae85bf62b9917e93538db2f2688ca?s=96&r=g&default=https%3A%2F%2Ffivemor.com%2Fwp-content%2Fplugins%2Fbuddypress-first-letter-avatar%2Fimages%2Fdefault%2F96%2Flatin_a.png","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/729ae85bf62b9917e93538db2f2688ca?s=96&r=g&default=https%3A%2F%2Ffivemor.com%2Fwp-content%2Fplugins%2Fbuddypress-first-letter-avatar%2Fimages%2Fdefault%2F96%2Flatin_a.png","caption":"admin"},"sameAs":["https:\/\/fivemor.com"],"url":"https:\/\/fivemor.com\/?author=1"}]}},"_links":{"self":[{"href":"https:\/\/fivemor.com\/index.php?rest_route=\/wp\/v2\/posts\/102058","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fivemor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fivemor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=102058"}],"version-history":[{"count":0,"href":"https:\/\/fivemor.com\/index.php?rest_route=\/wp\/v2\/posts\/102058\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=\/wp\/v2\/media\/102059"}],"wp:attachment":[{"href":"https:\/\/fivemor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=102058"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=102058"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=102058"},{"taxonomy":"dealstore","embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fdealstore&post=102058"},{"taxonomy":"offerexpiration","embeddable":true,"href":"https:\/\/fivemor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fofferexpiration&post=102058"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}