profile
viewpoint

GoogleChrome/lighthouse 20442

Automated auditing, performance metrics, and best practices for the web.

GoogleChrome/workbox 9345

📦 Workbox: JavaScript libraries for Progressive Web Apps

GoogleChrome/rendertron 4956

A Headless Chrome rendering solution

GoogleChrome/samples 4894

A repo containing samples tied to new functionality in each release of Google Chrome.

GoogleChrome/lighthouse-ci 3394

Automate running Lighthouse for every commit, viewing the changes, and preventing regressions

GoogleChrome/accessibility-developer-tools 2019

This is a library of accessibility-related testing and utility code.

GoogleChrome/dialog-polyfill 1955

Polyfill for the HTML dialog element

GoogleChrome/web-vitals 1649

Essential metrics for a healthy site.

GoogleChrome/web-vitals-extension 1574

A Chrome extension to measure essential metrics for a healthy site

startedGoogleChrome/lighthouse

started time in 29 minutes

issue commentGoogleChrome/lighthouse

Transfer size much bigger than Network Transferred Size or Resource Size on localhost

Thanks for filing @enmcewan!

We don't really have any information to be able to act on this as-is. The transfer size can be different in different environments for many valid reasons. Development environments are often very different from production ones w.r.t file size, common examples to check: compression differences, minification differences, geo differences, UA-sniffing, mobile v. desktop.

If you have a public URL where the number of bytes reported by Lighthouse does not match the number of bytes in DevTools while matching the same UA, DPR, and server then we'll happily take a look to fix it.

maybe the check is skipped below a certain threshold?

Yes, it is that might explain the difference there.

enmcewan

comment created time in an hour

startedGoogleChrome/chrome-app-samples

started time in 2 hours

startedGoogleChrome/lighthouse

started time in 2 hours

issue openedGoogleChrome/lighthouse

Transfer size much bigger than Network Transferred Size or Resource Size on localhost

What is the current behavior?

LH reports the following:

image

Dev Tools Network reports: image which matches the physical file size.

The Remove Unused CSS issue is not reported for this resource when the site is running on a web server so I don't know what the value is there. The Network Transfer size is down to ~3.5k (due to compression I assume), maybe the check is skipped below a certain threshold? Other resources are closer in Transfer Size to Network Transfer size but not the same on the web server

All this is confusing and time consuming, trying to reconcile the file sizes and check on the LH reported issue.

What is the expected behavior?

Transferred size should match the network transferred size on localhost.

  • Lighthouse version: 6.0.0

created time in 2 hours

startedGoogleChrome/lighthouse-ci

started time in 3 hours

startedGoogleChrome/web.dev

started time in 3 hours

issue openedGoogleChrome/web.dev

Add http authentication to secured folders by password

Please consider adding a user/password folder authentication, so ex. when no public the dev brunch folder to be able to measure!

created time in 3 hours

fork Ben-Moyer/lighthouse

Automated auditing, performance metrics, and best practices for the web.

https://developers.google.com/web/tools/lighthouse/

fork in 3 hours

issue closedGoogleChrome/lighthouse

Logo is reported as having an inappropriate size with an expected size of 97x97px, even though it renders as its actual size.

<!-- Before creating an issue please make sure you are using the latest version and have checked for duplicate issues. -->

