Andy Thomason is a Senior Programmer at Genomics PLC. He has been witing graphics systems, games and compilers since the '70s and specialises in code performance.
SELECT | |
form_factor.name AS form_factor, | |
cls.start, | |
ROUND(SUM(cls.density), 4) AS density | |
FROM | |
`chrome-ux-report.all.201905`, | |
UNNEST(experimental.cumulative_layout_shift.histogram.bin) AS cls | |
WHERE | |
origin = 'https://www.nytimes.com' | |
GROUP BY |
In this article, I would like to share three features of PageSpeed Insights (PSI), that is not easy to find in the official documentation. I discovered them while hacking on the Lighthouse plugin and integrating PSI to Treo.sh.
For a context, PSI is a simple yet powerful API by Google, that audits your page using Lighthouse and provides real-world users' data from Chrome UX Report (CrUX).
By default, PSI API returns only performance category. It's possible to pass ?category
argument multiple times and get a report with many Lighthouse categories using one request (available categories: performance
, accessibility
, best-practices
, seo
, pwa
).
curl -i "https://www.googleapis.com/pagespe
There's the pervarsive notion that all JS is created equal and that there's only minor and easily detectable differences between the various file formats used to author JavaScript. This is correct, from a certain point of view.
For many people writing JavaScript that gets passed into build tools,
As we were preparing Playwright 1.1.0, I learned quite a lot about Web Proxies. Below is the summary of my findings.
There are two groups of proxies that drive internet:
const minute = 60; | |
const hour = minute * 60; | |
const day = hour * 24; | |
const week = day * 7; | |
const month = day * 30; | |
const year = day * 365; | |
/** | |
* Convert a date to a relative time string, such as | |
* "a minute ago", "in 2 hours", "yesterday", "3 months ago", etc. |