Moyin.com Site Title

魔音工坊--达人热推的短视频/有声书AI配音平台

Moyin.com Meta Description

魔音工坊是一款可以在线将文字转成语音的智能配音产品。提供不同性别、不同口音的真人声音,在您输入文字后直接生成音频。您可快速对短视频等需要配音的内容进行配音。是一款功能强大AI语音合成神器。

Moyin.com Test Results

Moyin.com Mobile Performance: 55/100
Quick overview:
Time to Interactive
60.2 s
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.
First Meaningful Paint
60.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 1,515 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Reduce unused CSS
Potential savings of 255 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.
Eliminate render-blocking resources
Potential savings of 3,560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Largest Contentful Paint element
76,270 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Enable text compression
Potential savings of 263 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid multiple page redirects
Potential savings of 24,850 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid enormous network payloads
Total size was 14,551 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Reduce the impact of third-party code
Third-party code blocked the main thread for 6,180 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Serve static assets with an efficient cache policy
20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minimize main-thread work
14.7 s
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
Reduce JavaScript execution time
6.2 s
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.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

Moyin.com Mobile SEO: 64/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
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

Moyin.com Mobile Best Practices: 55/100
Quick overview:
General
Browser errors were logged to the console
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
Missing source maps for large first-party JavaScript
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.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Trust and Safety
Does not use HTTPS
3 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
Moyin.com Mobile Accessibility: 41/100
Quick overview:
Names and labels
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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
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.
Similar tests
www.moyin.com
www.moyin.net
www.moyin.org
www.moyin.info
www.moyin.biz
www.moyin.us
www.moyin.mobi
www.oyin.com
www.moyin.com
www.noyin.com
www.mnoyin.com
www.nmoyin.com
www.joyin.com
www.mjoyin.com
www.jmoyin.com
www.koyin.com
www.mkoyin.com
www.kmoyin.com
www.myin.com
www.miyin.com
www.moiyin.com
www.mioyin.com
www.mkyin.com
www.mokyin.com
www.mlyin.com
www.molyin.com
www.mloyin.com
www.mpyin.com
www.mopyin.com
www.mpoyin.com
www.moin.com
www.motin.com
www.moytin.com
www.motyin.com
www.mogin.com
www.moygin.com
www.mogyin.com
www.mohin.com
www.moyhin.com
www.mohyin.com
www.mouin.com
www.moyuin.com
www.mouyin.com
www.moyn.com
www.moyun.com
www.moyiun.com
www.moyjn.com
www.moyijn.com
www.moyjin.com
www.moykn.com
www.moyikn.com
www.moykin.com
www.moyon.com
www.moyion.com
www.moyoin.com
www.moyi.com
www.moyib.com
www.moyinb.com
www.moyibn.com
www.moyih.com
www.moyinh.com
www.moyihn.com
www.moyij.com
www.moyinj.com
www.moyim.com
www.moyinm.com
www.moyimn.com
www.moyin.con
Last Tested: