Skip to content
https://free.mabuku.site

Lighthouse Mobile

· 0 checks — Mobile 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.

61

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.

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.

URLResource SizeEst Savings
SCHEMES AND RECORDS OF WORK div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/6a6459171df6c_IMG_20260725_083332.jpg354.1 KiB334.3 KiB
Book Cover div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/assets/images/book-placeholder.png231.7 KiB208.7 KiB
NRP STANDARD 3 ENGLISH TEACHERS GUIDE div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781851004_IMG_20260619_083618.jpg85.9 KiB75.0 KiB
NRP Standard 2 English teachers Guide div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781850881_IMG_20260619_083345.jpg84.0 KiB73.5 KiB
Standard 4 NRP ENGLISH TEACHERS GUIDE div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781848531_IMG_20260619_075221.jpg85.1 KiB73.5 KiB
Standard 1 Chichewa Teachers Guide NRP div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781850701_IMG_20260619_083012.jpg65.1 KiB55.7 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

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.

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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.

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: 1.3 s

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.

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: 320 ms 43.8 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: 1.1 s 154.1 KiB

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.

CategoryTime Spent
Script Evaluation793 ms
Other685 ms
Style & Layout439 ms
Script Parsing & Compilation240 ms
Parse HTML & CSS79 ms
Rendering46 ms

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 reasonFailure type
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

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
NRP Standard 2 English teachers Guide div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781850881_IMG_20260619_083345.jpg
NRP STANDARD 3 ENGLISH TEACHERS GUIDE div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781851004_IMG_20260619_083618.jpg
Book Cover div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/assets/images/book-placeholder.png
SCHEMES AND RECORDS OF WORK div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/6a6459171df6c_IMG_20260725_083332.jpg
Standard 4 NRP ENGLISH TEACHERS GUIDE div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781848531_IMG_20260619_075221.jpg
Standard 1 Chichewa Teachers Guide NRP div#book-list > div.col-6 > div.card > img.card-img-top
free.mabuku.site/uploads/img/1781850701_IMG_20260619_083012.jpg

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,432 KiB
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 10 long tasks found
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 170 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 100 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
87

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View All div.main-content > div.container > div.d-flex > a.text-decoration-none
Standard 1-8 div.col-6 > div.card > div.card-body > span.badge
Form 4 div.col-6 > div.card > div.card-body > span.badge
Standard 3 div.col-6 > div.card > div.card-body > span.badge
Standard 2 div.col-6 > div.card > div.card-body > span.badge
Standard 1 div.col-6 > div.card > div.card-body > span.badge
Standard 4 div.col-6 > div.card > div.card-body > span.badge
View All div.main-content > div.container > div.d-flex > a.text-decoration-none
SUPPORT MABUKU div#global-popup-overlay > div.popup-box > div.popup-header > h2
mabuku.site div.popup-box > div.popup-body > p > strong
K200 div.popup-box > div.popup-body > p > strong
DONATE NOW div.popup-box > div.popup-body > div.popup-cta > a
Maybe Later div#global-popup-overlay > div.popup-box > div.popup-footer > button.close-btn
Privacy Policy div#global-popup-overlay > div.popup-box > div.popup-footer > a.privacy-link

These are opportunities to improve the legibility of your content.

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
Free Learning Resources div.col-12 > div.card > div.card-body > h4.fw-bold
SCHEMES AND RECORDS OF WORK div.col-6 > div.card > div.card-body > h6.card-title

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●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
○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
○`[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
○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
○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.
○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.
○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.
77

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 URLRequest Resolution
free.mabuku.site/?i=1Allowed

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
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Manifest: Line: 1, column: 1, Syntax error.
Manifest: Line: 1, column: 1, Syntax error.
free.mabuku.site/?i=1 line 37, col 4
ReferenceError: aclib is not defined at https://free.mabuku.site/?i=1:38:5
TypeError: Cannot read properties of null (reading 'parentNode') at HTMLDocument.<anonymous> (https://free.mabuku.site/assets/js/search.js:8:17)
●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
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`

Send Feedback