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.

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.

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

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

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	Duration
/main.b7671beac3a81e5447906e60b8ae1e3d60a303775feea4ab908...	11.0 KiB	77 ms

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
gc.zgo.at/count.js	604800.0 s	3.3 KiB

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
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/national-assembly-vs-senate/cover_hu_e2a0797685312039.webp	21.5 KiB	15.7 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/prime-cabinet-secretary-salary/cover_hu_de683e8e93b0ea7c.webp	20.8 KiB	15.2 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/principal-secretary-salary/cover_hu_c9542258d21940ac.webp	19.3 KiB	14.1 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/faqs-elections-kenya/cover_hu_de9d1b38e5033928.webp	19.3 KiB	14.1 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	/top-ten-counties-revenue-collection/cover_hu_eb920c51bf3...	18.8 KiB	13.7 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/cabinet-secretary-salary/cover_hu_31510b202d2934e8.webp	18.3 KiB	13.4 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/county-assembly-structure/cover_hu_969a7fc1dfd9e3f1.webp	18.0 KiB	13.2 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/free-fair-elections/cover_hu_3221bc1097c99105.webp	17.6 KiB	12.8 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/national-assembly-role/cover_hu_9a3f2d0ea6f7a298.webp	17.5 KiB	12.8 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/attorney-general-salary/cover_hu_cc3e1da0b802c102.webp	17.5 KiB	12.8 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/consolidated-fund-services/cover_hu_d3249e587ecd7689.webp	17.2 KiB	12.6 KiB
a.group > div.bg-gray-100 > div.block > img.w-full `a.group > div.bg-gray-100 > div.block > img.w-full`	blog.afro.co.ke/role-of-political-parties/cover_hu_d552b0a6f314d4b.webp	15.5 KiB	11.3 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.6 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 365 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 30 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 30 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Constitution `div.flex > ul.hidden > li.relative > a.text-gray-600`
Tags `div.flex > ul.hidden > li.relative > a.text-gray-600`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#main-nav > div.flex > ul.hidden > a.relative `nav#main-nav > div.flex > ul.hidden > a.relative`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tags En `div.mx-auto > nav#main-nav > div.flex > ul.hidden`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
En `div.flex > ul.hidden > div.hidden > li.relative`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Categories `div.flex > ul.hidden > li.relative > button.inline-flex`
En `ul.hidden > div.hidden > li.relative > button.flex`

○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

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

●Select elements have associated label elements.

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○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 buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

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

○Identical links have the same purpose.

○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

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.

Source	Description
blog.afro.co.ke/ line 76, col 0	`Executing inline script violates the following Content Security Policy directive 'script-src 'self' https://afrocave.goatcounter.com/count https://gc.zgo.at/count.js'. Either the 'unsafe-inline' keyword, a hash ('sha256-OYHFM4g87MIqGMUwh6OpoJctO554ZhYDKlajuSdI80Q='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked.`
blog.afro.co.ke/	`Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/v833ccba57c9e4d2798f2e76cebdd09a11778172276447' violates the following Content Security Policy directive: "script-src 'self' https://afrocave.goatcounter.com/count https://gc.zgo.at/count.js". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.`

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
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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`