Skip to content
https://m.starmakerstudios.com/v/quick-recharge/official

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.

33

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.

RequestCache TTLTransfer Size
m.starmakerstudios.com/cdn/vue/fonts/PingFang-SC-Regular.otf604800.0 s10.3 MiB
m.starmakerstudios.com/cdn/vue/fonts/SF-Pro-Display-Semibold.otf604800.0 s328.1 KiB
m.starmakerstudios.com/cdn/vue/fonts/SF-Pro-Display-Medium.otf604800.0 s327.7 KiB
m.starmakerstudios.com/cdn/vue/fonts/SF-Pro-Display-Regular.otf604800.0 s292.0 KiB
/cdn/vue/agile-vue3/js/spa-quick-recharging/spa-quick-rec...604800.0 s54.8 KiB
/cdn/vue/js/h5-library/vue/3.4.21/vue.global.prod.js?vers...604800.0 s52.7 KiB
m.starmakerstudios.com/cdn/vue/agile-vue3/css/577.942d634ea48ef97323e9.css604800.0 s39.8 KiB
/cdn/vue/agile-vue3/js/vendors/vendors.92f18c2628113f1baa...604800.0 s29.3 KiB
/tools/im/0/production/statics/payment/361558bf2a69f40d.png2368166.0 s28.3 KiB
m.starmakerstudios.com/cdn/vue/agile-vue3/js/577/577.942d634ea48ef97323e9.js604800.0 s23.6 KiB
m.starmakerstudios.com/cdn/vue/agile-vue3/js/862/862.b32177920b1b7cdc7b77.js604800.0 s20.1 KiB
/cdn/vue/agile-vue3/views/spa-quick-recharging/web-sync/i...604800.0 s19.2 KiB
m.starmakerstudios.com/cdn/vue/agile-vue3/js/591/591.6e4b7b42007fbe02b933.js604800.0 s18.6 KiB
/cdn/vue/js/h5-library/axios/1.6.8/axios.min.js?version=1...604800.0 s15.0 KiB
/tools/im/0/production/statics/payment/55467c467dc6f903.png724035.0 s10.4 KiB
/cdn/vue/agile-vue3/js/main-chunk/main-chunk.fe0f1d2bf72c...604800.0 s9.9 KiB
/cdn/vue/js/h5-library/vue-router/4.3.0/vue-router.global...604800.0 s9.8 KiB
/tools/im/0/production/statics/payment/c0c30c7e26ca08df.jpg936915.0 s6.5 KiB
/cdn/vue/agile-vue3/views/spa-quick-recharging/web-sync/i...604800.0 s4.3 KiB
/cdn/vue/js/h5-library/pinia/3.0.4/pinia.iife.prod.js?ver...604800.0 s2.6 KiB
m.starmakerstudios.com/cdn/vue/js/h5-library/reset-css/0.0.3/index.css604800.0 s2.5 KiB
/cdn/vue/agile-vue3/css/main-chunk.fe0f1d2bf72cdaad7132.css604800.0 s2.1 KiB
m.starmakerstudios.com/cdn/vue/agile-vue3/css/908.533f0fbcfff4368f9bcf.css604800.0 s363 B
m.starmakerstudios.com/cdn/vue/agile-vue3/css/527.645f894934a433d9ebd5.css604800.0 s362 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.252185] map[node:map[boundingRect:map[bottom:1227 height:454 left:0 right:412 top:774 width:412] lhId:page-2-DIV nodeLabel:Notice to Users ①Don’t purchase StarMaker coins through unofficial or unauthor… path:1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,6,DIV selector:div#app > div#app > div.index > div.ContactBox snippet:<div data-v-55b2ff7f="" class="ContactBox"> type:node] score:0.217378 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:415 height:26 left:363 right:389 top:389 width:26] lhId:page-7-IMG nodeLabel:div.AreaDetail > div.main_head > p.changeArea > img path:1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,P,1,IMG selector:div.AreaDetail > div.main_head > p.changeArea > img snippet:<img data-v-b1dcca90="" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAAXNS…" alt=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1227 height:454 left:0 right:412 top:774 width:412] lhId:page-2-DIV nodeLabel:Notice to Users ①Don’t purchase StarMaker coins through unofficial or unauthor… path:1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,6,DIV selector:div#app > div#app > div.index > div.ContactBox snippet:<div data-v-55b2ff7f="" class="ContactBox"> type:node] score:0.034792 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:765 height:75 left:22 right:390 top:690 width:368] lhId:page-6-IMG nodeLabel:div#app > div.index > div.bg-img > img path:1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,5,DIV,0,IMG selector:div#app > div.index > div.bg-img > img snippet:<img data-v-55b2ff7f="" src="/cdn/vue/agile-vue3/views/spa-quick-recharging/web-sync/img/image2-424b2.p…" alt=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:111 height:13 left:295 right:394 top:98 width:99] lhId:page-1-DIV nodeLabel:What's StarMaker ID? path:1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV selector:div.index > div.myhead > div.account_tips > div.changeAccount snippet:<div data-v-2b35beba="" class="changeAccount"> type:node] score:1.5e-05 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:765 height:75 left:22 right:390 top:690 width:368] lhId:page-6-IMG nodeLabel:div#app > div.index > div.bg-img > img path:1,HTML,1,BODY,5,DIV,0,DIV,0,DIV,0,DIV,5,DIV,0,IMG selector:div#app > div.index > div.bg-img > img snippet:<img data-v-55b2ff7f="" src="/cdn/vue/agile-vue3/views/spa-quick-recharging/web-sync/img/image2-424b2.p…" alt=""> type:node]]] type:subitems]]]

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.

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

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.

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
div.logoBox > div.logoW > div.imgBox > img div.logoBox > div.logoW > div.imgBox > img
/tools/im/0/production/statics/payment/361558bf2a69f40d.png28.1 KiB27.5 KiB
div.logoBox > div.logoW > div.imgBox > img div.logoBox > div.logoW > div.imgBox > img
/tools/im/0/production/statics/payment/55467c467dc6f903.png10.3 KiB10.0 KiB
div.logoBox > div.logoW > div.imgBox > img div.logoBox > div.logoW > div.imgBox > img
/tools/im/0/production/statics/payment/c0c30c7e26ca08df.jpg6.3 KiB5.6 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.

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Notice to Users ①Don’t purchase StarMaker coins through unofficial or unauthor… div#app > div#app > div.index > div.ContactBox
0.217
Notice to Users ①Don’t purchase StarMaker coins through unofficial or unauthor… div#app > div#app > div.index > div.ContactBox
0.035
What's StarMaker ID? div.index > div.myhead > div.account_tips > div.changeAccount
0.000

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 Evaluation1.3 s
Other1.2 s
Script Parsing & Compilation191 ms
Style & Layout181 ms
Rendering44 ms
Parse HTML & CSS23 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 7.5 KiB

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: 0.0 ms 34.5 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
div#app > div.index > div.bg-img > img div#app > div.index > div.bg-img > img
/cdn/vue/agile-vue3/views/spa-quick-recharging/web-sync/i...
div.AreaDetail > div.main_head > p.changeArea > img div.AreaDetail > div.main_head > p.changeArea > img

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

●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 1 animated element found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 220 ms
●Server Backend Latencies 230 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 240 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
69

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
What's StarMaker ID? div.index > div.myhead > div.account_tips > div.changeAccount
Change div > div.AccountType > div.main > div.btn
Confirm div > div.AccountType > div > div.btnW
1USD div.logoBox > div.channelW > div.tip > span
79 div.logoBox > div.channelW > div.tip > span
1USD div.logoBox > div.channelW > div.tip > span
80 div.logoBox > div.channelW > div.tip > span
1USD div.logoBox > div.channelW > div.tip > span
80 div.logoBox > div.channelW > div.tip > span
【Terms of Service】 div.index > div.ContactBox > div.term-policy > span
【Privacy Policy】 div.index > div.ContactBox > div.term-policy > span

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#app > div.index > div.channel > li div#app > div.index > div.channel > li
Visa / Master / American Express / Diners / Discover 1USD ≈ 79 div#app > div.index > div.channel > li
Payoneer 1USD ≈ 80 div#app > div.index > div.channel > li
Epay 1USD ≈ 80 div#app > div.index > div.channel > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Form elements have associated labels
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○Links have a discernible name
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
66

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
https://m.starmakerstudios.com/robots.txt

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

○Structured data is valid
●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