Documenting results of a Lighthouse audit run on May 5th, 2021.
Mobile Performance Scores Low
I received an email notification from Google Search Console regarding a Redirect Error and ran an audit using Lighthouse in Chrome Developer Tools. The map on mobile scored very low on performance.
Email from Jason in response to audit results
I have not noticed any performance problems so take the metrics with a grain of salt. Also keep in mind that the welcome screen is the first thing users will see, and it should appear immediately. And even if they click out of it right away, that will still buy some time while the map loads. If they revisit the site later and do not show the welcome screen, much of the site should already be cached and therefore show up very quickly on subsequent visits.
The number of elements looks unsettling, and my guess is that it’s all because the table is loading in the background, along with the hundreds of elements inside it. Even though it doesn’t appear, it’s still happening in the background.
If that’s the culprit of that metric, it’s part of a much larger problem that’s always been on my radar but would take a very long time to fix, and it ties in closely with the broader goal of filtering and where/how I am pulling the data.
At any rate, serious effort and time would be required to address this but I wouldn’t mind if it was documented at least, so yes please create an issue and thanks for letting us know!
Documenting results of a Lighthouse audit run on May 5th, 2021.
Mobile Performance Scores Low
I received an email notification from Google Search Console regarding a Redirect Error and ran an audit using Lighthouse in Chrome Developer Tools. The map on mobile scored very low on performance.
Email from Jason in response to audit results
I have not noticed any performance problems so take the metrics with a grain of salt. Also keep in mind that the welcome screen is the first thing users will see, and it should appear immediately. And even if they click out of it right away, that will still buy some time while the map loads. If they revisit the site later and do not show the welcome screen, much of the site should already be cached and therefore show up very quickly on subsequent visits.
The number of elements looks unsettling, and my guess is that it’s all because the table is loading in the background, along with the hundreds of elements inside it. Even though it doesn’t appear, it’s still happening in the background.
If that’s the culprit of that metric, it’s part of a much larger problem that’s always been on my radar but would take a very long time to fix, and it ties in closely with the broader goal of filtering and where/how I am pulling the data.
At any rate, serious effort and time would be required to address this but I wouldn’t mind if it was documented at least, so yes please create an issue and thanks for letting us know!