Lilith.com Site Title

莉莉丝游戏

Lilith.com Meta Description

莉莉丝游戏是中国中生代游戏公司代表,在中国游戏市场保持领先地位。莉莉丝游戏自主研发运营多款精品游戏,包括《末世余晖》、《战火勋章》、《剑与远征》、《万国觉醒》、《剑与家园》、《艾彼》、《迷失岛2:时间的灰烬》、《小冰冰传奇》、《南瓜先生2九龙城寨》等。简单真诚是莉莉丝游戏的价值观,期待你加入莉莉丝,一起做好玩的游戏,一起为了游戏行业美好的未来贡献自己的力量!

Lilith.com Test Results

Lilith.com Mobile Performance: 47/100
Quick overview:
Max Potential First Input Delay
660 ms
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.
First Meaningful Paint
7.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
15.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.
Script Treemap Data
Used for treemap app
Diagnostics
Collection of useful page vitals.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Final Screenshot
The last screenshot captured of the pageload.

287979030378

Server Backend Latencies
270 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Metrics
Collects all available metrics.
Network Requests
Lists the network requests that were made during page load.
Network Round Trip Times
140 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.

Lilith.com Mobile SEO: 75/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.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn how to make pages mobile-friendly.
Tap targets are not sized appropriately
81% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.
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
robots.txt is not valid
34 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Lilith.com Mobile Best Practices: 0/100
Quick overview:
Browser Compatibility
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Trust and Safety
Does not use HTTPS
18 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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Lilith.com Mobile PWA: 38/100
Quick overview:
PWA Optimized
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons. No manifest was fetched
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Lilith.com Mobile Accessibility: 58/100
Quick overview:
ARIA
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.
`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
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 have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
Touch targets have sufficient size and spacing.
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.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
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.
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.
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.lilith.com
www.lilith.net
www.lilith.org
www.lilith.info
www.lilith.biz
www.lilith.us
www.lilith.mobi
www.ilith.com
www.lilith.com
www.pilith.com
www.lpilith.com
www.plilith.com
www.oilith.com
www.loilith.com
www.olilith.com
www.kilith.com
www.lkilith.com
www.klilith.com
www.llith.com
www.lulith.com
www.liulith.com
www.luilith.com
www.ljlith.com
www.lijlith.com
www.ljilith.com
www.lklith.com
www.liklith.com
www.lolith.com
www.liolith.com
www.liith.com
www.lipith.com
www.lilpith.com
www.liplith.com
www.lioith.com
www.liloith.com
www.likith.com
www.lilkith.com
www.lilth.com
www.liluth.com
www.liliuth.com
www.liluith.com
www.liljth.com
www.lilijth.com
www.liljith.com
www.lilkth.com
www.lilikth.com
www.liloth.com
www.lilioth.com
www.lilih.com
www.lilirh.com
www.lilitrh.com
www.lilirth.com
www.lilifh.com
www.lilitfh.com
www.lilifth.com
www.liligh.com
www.lilitgh.com
www.liligth.com
www.liliyh.com
www.lilityh.com
www.liliyth.com
www.lilit.com
www.lilitb.com
www.lilithb.com
www.lilitbh.com
www.lilitg.com
www.lilithg.com
www.lility.com
www.lilithy.com
www.lilitu.com
www.lilithu.com
www.lilituh.com
www.lilitj.com
www.lilithj.com
www.lilitjh.com
www.lilitn.com
www.lilithn.com
www.lilitnh.com
www.lilith.con
Last Tested: