Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

—

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/signals/config/842388869148196?v=2.9.303&r=stable&domain...	1200.0 s	46.8 KiB
/modules/custom/qcon_base/images/newsletter-images/footer...	0.0 ms	27.0 KiB
/modules/custom/qcon_base/images/newsletter-images/footer...	0.0 ms	7.9 KiB
/modules/custom/qcon_base/images/newsletter-images/footer...	0.0 ms	6.5 KiB
qconlondon.com/modules/custom/qcon_base/icons/icon-x-32.png	0.0 ms	1.2 KiB
/tr/?id=842388869148196&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	274 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Securing the AI Stack: From Model to Production `li > div.card__content > a.card__header > img.card__image`	/fit-in/256x364/filters:quality(80)/minibooks/secure-ai-s...	23.1 KiB	19.9 KiB
Evaluating AI Agents in Practice: Benchmarks, Frameworks, and Lessons Learned -… `div.single_card > a.thumb > picture > img`	/eyJidWNrZXQiOiAiYXNzZXRzLmluZm9xLmNvbSIsImtleSI6ICJ3ZWIv...	22.4 KiB	17.4 KiB
Architecture in the Age of AI: Change and Opportunity `li > div.card__content > a.card__header > img.card__image`	/fit-in/256x364/filters:quality(80)/minibooks/architectur...	13.7 KiB	10.5 KiB
Architecture Through Different Lenses 2025 `li > div.card__content > a.card__header > img.card__image`	/fit-in/256x364/filters:quality(80)/minibooks/architectur...	11.5 KiB	8.8 KiB
The InfoQ Trends Reports 2025 eMag `li > div.card__content > a.card__header > img.card__image`	/fit-in/256x364/filters:quality(80)/minibooks/2025-infoq-...	10.8 KiB	8.3 KiB
Lakehouse Tower of Babel: Handling Identifier Resolution Rules across Database … `li > div.card__content > a.card__header > img.card__image`	/fit-in/100x100/filters:quality(80)/articles/lakehouse-sq...	9.8 KiB	8.2 KiB
Building Production-Ready tRPC APIs: The TypeScript Alternative to Apollo Feder… `li > div.card__content > a.card__header > img.card__image`	/fit-in/100x100/filters:quality(80)/articles/building-trp...	9.1 KiB	7.5 KiB
Redesigning Banking PDF Table Extraction: A Layered Approach with Java `li > div.card__content > a.card__header > img.card__image`	/fit-in/100x100/filters:quality(80)/articles/redesign-pdf...	8.0 KiB	6.4 KiB
Using AWS Lambda Extensions to Run Post-Response Telemetry Flush `li > div.card__content > a.card__header > img.card__image`	/fit-in/100x100/filters:quality(80)/articles/lambda-exten...	7.8 KiB	6.2 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
cdn.infoq.com/statics_s1_20260421232814/styles/style.css	968.9 KiB
cdn.infoq.com/statics_s1_20260421232814/scripts/combinedJs.min.js	58.4 KiB
cdn.infoq.com/statics_s1_20260421232814/scripts/infoq.js	115.4 KiB
cdn.infoq.com/statics_s1_20260421232814/scripts/relatedVcr.min.js	5.7 KiB
cdn.infoq.com/statics_s1_20260421232814/styles/fonts/font.css	947 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
cdn.infoq.com/statics_s1_20260421232814/styles/icons.css	10.0 MiB
cdn.infoq.com/statics_s1_20260421232814/styles/style.css	968.9 KiB
/newsletter/architect/en/assets/Astronomer-DataPipeline-A...	306.6 KiB
www.googletagmanager.com/gtag/js?id=G-VMVPD4D2JY&cx=c&gtm=4e64h1	159.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W9GJ5DL	128.7 KiB
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js	123.3 KiB
cdn.infoq.com/statics_s1_20260421232814/scripts/infoq.js	115.4 KiB
connect.facebook.net/en_US/fbevents.js	96.6 KiB
cdn.infoq.com/statics_s1_20260421232814/scripts/combinedJs.min.js	58.4 KiB
/signals/config/842388869148196?v=2.9.303&r=stable&domain...	46.8 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.4 s

●Avoid non-composited animations 4 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 250 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP breakdown

○LCP request discovery

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
pnpm 11 Release Candidate: ESM Distribution, Supply Chain Defaults and a New St… `li > div.card__content > div.card__data > h4.card__title`
Anthropic Introduces Agent-Based Code Review for Claude Code `li.news > div.card__content > div.card__data > h5.card__title`
Redesigning Banking PDF Table Extraction: A Layered Approach with Java `li > div.card__content > div.card__data > h4.card__title`
Dynamic Moments: Weaving LLMs into Deep Personalization at DoorDash `li > div.card__content > div.card__data > h5.card__title`
Engineering Stable, Secure and Scalable Platforms: A Conversation with Matthew … `li > div.card__content > div.card__data > h5.card__title`
Securing the AI Stack: From Model to Production `li > div.card__content > div.card__data > h5.card__title`
Events `section.section > div.container__inner > div.events__list > h4.heading`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MICHAEL REDLICH `footer > div.authors > span > a`
ERIK COSTLOW `footer > div.authors > span > a`
KARSTEN SILZ `footer > div.authors > span > a`
TRISHA GEE `footer > div.authors > span > a`
MARIT VAN DIJK `footer > div.authors > span > a`
RICHARD FICHTNER `footer > div.authors > span > a`
BERT JAN SCHRIJVER `footer > div.authors > span > a`
STEEF-JAN WIGGERS `footer > div.authors > span > a`
SHWETA VOHRA `footer > div.authors > span > a`
SRINI PENCHIKALA `footer > div.authors > span > a`
SAVANNAH KUNOVSKY `footer > div.authors > span > a`
ANTHONY ALFORD `footer > div.authors > span > a`
DANIEL DOMINGUEZ `footer > div.authors > span > a`
SHANE HASTIE `footer > div.authors > span > a`
JUTTA ECKSTEIN `footer > div.authors > span > a`
SUSAN MCINTOSH `footer > div.authors > span > a`
RAFIQ GEMMAIL `footer > div.authors > span > a`
THOMAS BETTS `footer > div.authors > span > a`
SARAH WELLS `footer > div.authors > span > a`
ERAN STILLER `footer > div.authors > span > a`
DANIEL BRYANT `footer > div.authors > span > a`
SUDEEP DAS `div.card__details > div.card__authors > span > a`
PRADEEP MUTHUKRISHNAN `div.card__details > div.card__authors > span > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
/newsletter/architect/en/assets/Astronomer-DataPipeline-A...	Automatically upgraded to HTTPS

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`