Lighthouse Mobile

· 0 checks — Mobile 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
www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js	3600.0 s	510.6 KiB
www.opensocietyfoundations.org/dist/images/map-v2.svg	3600.0 s	114.4 KiB
www.opensocietyfoundations.org/dist/scripts/app-05eb876a18.js	3600.0 s	101.7 KiB
www.opensocietyfoundations.org/dist/styles/app-26c94e4767.css	3600.0 s	85.8 KiB
www.opensocietyfoundations.org/dist/fonts/LyonDisplay-Bold-Web.woff2	3600.0 s	55.0 KiB
www.opensocietyfoundations.org/dist/fonts/GT-America-Standard-Bold.woff2	3600.0 s	48.0 KiB
www.opensocietyfoundations.org/dist/fonts/GT-America-Compressed-Bold.woff2	3600.0 s	47.4 KiB
www.opensocietyfoundations.org/dist/fonts/GT-America-Standard-Regular.woff2	3600.0 s	45.4 KiB
www.opensocietyfoundations.org/dist/fonts/GT-America-Mono-Regular.woff2	3600.0 s	35.8 KiB
cdn.matomo.cloud/theideasletter.matomo.cloud/matomo.js	691200.0 s	39.0 KiB
cdn-cookieyes.com/assets/images/poweredbtcky.svg	36000.0 s	1.5 KiB
cdn-cookieyes.com/assets/images/close.svg	36000.0 s	858 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.126382] map[node:map[boundingRect:map[bottom:707 height:275 left:0 right:412 top:432 width:412] lhId:page-2-DIV nodeLabel:People holding flags path:1,HTML,1,BODY,7,DIV,2,MAIN,0,DIV,0,DIV,0,SECTION,1,DIV selector:div > div > section.m-hero > div.m-hero__image snippet:<div class="m-hero__image"> type:node] score:0.126382 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:3089 height:205 left:25 right:387 top:2884 width:362] lhId:page-54-IMG nodeLabel:George Soros path:1,HTML,1,BODY,7,DIV,2,MAIN,0,DIV,0,DIV,6,DIV,0,DIV,1,DIV,0,DIV,0,FIGURE,0,DIV,0,IMG selector:div.m-textBlock > figure.a-media > div.a-media__container > img snippet:<img src="https://opensocietyfoundations.imgix.net/uploads/e9f02c84-c594-4a4c-991b-1…" srcset="https://opensocietyfoundations.imgix.net/uploads/e9f02c84-c594-4a4c-991b-1…" alt="George Soros"> type:node]]] type:subitems]]]

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:31.199 source:map[column:21958 line:1 type:source-location url:https://www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:57.608 source:map[type:text value:[unattributed]]] map[reflowTime:0.751 source:map[column:55127 line:0 type:source-location url:https://www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js urlProvider:network]] map[reflowTime:2.999 source:map[column:68960 line:0 type:source-location url:https://www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js urlProvider:network]] map[reflowTime:0.656 source:map[column:37684 line:0 type:source-location url:https://www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js urlProvider:network]] map[reflowTime:0.405 source:map[column:48624 line:0 type:source-location url:https://www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js urlProvider:network]] map[reflowTime:26.388 source:map[column:43021 line:0 type:source-location url:https://www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js urlProvider:network]]]

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
People holding flags `section.m-hero > div.m-hero__image > picture > img`	/uploads/9b241864-37fa-40a3-b76e-8b4038b9d35a/20230524-bh...	84.2 KiB	40.3 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

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.

Estimated savings: 753 ms

URL	Time Spent
opensocietyfoundations.org/	753 ms
www.opensocietyfoundations.org/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
People holding flags `div > div > section.m-hero > div.m-hero__image`	0.126

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

Diagnostics

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.

Estimated savings: 450 ms 76.3 KiB

URL	Transfer Size	Est Savings
www.opensocietyfoundations.org/dist/styles/app-26c94e4767.css	85.7 KiB	76.3 KiB

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.

Estimated savings: 450 ms 217.3 KiB

URL	Transfer Size	Est Savings
www.opensocietyfoundations.org/dist/scripts/app-05eb876a18.js	101.6 KiB	87.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-NNRNV5Q	145.9 KiB	64.8 KiB
www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js	510.5 KiB	40.8 KiB
cdn.matomo.cloud/theideasletter.matomo.cloud/matomo.js	38.5 KiB	24.2 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js	3.8 s	2.6 s	232 ms
www.opensocietyfoundations.org/	927 ms	30 ms	5.0 ms
Unattributable	573 ms	22 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-NNRNV5Q	461 ms	378 ms	75 ms
www.opensocietyfoundations.org/dist/scripts/app-05eb876a18.js	213 ms	117 ms	55 ms
cdn-cookieyes.com/client_data/d5c9db975dc7fd2090aba4aa/banner.js	117 ms	74 ms	5.9 ms
cdn.matomo.cloud/theideasletter.matomo.cloud/matomo.js	95 ms	67 ms	26 ms
cdn-cookieyes.com/client_data/d5c9db975dc7fd2090aba4aa/script.js	52 ms	45 ms	5.2 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.3 s
Other	1.2 s
Style & Layout	872 ms
Script Parsing & Compilation	407 ms
Garbage Collection	215 ms
Rendering	142 ms
Parse HTML & CSS	132 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
People holding flags `section.m-hero > div.m-hero__image > picture > img`	/uploads/9b241864-37fa-40a3-b76e-8b4038b9d35a/20230524-bh...
George Soros `div.m-textBlock > figure.a-media > div.a-media__container > img`	/uploads/e9f02c84-c594-4a4c-991b-1c49c6b0e054/2007-george...

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

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,409 KiB

●Avoid long main-thread tasks 12 long tasks found

●Avoid non-composited animations 47 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

100

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.

○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

●`[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

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

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

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

○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.

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.opensocietyfoundations.org/dist/scripts/maps-400ffa8c35.js

●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 browser errors logged to the console

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.opensocietyfoundations.org/voices	Learn more
www.opensocietyfoundations.org/how-we-work/how-we-fund	Learn more

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

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`