Skip to content
#

best-practices

Here are 1,248 public repositories matching this topic...

connorjclark
connorjclark commented Oct 6, 2021

https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/audits/image-size-responsive.js#L149

This is the only audit that saves a separate "elidedUrl" property. All other audits save the result of URL.elideDataURI to their url property. We should just set url to this elided value, and drop elidedUrl. Otherwise, data uir images failing this audit will make the LHR larger th

wstg
jespunya
jespunya commented Mar 13, 2020

What would you like added?
Common Platform Enumeration (CPE) is a structured naming scheme for information technology systems, software, and packages. Based upon the generic syntax for Uniform Resource Identifiers (URI), CPE includes a formal name format, a method for checking names against a system, and a description format for binding text and tests to a name.

The usage of CPE naming is

datree
myishay
myishay commented Oct 15, 2021

Is your feature request related to a problem? Please describe.
Installation script supports only x86_64 architecture. 386 and arm64 are not supported.

Describe the solution you'd like
Detect the machine's architecture and download the relevant release in the install script

Additional context
the relevant file that should be changed should be install.sh and `windows_install.p

jamieburchell
jamieburchell commented Oct 15, 2021

Google Lighthouse seems to complain that assets with a cache expiry of 30 days should be set with longer expiry times. I believe the thinking is if it's OK to cache something for 30, it's probably OK to cache something for a year. Certainly, when I changed my own config to expiry images and fonts from 30 days to 1 year, Lighthouse was happy.

Improve this page

Add a description, image, and links to the best-practices topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the best-practices topic, visit your repo's landing page and select "manage topics."

Learn more