https://aicost.tools
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.
99
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 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:30.556 source:map[column:19 line:173 type:source-location url:https://earlylaunch.co/widget/1e211b2b-5d2d-400f-898a-32c44314c7fb/script.js urlProvider:network]]]
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
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 |
|---|---|---|
| earlylaunch.co/widget/1e211b2b-5d2d-400f-898a-32c44314c7fb/script.js | 14400.0 s | 2.4 KiB |
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 |
|---|---|---|
| aicost.tools/_astro/Base.xACOz3Uc.css | 7.5 KiB | 120 ms |
| aicost.tools/_astro/index.CDcIbIbF.css | 4.6 KiB | 214 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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: 0.0 ms 73.0 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-FN9H4RKMSJ | 176.8 KiB | 73.0 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.
Launched on AI Website Directory div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Featured on LaunchNests div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
AICost on PeerPush div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Featured on AITrustList div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Listed on ProofStories div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Submit AI Tools div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Featured on Next Launch div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Featured div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
AICost on Siteefy div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Listed on AgentLocker — AICost div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
LaunchClash div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Pro Launch Featured Badge (light theme) div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
AICost on OnlyFoundrs div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
Ranked on OpenRank.bid div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img div.fo-track > div.fo-group > a.fo-card > img.fo-badge-img |
More information about the performance of your application. These numbers don't directly affect the Performance score.
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Time to Interactive 0.9 s
●Max Potential First Input Delay 30 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 548 KiB
●JavaScript execution time 0.1 s
●Minimizes main-thread work 0.3 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 100 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 200 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
94
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 |
|---|
Search the index nav.top > div.nav-actions > button.search-trigger > span.search-label |
SECTION table.directory-table > thead > tr > th |
COVERAGE table.directory-table > thead > tr > th |
PAGES table.directory-table > thead > tr > th.num-col |
UPDATED table.directory-table > thead > tr > th.num-col |
STATUS table.directory-table > thead > tr > th.num-col |
6 LABS · CURRENT FRONTIER TIER · RATES VERIFIED 2026-10-23 section.picks-section > div.picks-head > div.picks-meta > span |
ANTHROPIC section.picks-section > div.pp-grid > a.pp-card > div.pp-tier |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
INPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
OUTPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
BLENDED a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
OPENAI section.picks-section > div.pp-grid > a.pp-card > div.pp-tier |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
INPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
OUTPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
BLENDED a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
GOOGLE DEEPMIND section.picks-section > div.pp-grid > a.pp-card > div.pp-tier |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
INPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
OUTPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
BLENDED a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
SPACEXAI section.picks-section > div.pp-grid > a.pp-card > div.pp-tier |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
INPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
OUTPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
BLENDED a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
MOONSHOT (KIMI) section.picks-section > div.pp-grid > a.pp-card > div.pp-tier |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
INPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
OUTPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
BLENDED a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
ZHIPU (Z.AI / GLM) section.picks-section > div.pp-grid > a.pp-card > div.pp-tier |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
INPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
OUTPUT a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
/M div.pp-prices > div.pp-price > div.pp-price-num > span.pp-price-unit |
BLENDED a.pp-card > div.pp-prices > div.pp-price > div.pp-price-label |
Blended rate assumes a 92% input / 8% output, 82% cached workload — the same as… body > main > section.picks-section > p.pp-note |
SOURCE-VERIFIED · LIVE PRICING & BENCHMARKS section.picks-section > div.picks-head > div.picks-meta > span |
§ COMPARE / 01 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
2026-10 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
VS div.cmps-grid > a.cmp-card > div.cmp-vs > span.cmp-vs-sep |
§ COMPARE / 02 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
2026-10 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
VS div.cmps-grid > a.cmp-card > div.cmp-vs > span.cmp-vs-sep |
§ COMPARE / 03 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
2026-10 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
VS div.cmps-grid > a.cmp-card > div.cmp-vs > span.cmp-vs-sep |
§ COMPARE / 04 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
2026-09 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
VS div.cmps-grid > a.cmp-card > div.cmp-vs > span.cmp-vs-sep |
§ COMPARE / 05 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
2026-09 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
VS div.cmps-grid > a.cmp-card > div.cmp-vs > span.cmp-vs-sep |
§ COMPARE / 06 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
2026-09 div.cmps-grid > a.cmp-card > div.cmp-meta > span |
VS div.cmps-grid > a.cmp-card > div.cmp-vs > span.cmp-vs-sep |
SEP 27 · 17 MIN div.feature-grid > a.feature-card > div.feature-meta > span |
SEP 19 · 17 MIN div.feature-grid > a.feature-card > div.feature-meta > span |
AUG 31 · 24 MIN div.feature-grid > a.feature-card > div.feature-meta > span |
AUG 27 · 22 MIN div.feature-grid > a.feature-card > div.feature-meta > span |
AUG 23 · 19 MIN div.feature-grid > a.feature-card > div.feature-meta > span |
AUG 21 · 16 MIN div.feature-grid > a.feature-card > div.feature-meta > span |
FEATURED ON main > section.featured-on > div.fo-head > span.fo-eyebrow |
AFFILIATE DISCLOSURE · SOME LINKS ARE TRACKED. SPONSORED SLOTS ARE VISUALLY MAR… div.footer-inner > div.footer-grid > div.footer-lede > p.footer-disclaimer |
© 2026 AI//COST · Vol. 02, Issue 047 · Published continuously since 2025 footer > div.footer-inner > div.footer-bottom > div |
Search div.footer-inner > div.footer-bottom > div.legal > a |
Methodology div.footer-inner > div.footer-bottom > div.legal > a |
Privacy div.footer-inner > div.footer-bottom > div.legal > a |
Terms div.footer-inner > div.footer-bottom > div.legal > a |
Contact div.footer-inner > div.footer-bottom > div.legal > a |
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 |
|---|
TOOLS div.footer-inner > div.footer-grid > div.footer-col > h4 |
These are opportunities to improve keyboard navigation in your application.
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 |
|---|
Search the index
/ body > nav.top > div.nav-actions > button.search-trigger |
Tiny Startups
tinystartups.com div.fo-viewport > div.fo-track > div.fo-group > a.fo-card |
FridayHunt
fridayhunt.com div.fo-viewport > div.fo-track > div.fo-group > a.fo-card |
○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
●`[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
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●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.
○`[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 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
○`<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.
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
●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`