Skip to content
https://myminifactory.com

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.

43

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.

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.

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:379.3409990234375 label:Time to first byte subpart:timeToFirstByte] map[duration:985.2670009765625 label:Resource load delay subpart:resourceLoadDelay] map[duration:49.688 label:Resource load duration subpart:resourceLoadDuration] map[duration:1143.844 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div > div > picture.sc-bxWfHM > img.sc-eCiCVF
path: 1,HTML,1,BODY,3,DIV,1,SECTION,0,SECTION,1,DIV,0,DIV,a,#document-fragment,1,DIV,0,DIV,0,A,0,DIV,0,DIV,0,PICTURE,1,IMG
selector: div > div > picture.sc-bxWfHM > img.sc-eCiCVF
snippet: <img src="https://images2.myminifactory.com/insecure/resizing_type:fill-down/enlarge…" alt="" class="sc-eCiCVF dDsFVr">

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: div > div > picture.sc-bxWfHM > img.sc-eCiCVF
path: 1,HTML,1,BODY,3,DIV,1,SECTION,0,SECTION,1,DIV,0,DIV,a,#document-fragment,1,DIV,0,DIV,0,A,0,DIV,0,DIV,0,PICTURE,1,IMG
selector: div > div > picture.sc-bxWfHM > img.sc-eCiCVF
snippet: <img src="https://images2.myminifactory.com/insecure/resizing_type:fill-down/enlarge…" alt="" class="sc-eCiCVF dDsFVr">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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.

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
Universal Guard - AFV div.sc-bXdtCk > div.sc-bXdtCk > a > img.sc-kDXjwZ
/insecure/resizing_type:fill-down/enlarge:true/height:600...52.9 KiB47.4 KiB
div.sc-bXdtCk > div.sc-bXdtCk > a > div.sc-fIQtvO div.sc-bXdtCk > div.sc-bXdtCk > a > div.sc-fIQtvO
/insecure/resizing_type:fill-down/enlarge:true/height:550...123.4 KiB35.8 KiB
Samucrab Kungfu / Claw Hugger Samurai / Water Ronin / Asian Sea Creature / Unde… div.sc-bXdtCk > div.sc-bXdtCk > a > img.sc-kDXjwZ
/insecure/resizing_type:fill-down/enlarge:true/height:600...42.3 KiB31.3 KiB
div.sc-bXdtCk > div.sc-bXdtCk > a > div.sc-fIQtvO div.sc-bXdtCk > div.sc-bXdtCk > a > div.sc-fIQtvO
/insecure/resizing_type:fill-down/enlarge:true/height:600...77.5 KiB18.9 KiB
Trench Crusade Tribe banner div > a > picture > img
/insecure/resizing_type:fill-down/enlarge:true/plain/http...22.1 KiB17.7 KiB
div.sc-bXdtCk > div.sc-bXdtCk > a > div.sc-fIQtvO div.sc-bXdtCk > div.sc-bXdtCk > a > div.sc-fIQtvO
/insecure/resizing_type:fill-down/enlarge:true/height:600...50.4 KiB17.4 KiB
div > div > picture.sc-bxWfHM > img.sc-eCiCVF div > div > picture.sc-bxWfHM > img.sc-eCiCVF
/insecure/resizing_type:fill-down/enlarge:true/width:430/...46.4 KiB16.3 KiB
onepagerules div > div.sc-bXdtCk > a > img.sc-ljKisr
/insecure/rt:fill-down/w:200/h:200/el:1/plain/https://dl4...8.4 KiB8.0 KiB
Anvil Digital Forge div.sc-bXdtCk > a > div.sc-bXdtCk > img.sc-ljKisr
/insecure/rt:fill-down/w:200/h:200/el:1/plain/https://dl4...5.5 KiB4.8 KiB

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: 802 ms

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

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 Evaluation2.3 s
Other631 ms
Script Parsing & Compilation314 ms
Style & Layout307 ms
Parse HTML & CSS82 ms
Rendering57 ms
Garbage Collection18 ms

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
MyMiniFactory logo div.footerInner > div.footer__mobile-bottom > a > img.footer__logo
www.myminifactory.com/images/footer/MMF_footer_logo.svg

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

●Layout shift culprits
●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 2,233 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 10 long tasks found
●Avoid non-composited animations 25 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 40 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 310 ms
○INP breakdown
○Avoid large layout shifts
85

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cart icon div.mmf-topbar-cart-container > div.mmf-cart-container > a.cart-button-container > i

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.

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
LOGIN div > div > div.mmf-user-menu-container > button
$32.99 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
$10.00 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
$4.90 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
VIEW ALL div.sc-bXdtCk > div.sc-bXdtCk > a.sc-llIIlC > div.sc-bXdtCk
$24.00 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
$1.00 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
UPCOMING div.sc-gwsNht > div.sc-bXdtCk > div.sc-bXdtCk > span.sc-jMpmlX
$8.00 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
NEW div.sc-gwsNht > div.sc-bXdtCk > div.sc-bXdtCk > span.sc-jMpmlX
VIEW ALL div.sc-bXdtCk > div.sc-bXdtCk > a.sc-llIIlC > div.sc-bXdtCk
$4.90 section.sc-fiuFiy > div.sc-bXdtCk > div.sc-bXdtCk > p.sc-dYttxY
Help/FAQ div.footer__container > div.footerInner > div.footer__mobile-top > a.footer__bottom-link
T&C div.footer__container > div.footerInner > div.footer__mobile-top > a.footer__bottom-link
Privacy Policy div.footer__container > div.footerInner > div.footer__mobile-top > a.footer__bottom-link
Sitemap div.footer__container > div.footerInner > div.footer__mobile-top > a.footer__bottom-link
Advertize div.footer__container > div.footerInner > div.footer__mobile-top > a.footer__bottom-link
Copyright, MyMiniFactory, 2026 / 51-53 Rivington Street, London, EC2A 3QN, Unit… div.footer__container > div.footerInner > div.footer__mobile-bottom > p.footer__company-address

These are opportunities to improve the legibility of your content.

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
div.outer-container > div > div > a div.outer-container > div > div > a

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Heading elements appear in a sequentially-descending order
●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.
○`[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
○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
○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

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
div > div > picture.sc-bxWfHM > img.sc-eCiCVF div > div > picture.sc-bxWfHM > img.sc-eCiCVF
/insecure/resizing_type:fill-down/enlarge:true/width:430/...412 x 412430 x 430618 x 618

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●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
●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
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
92

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
ENDING div.sc-bXdtCk > ul.sc-cUpKot > li.sc-eJfVlx > a
POPULAR div.sc-bXdtCk > ul.sc-cUpKot > li.sc-eJfVlx > a
COMING SOON div.sc-bXdtCk > ul.sc-cUpKot > li.sc-eJfVlx > a
PLEDGE MANAGER div.sc-bXdtCk > ul.sc-cUpKot > li.sc-eJfVlx > a

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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback