https://emmanuel-alade-websi-5h0d.bolt.host

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.

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
Emmanuel Alade `header.fixed > nav.container-lux > a.flex > img.h-12`	emmanuel-alade-websi-5h0d.bolt.host/Brand_logo_2.png	929.0 KiB	928.5 KiB
Emmanuel Alade — Brand Strategist & Website Designer `div.lg:col-span-5 > div.relative > div.relative > img.h-full`	emmanuel-alade-websi-5h0d.bolt.host/file_000000005f447243822948e698b48f4b_5.png	594.9 KiB	561.8 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:312.428 label:Time to first byte subpart:timeToFirstByte] map[duration:1039.352 label:Resource load delay subpart:resourceLoadDelay] map[duration:1173.866 label:Resource load duration subpart:resourceLoadDuration] map[duration:56.984 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Emmanuel Alade

path: 1,HTML,1,BODY,0,DIV,0,DIV,0,HEADER,0,NAV,0,A,0,IMG

selector: header.fixed > nav.container-lux > a.flex > img.h-12

snippet: <img src="/Brand_logo_2.png" alt="Emmanuel Alade" class="h-12 w-auto transition-transform duration-300 group-hover:scale-105">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Emmanuel Alade

path: 1,HTML,1,BODY,0,DIV,0,DIV,0,HEADER,0,NAV,0,A,0,IMG

selector: header.fixed > nav.container-lux > a.flex > img.h-12

snippet: <img src="/Brand_logo_2.png" alt="Emmanuel Alade" class="h-12 w-auto transition-transform duration-300 group-hover:scale-105">

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.

URL	Transfer Size	Duration
emmanuel-alade-websi-5h0d.bolt.host/assets/index-KCO9pV2O.css	7.0 KiB
/css2?family=Cormorant+Garamond:ital,wght@0,300;0,400;0,5...	1.6 KiB	858 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
bolt.new/badge.js?s=7817d710-915a-46a9-9243-0a581221d7fc	60.0 s	464 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

Diagnostics

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: 500 ms 57.3 KiB

URL	Transfer Size	Est Savings
emmanuel-alade-websi-5h0d.bolt.host/assets/index-DHYN5LDQ.js	112.7 KiB	57.3 KiB

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
Emmanuel Alade `header.fixed > nav.container-lux > a.flex > img.h-12`	emmanuel-alade-websi-5h0d.bolt.host/Brand_logo_2.png
Emmanuel Alade `div.grid > div.md:col-span-4 > a.flex > img.h-12`	emmanuel-alade-websi-5h0d.bolt.host/Brand_logo_2.png

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

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

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
Brand Strategist, Website Designer & AI Solutions Specialist helping businesses… `div.container-lux > div.grid > div.md:col-span-4 > p.mt-6`
hello@emmanuelalade.com `div.grid > div.md:col-span-4 > div.mt-6 > a.flex`
+234 808 916 5528 `div.grid > div.md:col-span-4 > div.mt-6 > a.flex`
Ibadan, Nigeria `div.grid > div.md:col-span-4 > div.mt-6 > p.flex`
Home `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
About `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Services `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Work `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Journal `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Contact `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Brand Strategy `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Website Design `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
AI Solutions `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Social Media `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
Content Marketing `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
LinkedIn Marketing `div.md:col-span-3 > ul.space-y-3 > li > a.text-sm`
© 2026 Emmanuel Alade. All rights reserved. `footer.bg-navy-800 > div.container-lux > div.mt-16 > p.text-xs`
From Ibadan to the world. `footer.bg-navy-800 > div.container-lux > div.mt-16 > p.text-xs`

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
NAVIGATE `div.container-lux > div.grid > div.md:col-span-3 > h4.text-xs`

These are opportunities to improve keyboard navigation in your application.

○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

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

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

○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

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

○Identical links have the same purpose.

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

100

Best Practices

●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

●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

○Use a strong HSTS policy

○Detected JavaScript libraries

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
62	`<!doctype html>`	`Syntax not understood`
63	`<html lang="en">`	`Syntax not understood`
64	`<head>`	`Syntax not understood`
65	`<meta charset="UTF-8" />`	`Syntax not understood`
66	`<link rel="icon" type="image/png" href="/Brand_logo_2.png" />`	`Syntax not understood`
67	`<meta name="viewport" content="width=device-width, initial-scale=1.0" />`	`Syntax not understood`
68	`<meta name="theme-color" content="#071D3A" />`	`Syntax not understood`
70	`<title>Emmanuel Alade — Brand Strategist, Website Designer & AI Solutions Specialist</title>`	`Syntax not understood`
71	`<meta name="description" content="Helping businesses build memorable brands, high-performing websites, and intelligent digital experiences through strategy, design, and AI. Based in Ibadan, Nigeria — working worldwide." />`	`Syntax not understood`
72	`<meta name="keywords" content="Brand Strategist, Website Designer, Website Developer, AI Solutions Specialist, Branding Consultant, Personal Branding, Digital Strategy, Business Websites, Emmanuel Alade" />`	`Syntax not understood`
73	`<meta name="author" content="Emmanuel Alade" />`	`Syntax not understood`
74	`<meta name="robots" content="index, follow" />`	`Syntax not understood`
76	`<meta property="og:type" content="website" />`	`Unknown directive`
77	`<meta property="og:title" content="Emmanuel Alade — Brand Strategist & Website Designer" />`	`Unknown directive`
78	`<meta property="og:description" content="Helping businesses build memorable brands, high-performing websites, and intelligent digital experiences through strategy, design, and AI." />`	`Unknown directive`
79	`<meta property="og:image" content="/VERA_SKINCARE_PROJECT_COVER_IMAGE.png" />`	`Unknown directive`
81	`<meta name="twitter:card" content="summary_large_image" />`	`Unknown directive`
82	`<meta name="twitter:title" content="Emmanuel Alade — Brand Strategist & Website Designer" />`	`Unknown directive`
83	`<meta name="twitter:description" content="Helping businesses build memorable brands, high-performing websites, and intelligent digital experiences through strategy, design, and AI." />`	`Unknown directive`
84	`<meta name="twitter:image" content="/VERA_SKINCARE_PROJECT_COVER_IMAGE.png" />`	`Unknown directive`
86	`<script type="application/ld+json">`	`Syntax not understood`
87	`{`	`Syntax not understood`
88	`"@context": "https://schema.org",`	`Unknown directive`
89	`"@type": "ProfessionalService",`	`Unknown directive`
90	`"name": "Emmanuel Alade",`	`Unknown directive`
91	`"description": "Brand Strategist, Website Designer & Developer, and AI Solutions Specialist helping businesses build memorable brands and intelligent digital experiences.",`	`Unknown directive`
92	`"url": "https://emmanuelalade.com",`	`Unknown directive`
93	`"email": "hello@emmanuelalade.com",`	`Unknown directive`
94	`"address": {`	`Unknown directive`
95	`"@type": "PostalAddress",`	`Unknown directive`
96	`"addressLocality": "Ibadan",`	`Unknown directive`
97	`"addressCountry": "Nigeria"`	`Unknown directive`
98	`},`	`Syntax not understood`
99	`"knowsAbout": ["Brand Strategy", "Website Design", "Website Development", "AI Solutions", "Digital Strategy", "Personal Branding", "Social Media Marketing", "Content Marketing"],`	`Unknown directive`
100	`"serviceType": ["Brand Strategy", "Website Design & Development", "AI Solutions", "Social Media Management", "Content Marketing", "LinkedIn Marketing", "Analytics & Reporting", "Video Editing", "Content Writing"]`	`Unknown directive`
101	`}`	`Syntax not understood`
102	`</script>`	`Syntax not understood`
103	`<script type="module" crossorigin src="/assets/index-DHYN5LDQ.js"></script>`	`Syntax not understood`
104	`<link rel="stylesheet" crossorigin href="/assets/index-KCO9pV2O.css">`	`Syntax not understood`
105	`<script async src="https://bolt.new/badge.js?s=7817d710-915a-46a9-9243-0a581221d7fc"></script></head>`	`Unknown directive`
106	`<body>`	`Syntax not understood`
107	`<div id="root"></div>`	`Syntax not understood`
108	`</body>`	`Syntax not understood`
109	`</html>`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`