https://minimaxh3.art
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.
90
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
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 |
|---|---|---|
| /beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e178179150... | 86400.0 s | 11.3 KiB |
| minimaxh3.art/images/h3/show-1.webp | 0.0 ms | 436 B |
| minimaxh3.art/images/h3/case-2.jpg | 0.0 ms | 435 B |
| minimaxh3.art/images/h3/case-3.jpg | 0.0 ms | 434 B |
| minimaxh3.art/images/h3/hero-demo-0.jpg | 0.0 ms | 433 B |
| minimaxh3.art/images/h3/hero-demo-0.jpg | 0.0 ms | 432 B |
| minimaxh3.art/images/h3/hero-demo-0.webm | 0.0 ms | 432 B |
| minimaxh3.art/images/h3/case-1.jpg | 0.0 ms | 430 B |
| minimaxh3.art/images/h3/show-2.webp | 0.0 ms | 429 B |
| minimaxh3.art/images/h3/show-3.webp | 0.0 ms | 429 B |
| minimaxh3.art/logo.png | 0.0 ms | 418 B |
| minimaxh3.art/logo.png | 0.0 ms | 414 B |
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 |
|---|---|---|
| minimaxh3.art/assets/index-qMomN_Ek.css | 0 B | 482 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Diagnostics
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 | |
|---|---|
Listed on Turbo0 div.grid > a.flex > span.flex > img.max-h-10 | img.turbo0.com/badge-listed-light.svg |
Featured on ToolPilot div.grid > a.flex > span.flex > img.max-h-10 | www.toolpilot.ai/cdn/shop/files/f-b_690x151_crop_center.png |
NavFolders div.grid > a.flex > span.flex > img.max-h-10 | navfolders.com/badge/nav_dark.svg |
Featured on FreeAI div.grid > a.flex > span.flex > img.max-h-10 | www.freeai.run/badge/badge_dark.svg |
Featured on DeepLaunch.io div.grid > a.flex > span.flex > img.max-h-10 | deeplaunch.io/badge/badge_dark.svg |
Featured on ToolDirs div.grid > a.flex > span.flex > img.max-h-10 | tooldirs.com/badge/badge_dark.svg |
Sneaker dynamization from a still div.mt-10 > article.group > div.relative > img.h-full | minimaxh3.art/images/h3/case-1.jpg |
Night city tracking shot div.mt-10 > article.group > div.relative > img.h-full | minimaxh3.art/images/h3/case-2.jpg |
Character multi-beat from one frame div.mt-10 > article.group > div.relative > img.h-full | minimaxh3.art/images/h3/case-3.jpg |
MiniMax H3 div.grid > div > div.flex > img.size-11 | minimaxh3.art/logo.png |
More information about the performance of your application. These numbers don't directly affect the Performance score.
●Time to Interactive 3.0 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 113 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 1.4 s
●Avoid long main-thread tasks 4 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 330 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 530 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
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 annual deals div.sticky > div.promo-banner > div.relative > a.inline-flex |
MiniMax a.group > span.flex > span.font-display > span.text-white/90 |
H3 a.group > span.flex > span.font-display > span.ml-1 |
Hailuo 3.0 div.mx-auto > a.group > span.flex > span.mt-0.5 |
MiniMax H3 header.w-full > div.mx-auto > a.group > span.sr-only |
Product header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Features header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Showcase header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Pricing header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Product header.w-full > div.border-t > div.flex > a.rounded-lg |
Features header.w-full > div.border-t > div.flex > a.rounded-lg |
Showcase header.w-full > div.border-t > div.flex > a.rounded-lg |
Pricing header.w-full > div.border-t > div.flex > a.rounded-lg |
Try MiniMax H3 text-to-video div.mx-auto > div.grid > div.lg:col-span-4 > a.mt-8 |
Generate with MiniMax H3 section#cases-section > div.mx-auto > div.mt-10 > a.inline-flex |
OpenArt — MiniMax H3 model page div.mx-auto > ul.mt-8 > li.border > a.text-sm |
MiniMax official site div.mx-auto > ul.mt-8 > li.border > a.text-sm |
Hailuo AI div.mx-auto > ul.mt-8 > li.border > a.text-sm |
Start generating section#how-section > div.mx-auto > div.mt-10 > a.inline-flex |
Generate with MiniMax H3 section#cta-section > div.mx-auto > div.mt-8 > a.inline-flex |
View pricing section#cta-section > div.mx-auto > div.mt-8 > a.inline-flex |
Video Studio div > ul.space-y-2.5 > li > a.text-sm |
Pricing div > ul.space-y-2.5 > li > a.text-sm |
About div > ul.space-y-2.5 > li > a.text-sm |
Blog div > ul.space-y-2.5 > li > a.text-sm |
How it works div > ul.space-y-2.5 > li > a.text-sm |
Use cases div > ul.space-y-2.5 > li > a.text-sm |
What is H3 div > ul.space-y-2.5 > li > a.text-sm |
FAQ div > ul.space-y-2.5 > li > a.text-sm |
About div > ul.space-y-2.5 > li > a.text-sm |
Privacy Policy div > ul.space-y-2.5 > li > a.text-sm |
Terms of Service div > ul.space-y-2.5 > li > a.text-sm |
Refund Policy div > ul.space-y-2.5 > li > a.text-sm |
support@minimaxh3.art div.mx-auto > div.grid > div > a.text-sm |
Featured on FreeAI div.mx-auto > div.grid > a.flex > span.min-w-0 |
Featured on ToolDirs div.mx-auto > div.grid > a.flex > span.min-w-0 |
Featured on ToolPilot div.mx-auto > div.grid > a.flex > span.min-w-0 |
Powered by Startup Fast div.mx-auto > div.grid > a.flex > span.min-w-0 |
Featured on DeepLaunch.io div.mx-auto > div.grid > a.flex > span.min-w-0 |
Featured on First Look div.mx-auto > div.grid > a.flex > span.min-w-0 |
Listed on Turbo0 div.mx-auto > div.grid > a.flex > span.min-w-0 |
Listed on ToolRain div.mx-auto > div.grid > a.flex > span.min-w-0 |
NavFolders div.mx-auto > div.grid > a.flex > span.min-w-0 |
Featured on LaunchIgniter div.mx-auto > div.grid > a.flex > span.min-w-0 |
These are opportunities to improve the legibility of your content.
Names and labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.-mt-px > div.flex > div.flex > input.hidden div.-mt-px > div.flex > div.flex > input.hidden |
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.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
View annual deals div.sticky > div.promo-banner > div.relative > a.inline-flex |
Product header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Features header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Showcase header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Pricing header.w-full > div.mx-auto > nav.hidden > a.py-1 |
Get Started header.w-full > div.mx-auto > div.flex > button.inline-flex |
Product header.w-full > div.border-t > div.flex > a.rounded-lg |
Features header.w-full > div.border-t > div.flex > a.rounded-lg |
Sign in to generate div.-mt-px > div.flex > div.hidden > button.inline-flex |
Sign in to generate section#app-section > div.relative > div.mt-1.5 > button.inline-flex |
Cinematic tracking shot of a neon cyberpunk city in the rain section#app-section > div.relative > div.hidden > button.max-w-full |
Slow orbit around a luxury sneaker on a reflective floor section#app-section > div.relative > div.hidden > button.max-w-full |
What is MiniMax H3 or Hailuo 3.0 / 海螺3?▾ div.mx-auto > div.flex > details.group > summary.cursor-pointer |
How long are generated videos, and what resolution?▾ div.mx-auto > div.flex > details.group > summary.cursor-pointer |
How do credits and pricing work?▾ div.mx-auto > div.flex > details.group > summary.cursor-pointer |
Can I use generated videos commercially?▾ div.mx-auto > div.flex > details.group > summary.cursor-pointer |
How long does generation take?▾ div.mx-auto > div.flex > details.group > summary.cursor-pointer |
Does MiniMax H3 generate audio with the video?▾ div.mx-auto > div.flex > details.group > summary.cursor-pointer |
Video Studio div > ul.space-y-2.5 > li > a.text-sm |
Pricing div > ul.space-y-2.5 > li > a.text-sm |
About div > ul.space-y-2.5 > li > a.text-sm |
Blog div > ul.space-y-2.5 > li > a.text-sm |
How it works div > ul.space-y-2.5 > li > a.text-sm |
Use cases div > ul.space-y-2.5 > li > a.text-sm |
What is H3 div > ul.space-y-2.5 > li > a.text-sm |
FAQ div > ul.space-y-2.5 > li > a.text-sm |
About div > ul.space-y-2.5 > li > a.text-sm |
Privacy Policy div > ul.space-y-2.5 > li > a.text-sm |
Terms of Service div > ul.space-y-2.5 > li > a.text-sm |
Refund Policy div > ul.space-y-2.5 > li > a.text-sm |
Powered by Startup Fast section.border-t > div.mx-auto > div.grid > a.flex |
Featured on DeepLaunch.io section.border-t > div.mx-auto > div.grid > a.flex |
Featured on First Look section.border-t > div.mx-auto > div.grid > a.flex |
Listed on Turbo0 section.border-t > div.mx-auto > div.grid > a.flex |
Listed on ToolRain section.border-t > div.mx-auto > div.grid > a.flex |
NavFolders section.border-t > div.mx-auto > div.grid > a.flex |
Featured on LaunchIgniter section.border-t > div.mx-auto > div.grid > a.flex |
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>`
●`[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.
●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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●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 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.
○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
○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.
96
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 |
|---|---|
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
Failed to load resource: the server responded with a status of 404 () | |
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. |
●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 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`