Lighthouse

Run chrome lighthouse's audit from command line

↘锁芯ラ 提交于 2019-12-12 08:00:01
问题 I would like to write a script which run (from the chrome's binary) its lighthouse 's audit with a url given. I didn't manage to find how to do it, but since there is even a chrome extension doing I assume it should be feasible right ? 回答1: Google Lighthouse can be ran using the command line. To run it from the command line, you must first install: Google Chrome for Desktop Node.js v6 or later. To install the Lighthouse CLI, open a command line and type the following command: npm install -g

How to fix “Lighthouse returned error: NO_FCP.” when running Google Page Speed Test?

依然范特西╮ 提交于 2019-12-10 12:56:36
问题 I am running the Google Page Speed test for https://www.oceanluxe.com.au and get the following message: > Lighthouse returned error: NO_FCP. Something went wrong with the recording > the trace over your page load. Please run the Lighthouse again. (NO_FCP) > (NO_FCP) Can anyone help? Tried on different servers, tried various URLs as well http://oceanluxe.com.au 回答1: Try to do a test again in incognito mode. I had the same problem today and clearing the cookies and cached files helped in my

Progressive Web App “does not work offline” error

走远了吗. 提交于 2019-12-09 06:54:15
问题 I have written a progressive web app, following all available guides and examples, but for some reason when I click the Add to homescreen button, I keep getting this mysterious error: Site cannot be installed: does not work offline The major difference between my PWA and the examples, is that mine is running purely in a non-root path of the domain, so I have had to add extra paths to the configs in various places so the app is restricted to the non-root folder. The Google Lighthouse site

Manifest start_url is not cached by a Service Worker

南笙酒味 提交于 2019-12-06 19:21:21
问题 I'm using Lighthouse to audit my webapp. I'm working through the failures, but I'm stuck on this one: Failures: Manifest start_url is not cached by a Service Worker. In my manifest.json I have "start_url": "index.html", In my worker.js I am caching the following: let CACHE_NAME = 'my-site-cache-v1'; let urlsToCache = [ '/', '/scripts/app.js', '/index.html' ]; Which lines up with what I see in the Application tab in Chrome Dev tools: So... why is it telling me start_url is not cached? Here is

Manifest start_url is not cached by a Service Worker

孤者浪人 提交于 2019-12-05 00:54:08
I'm using Lighthouse to audit my webapp. I'm working through the failures, but I'm stuck on this one: Failures: Manifest start_url is not cached by a Service Worker. In my manifest.json I have "start_url": "index.html", In my worker.js I am caching the following: let CACHE_NAME = 'my-site-cache-v1'; let urlsToCache = [ '/', '/scripts/app.js', '/index.html' ]; Which lines up with what I see in the Application tab in Chrome Dev tools: So... why is it telling me start_url is not cached? Here is my full worker.js file: if ('serviceWorker' in navigator) { window.addEventListener('load', function()

Can Google.com and other heavily trafficked websites get a “fast” rank using Google's PSI v5 API?

本小妞迷上赌 提交于 2019-12-04 02:06:08
Does using the 90-percentile instead of median score when saying, "based on field data the 'page is slow'" make it impossible for heavily trafficked websites, such as google.com, from ever getting ranked "Fast"? This due to the long tail that occurs when monthly traffic is in the 10M+ ranges? Last time I checked (early Feb. 2018), the Desktop google.com received a 100 Lighthouse synthetic score, which is supposed to be interpreted as "there is little room for improvement," and yet, the page is ranked "slow" because the 90th percentile FCP is way over 3s. Will a page like nytimes.com ever be

Google Page Speed insights. Lighthouse measurement origin

隐身守侯 提交于 2019-12-03 18:18:09
问题 Google provides Speed index for given URL by doing a lighthouse measurement: https://developers.google.com/speed/pagespeed/insights The data differs a lot from my own measurement. Now my guess is for the mobile page test they use some 4G emulation on a machine located in the US while my testet webserver is located in europe. Any idea where to find information on the geo location they perform testing from ? 回答1: Lighthouse uses 'a slow 4G connection'. This choice influences the importance of

Objective-c HTTP Basic authentication

你说的曾经没有我的故事 提交于 2019-12-03 14:04:26
问题 How would i go about replicating this in objective-c curl -u rick@email.com:mypassword http://foo.lighthouseapp.com/projects.xml I've been playing around with the ASIHTTPRequest library but can't seem to figure it out, obviously sending my request like so returns an authentication error: -(void)submit:(id)sender { NSURL *url = [NSURL URLWithString:@"http://ldn.lighthouseapp.com/projects/63254-londonist-20/tickets.xml"]; ASIHTTPRequest *request = [ASIHTTPRequest requestWithURL:url]; [request

Progressive Web App “does not work offline” error

安稳与你 提交于 2019-12-03 08:37:43
I have written a progressive web app, following all available guides and examples, but for some reason when I click the Add to homescreen button, I keep getting this mysterious error: Site cannot be installed: does not work offline The major difference between my PWA and the examples, is that mine is running purely in a non-root path of the domain, so I have had to add extra paths to the configs in various places so the app is restricted to the non-root folder. The Google Lighthouse site doesn't help much either, giving a very similar message. Can anyone suggest what this error might be caused

Objective-c HTTP Basic authentication

泄露秘密 提交于 2019-12-03 04:11:23
How would i go about replicating this in objective-c curl -u rick@email.com:mypassword http://foo.lighthouseapp.com/projects.xml I've been playing around with the ASIHTTPRequest library but can't seem to figure it out, obviously sending my request like so returns an authentication error: -(void)submit:(id)sender { NSURL *url = [NSURL URLWithString:@"http://ldn.lighthouseapp.com/projects/63254-londonist-20/tickets.xml"]; ASIHTTPRequest *request = [ASIHTTPRequest requestWithURL:url]; [request startSynchronous]; NSError *error = [request error]; if (!error) { NSString *response = [request