Skip to content
https://indymedia.org

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

100

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.

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

●Use efficient cache lifetimes
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Time to Interactive 0.2 s
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 4 KiB
●Minimizes main-thread work 0.0 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 0 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 170 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○JavaScript execution time
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
76

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
https://www.indybay.org/newsitems/2019/11/30/18828519.php body > ul > li > a
https://www.democracynow.org/2019/11/27/1999_wto_protests_20_years_later body > ul > li > a
https://archive.is/03tV4 body > ul > li > a
Indymedia 20th Anniversary Encuentro body > ul > li > a
https://www.historylink.org/File/2142 body > ul > li > a
Antwerpen body > p > a
Athens body > p > a
Barcelona body > p > a
Belarus body > p > a
Belgium body > p > a
Brussels body > p > a
Bulgaria body > p > a
Estrecho / madiaq body > p > a
Germany body > p > a
Grenoble body > p > a
Ireland body > p > a
Istanbul body > p > a
Italy body > p > a
La plana body > p > a
Paris/Île-de-france body > p > a
Patras body > p > a
Piemonte body > p > a
Poland body > p > a
Portugal body > p > a
Romania body > p > a
Russia body > p > a
Sardegna body > p > a
Scotland body > p > a
Switzerland body > p > a
Ukraine body > p > a
United kingdom body > p > a
Valencia body > p > a.indypagebody
Atlanta body > p > a
Big muddy body > p > a
Boston body > p > a
Buffalo body > p > a
Chicago body > p > a
Santa cruz, ca body > p > a
United states body > p > a
Urbana-champaign body > p > a
print body > a
radio body > a
satellite tv body > a
video body > a
abruzzo body > a
alacant body > a
andorra body > a
antwerpen body > a
armenia body > a
athens body > a
austria body > a
barcelona body > a
belarus body > a
belgium body > a
bristol body > a
brussels body > a
bulgaria body > a
calabria body > a
cyprus body > a
emilia-romagna body > a
euskal herria body > a
galiza body > a
germany body > a
grenoble body > a
ireland body > a
istanbul body > a
italy body > a
la plana body > a
liege body > a
liguria body > a
lille body > a
linksunten body > a
lombardia body > a
london body > a
madrid body > a
malta body > a
marseille body > a
nantes body > a
napoli body > a
netherlands body > a
nice body > a
northern england body > a
nottingham body > a
paris/île-de-france body > a
patras body > a
piemonte body > a
poland body > a
portugal body > a
romania body > a
russia body > a
sardegna body > a
sverige body > a
switzerland body > a
torun body > a
toscana body > a
toulouse body > a
ukraine body > a
valencia body > a
argentina body > a
bolivia body > a
chiapas body > a
chile body > a
chile sur body > a
cmi brasil body > a
colombia body > a
ecuador body > a
mexico body > a
peru body > a
puerto rico body > a
qollasuyu body > a
rosario body > a
santiago body > a
tijuana body > a
uruguay body > a
valparaiso body > a
aotearoa body > a
darwin body > a
atlanta body > a
austin body > a
austin indymedia body > a
big muddy body > a
binghamton body > a
boston body > a
buffalo body > a
charlottesville body > a
chicago body > a
cleveland body > a
colorado body > a
columbus body > a
dc body > a
hawaii body > a
houston body > a
hudson mohawk body > a
kansas city body > a
la body > a
madison body > a
maine body > a
michigan body > a
milwaukee body > a
minneapolis/st. paul body > a
new jersey body > a
new mexico body > a
new orleans body > a
north carolina body > a
nyc body > a
philadelphia body > a
pittsburgh body > a
portland body > a
richmond body > a
rochester body > a
rogue valley body > a
san diego body > a
san francisco body > a
san francisco bay area body > a
santa cruz, ca body > a
sarasota body > a
seattle body > a
tennessee body > a
urbana-champaign body > a
worcester body > a
armenia body > a
beirut body > a
israel body > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●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
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Elements with visible text labels have matching accessible names.
○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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
indymedia.org/favicon.ico
Failed to load resource: the server responded with a status of 404 (Not Found)
●Uses HTTPS
●Avoids deprecated APIs
●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 issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
90

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Document has a valid `hreflang`
○robots.txt is valid
○Image elements have `[alt]` attributes
○Document has a valid `rel=canonical`

Send Feedback