<!-- Before creating an Accessibility issue please test that it is reproducible upstream with axe (https://www.deque.com/axe/) first and file the issue there if necessary. -->

Provide the steps to reproduce

  1. Run LH on https://www.aleksandrhovhannisyan.com/
  2. Note that the Best Practices score is 92.
  3. Note that one of the images is my logo, which is 32x32px. Lighthouse claims the expected size was 97x97px.

image

<!-- If your page is only local, or is liable to change, consider uploading a repro so that we can more easily debug the problem. Some services that will help are: https://jsbin.com/, https://surge.sh/ -->

What is the expected behavior?

The image's actual size is 32x32px, and its rendered size is 32x32px. I'm not sure why Lighthouse is expecting it to be 97x97px.

Environment Information

  • Affected Channels: DevTools
  • Lighthouse version: 6.0.0
  • Chrome version: 84.0.4147.105 (Official Build) (64-bit) (cohort: Stable)
  • Node.js version: N/A
  • Operating System: Windows 10 OS Version 1903 (Build 18362.778)

closed time in 4 hours

AleksandrHovhannisyan

issue commentGoogleChrome/lighthouse

Logo is reported as having an inappropriate size with an expected size of 97x97px, even though it renders as its actual size.

Thanks for filing @AleksandrHovhannisyan !

I'm not sure why Lighthouse is expecting it to be 97x97px.

DPR

Please see https://github.com/GoogleChrome/lighthouse/issues/11238, https://github.com/GoogleChrome/lighthouse/issues/10802#issuecomment-630233444, https://github.com/GoogleChrome/lighthouse/issues/11169#issuecomment-664693157

AleksandrHovhannisyan

comment created time in 4 hours

startedGoogleChrome/workbox

started time in 4 hours

issue openedGoogleChrome/lighthouse

Logo is reported as having an inappropriate size with an expected size of 97x97px, even though it renders as its actual size.

<!-- Before creating an issue please make sure you are using the latest version and have checked for duplicate issues. -->

<!-- Before creating an Accessibility issue please test that it is reproducible upstream with axe (https://www.deque.com/axe/) first and file the issue there if necessary. -->

Provide the steps to reproduce

  1. Run LH on https://www.aleksandrhovhannisyan.com/
  2. Note that the Best Practices score is 92.
  3. Note that one of the images is my logo, which is 32x32px. Lighthouse claims the expected size was 97x97px.

image

<!-- If your page is only local, or is liable to change, consider uploading a repro so that we can more easily debug the problem. Some services that will help are: https://jsbin.com/, https://surge.sh/ -->

What is the expected behavior?

The image's actual size is 32x32px, and its rendered size is 32x32px. I'm not sure why Lighthouse is expecting it to be 97x97px.

Environment Information

  • Affected Channels: DevTools
  • Lighthouse version: 6.0.0
  • Chrome version: 84.0.4147.105 (Official Build) (64-bit) (cohort: Stable)
  • Node.js version: N/A
  • Operating System: Windows 10 OS Version 1903 (Build 18362.778)

created time in 4 hours

pull request commentGoogleChrome/web.dev

Update index.md

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

<!-- ok -->

Allanbikundo

comment created time in 5 hours

pull request commentGoogleChrome/web.dev

Update index.md

@googlebot I signed it!

@googlebot I signed it!

Allanbikundo

comment created time in 5 hours

pull request commentGoogleChrome/web.dev

Update index.md

Deploy preview for web-dev-staging ready!

Built with commit 047394b245e28528560a7ac14578d44c45d748b6

https://deploy-preview-3667--web-dev-staging.netlify.app

Allanbikundo

comment created time in 5 hours

pull request commentGoogleChrome/web.dev

Update index.md

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

<!-- need_sender_cla -->

Allanbikundo

comment created time in 5 hours

PR opened GoogleChrome/web.dev

Update index.md

Creation of the thumbor config file and enabling AUTO_WEBP in the config

<!-- Add the DO NOT MERGE label if you don't want the web.dev team to merge this PR immediately after approving it. -->

Fixes #SOME_ISSUE_NUMBER

Changes proposed in this pull request:

+19 -0

0 comment

1 changed file

pr created time in 5 hours

fork Allanbikundo/web.dev

The frontend, backend, and content source code for web.dev

https://web.dev

fork in 5 hours

startedGoogleChrome/lighthouse

started time in 7 hours

startedGoogleChrome/web-vitals

started time in 7 hours

issue commentGoogleChrome/web.dev

The charts look weird in the print view of the homepage (with report)

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. To prevent this from happening, leave a comment.

pojda

comment created time in 11 hours

startedGoogleChrome/web-vitals

started time in 12 hours

CommitCommentEvent

startedGoogleChrome/custom-tabs-client

started time in 13 hours

startedGoogleChrome/lighthouse

started time in 13 hours

startedGoogleChrome/android-browser-helper

started time in 14 hours

startedGoogleChrome/lighthouse-ci

started time in 15 hours

more