jiepaivip.com

jiepaivip.com may not be SSL secured

Free website and domain report on jiepaivip.com

Last Updated: 3rd December, 2022 Update Now
Overview

Snoop Summary for jiepaivip.com

This is a free and comprehensive report about jiepaivip.com. The domain jiepaivip.com is currently hosted on a server located in Central, Central and Western District in Hong Kong with the IP address 128.1.138.159, where HKD is the local currency and the local language is English. Our records indicate that jiepaivip.com is owned/operated by jiepaivip. If jiepaivip.com was to be sold it would possibly only be worth $10 USD (the typical cost of the registration fee for the domain name). This report was last updated 3rd December, 2022.

About jiepaivip.com

Site Preview: jiepaivip.com jiepaivip.com
Title:
Description:
Keywords and Tags: bulletin boards, forum
Related Terms:
Fav Icon:
Age: Over 12 years old
Domain Created: 23rd November, 2011
Domain Updated: 26th October, 2022
Domain Expires: 23rd November, 2023
Review

Snoop Score

1/5

Valuation

$10 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 10,073,565
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 1
Moz Page Authority: 25

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 0
Monthly Visitors: 0
Yearly Visitors: 0
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $0 USD
Yearly Revenue: $0 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: jiepaivip.com 13
Domain Name: jiepaivip 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 98
Accessibility 91
Best Practices 62
SEO 80
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for jiepaivip.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://jiepaivip.com/
http/1.1
0
221.13099996932
559
430
200
text/html
Document
https://xiao1.xiao301.org:1101/?u=http://jiepaivip.com/&p=/
http/1.1
249.14900003932
641.52699988335
514
0
302
text/html
https://www.aaokok.com/?jiepaivip1
h2
641.86499989592
1867.1299999114
2043
4376
200
text/html
Document
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
http/1.1
1893.4400000144
3167.7629998885
13775
36277
200
application/javascript
Script
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
h2
1894.3270000163
2454.6769999433
72895
72326
200
application/javascript
Script
https://pic.zhifuok.com/yes/yindaozhanbeijing.gif
h2
1897.2030000295
2572.2459999379
5952
5368
200
image/gif
Image
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=800x600&vl=940&et=0&ja=0&ln=en-us&lo=0&rnd=813100737&si=47cf7c8db9bdb0690c697413fe0d8444&su=http%3A%2F%2Fjiepaivip.com%2F&v=1.2.89&lv=1&sn=30162&r=0&ww=1350&ct=!!&u=https%3A%2F%2Fwww.aaokok.com%2F%3Fjiepaivip1&tt=%E8%A1%97%E6%8B%8D%E8%99%8E
http/1.1
3193.1559999939
4841.3839999121
299
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
275.848
9.409
1922.119
9.383
1937.494
8.035
1945.539
58.336
2512.972
18.456
3220.876
21.3
5532.127
8.66
5596.346
11.459
5906.451
41.532
5964.224
9.93
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Jiepaivip.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Jiepaivip.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Jiepaivip.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Jiepaivip.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Jiepaivip.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Jiepaivip.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 53 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
72895
54004
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 47 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
72326
47635
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Jiepaivip.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 94 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
72895
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
13775
https://pic.zhifuok.com/yes/yindaozhanbeijing.gif
5952
https://www.aaokok.com/?jiepaivip1
2043
http://jiepaivip.com/
559
https://xiao1.xiao301.org:1101/?u=http://jiepaivip.com/&p=/
514
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=800x600&vl=940&et=0&ja=0&ln=en-us&lo=0&rnd=813100737&si=47cf7c8db9bdb0690c697413fe0d8444&su=http%3A%2F%2Fjiepaivip.com%2F&v=1.2.89&lv=1&sn=30162&r=0&ww=1350&ct=!!&u=https%3A%2F%2Fwww.aaokok.com%2F%3Fjiepaivip1&tt=%E8%A1%97%E6%8B%8D%E8%99%8E
299
Avoids an excessive DOM size — 11 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
11
Maximum DOM Depth
5
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Jiepaivip.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.aaokok.com/?jiepaivip1
104.118
14.118
7.468
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
88.498
78.748
0.627
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
116.928
Style & Layout
55.594
Other
45.355
Script Parsing & Compilation
13.793
Parse HTML & CSS
8.574
Rendering
6.121
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 7 requests • 94 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
7
96037
Script
2
86670
Image
2
6251
Document
2
2602
Other
1
514
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
6
93994
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
14074
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of jiepaivip.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 1.6 s
The time taken for the page contents to be visibly populated.

Other

Avoid multiple page redirects — Potential savings of 420 ms
Redirects can cause additional delays before the page can begin loading. Jiepaivip.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://jiepaivip.com/
190
https://xiao1.xiao301.org:1101/?u=http://jiepaivip.com/&p=/
230
https://www.aaokok.com/?jiepaivip1
0
Serve static assets with an efficient cache policy — 2 resources found
Jiepaivip.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
0
72895
https://pic.zhifuok.com/yes/yindaozhanbeijing.gif
0
5952

Other

Reduce initial server response time — Root document took 1,230 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.aaokok.com/?jiepaivip1
1226.257
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of jiepaivip.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Jiepaivip.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
62

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that jiepaivip.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.4.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://jiepaivip.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
7
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Charset declaration is missing or occurs too late in the HTML
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
80

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for jiepaivip.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of jiepaivip.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 5 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<script>
Syntax not understood
2
<!--
Syntax not understood
3
document.write(unescape("%3C%21DOCTYPE%20html%3E%0A%3Chtml%20lang%3D%22en%22%3E%0A%0A%3Chead%3E%0A%20%20%20%20%3Cmeta%20charset%3D%22UTF-8%22%3E%0A%20%20%20%20%3Ctitle%3E%u8857%u62CD%u864E%3C/title%3E%0A%20%20%20%20%3Cmeta%20http-equiv%3D%22X-UA-Compatible%22%20content%3D%22IE%3Dedge%22%3E%0A%20%20%20%20%3Cmeta%20name%3D%22viewport%22%20content%3D%22width%3Ddevice-width%2C%20initial-scale%3D1.0%22%3E%0A%20%20%20%20%3Ctitle%3E%3C/title%3E%0A%20%20%20%20%3Cstyle%3E%0A%20%20%20%20%20%20%20%20html%2C%0A%20%20%20%20%20%20%20%20body%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20height%3A%20100%25%3B%0A%20%20%20%20%20%20%20%20%7D%0A%0A%20%20%20%20%20%20%20%20body%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20background%3A%20url%28//pic.zhifuok.com/yes/yindaozhanbeijing.gif%29%3B%0A%20%20%20%20%20%20%20%20%7D%0A%0A%20%20%20%20%20%20%20%20a%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20text-decoration%3A%20none%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%3C/style%3E%0A%3Cscript%3E%0Avar%20_hmt%20%3D%20_hmt%20%7C%7C%20%5B%5D%3B%0A%28function%28%29%20%7B%0A%20%20var%20hm%20%3D%20document.createElement%28%22script%22%29%3B%0A%20%20hm.src%20%3D%20%22https%3A//hm.baidu.com/hm.js%3F47cf7c8db9bdb0690c697413fe0d8444%22%3B%0A%20%20var%20s%20%3D%20document.getElementsByTagName%28%22script%22%29%5B0%5D%3B%20%0A%20%20s.parentNode.insertBefore%28hm%2C%20s%29%3B%0A%7D%29%28%29%3B%0A%3C/script%3E%0A%3C/head%3E%0A%0A%3Cbody%3E%0A%20%20%20%20%3Cdiv%0A%20%20%20%20%20%20%20%20style%3D%22position%3A%20fixed%3Btop%3A%200px%3Bleft%3A%200px%3Bright%3A%200px%3Bbottom%3A%200px%3Bmargin%3A%20auto%3Bwidth%3A324px%3Bheight%3A%20300px%3Bfont-size%3A25px%3Bline-height%3A40px%3B%22%3E%0A%20%20%20%20%20%20%20%20%3Cdiv%20style%3D%22background%3A%20%23ff0101%3Btext-align%3A%20center%3Bpadding%3A20px%3Bcolor%3A%20%23f6f3ee%3Bborder-radius%3A5px%3B%22%3E%3Cspan%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20id%3D%22referrer%22%3E%u5F53%u524D%u57DF%u540D%u5373%u5C06%u5931%u6548%3Cbr%3E%u52A1%u5FC5%u4FDD%u5B58%u4EE5%u4E0B%u57DF%u540D%3Cbr%3E%3C/span%3E%u2193%u6C38%u4E45%u57DF%u540D%u2193%3Cbr%3Ewww.xxokok.com%3C/div%3E%0A%20%20%20%20%20%20%20%20%3Cdiv%20style%3D%22background%3A%20%236bc30d%3Btext-align%3A%20center%3Bpadding%3A10px%3Bcolor%3A%20%23f6f3ee%3Bmargin-top%3A%2020px%3Bcursor%3A%20pointer%3B%22%20onclick%3D%22openurl%28%29%22%3E%u70B9%20%u51FB%20%u8BBF%20%u95EE%3C/div%3E%0A%20%20%20%20%3C/div%3E%0A%20%20%20%20%3Cscript%3E%0A%20%20%20%20%20%20%20%20var%20url1%20%3D%20%27http%3A//%27%2C%20url2%20%3D%20%27301%27%2C%20url3%20%3D%20%27oksizu%27%2C%20url4%20%3D%20%27com%27%3B%0A%20%20%20%20%20%20%20%20var%20url5%20%3D%20%27https%3A//%27%2C%20url6%20%3D%20%27www%27%2C%20url7%20%3D%20%27ddokok%27%2C%20url8%20%3D%20%27com%27%3B%0A%20%20%20%20%20%20%20%20var%20url%20%3D%20url1%20+%20url2%20+%20%27.%27%20+%20url3%20+%20%27.%27%20+%20url4%3B%0A%20%20%20%20%20%20%20%20if%20%28document.referrer%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20//document.getElementById%28%27referrer%27%29.innerHTML%20%3D%20%27%27%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20var%20str%20%3D%20location.href%3B%0A%20%20%20%20%20%20%20%20var%20num%20%3D%20str.indexOf%28%22%3F%22%29%0A%20%20%20%20%20%20%20%20if%20%28num%20%3E%3D%200%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20str%20%3D%20str.substr%28num%20+%201%29%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20url%20%3D%20url5%20+%20url6%20+%20%27.%27%20+%20url7%20+%20%27.%27%20+%20url8%20+%20%27/%3Fhmsr%3D%27%20+%20str%20+%20%27%26hmpl%3D%26hmcu%3D%26hmkw%3D%26hmci%3D%27%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20function%20openurl%28%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20window.location.href%20%3D%20url%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%3C/script%3E%0A%20%20%20%20%3Cscript%20src%3D%22//zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js%22%3E%3C/script%3E%0A%20%20%20%20%3Cscript%20type%3D%22text/javascript%22%3E%0A%20%20%20%20%20%20%20%20setInterval%28%22removead%28%29%22%2C%201000%29%3B%0A%20%20%20%20%20%20%20%20function%20removead%28%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%24%28%27%23adline%27%29.nextAll%28%29.remove%28%29%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%3C/script%3E%0A%20%20%20%20%3Cdiv%20id%3D%22adline%22%20style%3D%22display%3Anone%3B%22%3E%u8857%u62CD%3C/div%3E%0A%3C/body%3E%0A%0A%3C/html%3E"));
Syntax not understood
4
//-->
Syntax not understood
5
</script>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of jiepaivip.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of jiepaivip.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 72
Performance 96
Accessibility 91
Best Practices 62
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
96

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for jiepaivip.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 2.2 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 1.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://jiepaivip.com/
http/1.1
0
67.06800009124
559
430
200
text/html
Document
https://xiao1.xiao301.org:1101/?u=http://jiepaivip.com/&p=/
http/1.1
82.517000031658
425.81100005191
499
0
302
text/html
https://www.aaokok.com/?jiepaivip1
h2
426.23600002844
1674.0090000676
1652
4376
200
text/html
Document
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
http/1.1
1693.8760000048
2977.8090000618
13775
36277
200
application/javascript
Script
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
h2
1694.8580000317
2273.2100000139
72888
72326
200
application/javascript
Script
https://pic.zhifuok.com/yes/yindaozhanbeijing.gif
h2
1696.0840000538
2574.2450000253
5946
5368
200
image/gif
Image
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=360x640&vl=640&et=0&ja=0&ln=en-us&lo=0&rnd=1211564404&si=47cf7c8db9bdb0690c697413fe0d8444&su=http%3A%2F%2Fjiepaivip.com%2F&v=1.2.89&lv=1&sn=30180&r=0&ww=360&ct=!!&u=https%3A%2F%2Fwww.aaokok.com%2F%3Fjiepaivip1&tt=%E8%A1%97%E6%8B%8D%E8%99%8E
http/1.1
2995.6720001064
4064.7850000532
299
43
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
111.192
8.386
1717.926
6.94
1725.391
6.986
1736.73
19.301
2321.139
9.094
3023.858
13.146
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Jiepaivip.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Jiepaivip.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Jiepaivip.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Jiepaivip.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Jiepaivip.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Jiepaivip.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Jiepaivip.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 93 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
72888
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
13775
https://pic.zhifuok.com/yes/yindaozhanbeijing.gif
5946
https://www.aaokok.com/?jiepaivip1
1652
http://jiepaivip.com/
559
https://xiao1.xiao301.org:1101/?u=http://jiepaivip.com/&p=/
499
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=360x640&vl=640&et=0&ja=0&ln=en-us&lo=0&rnd=1211564404&si=47cf7c8db9bdb0690c697413fe0d8444&su=http%3A%2F%2Fjiepaivip.com%2F&v=1.2.89&lv=1&sn=30180&r=0&ww=360&ct=!!&u=https%3A%2F%2Fwww.aaokok.com%2F%3Fjiepaivip1&tt=%E8%A1%97%E6%8B%8D%E8%99%8E
299
Avoids an excessive DOM size — 11 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
11
Maximum DOM Depth
5
Maximum Child Elements
5
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Jiepaivip.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.aaokok.com/?jiepaivip1
185.652
30.568
14.12
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
86.748
76.892
2.836
Unattributable
76.532
10.864
0.76
Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
155.184
Other
119.164
Style & Layout
77.6
Script Parsing & Compilation
24.168
Rendering
11.484
Parse HTML & CSS
11.46
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 7 requests • 93 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
7
95618
Script
2
86663
Image
2
6245
Document
2
2211
Other
1
499
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
6
93966
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
14074
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://hm.baidu.com/hm.js?47cf7c8db9bdb0690c697413fe0d8444
3120
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of jiepaivip.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 4.5 s
The time taken for the page contents to be visibly populated.

Other

Reduce unused JavaScript — Potential savings of 53 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
72888
53998
Enable text compression — Potential savings of 47 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
72326
47635
Serve static assets with an efficient cache policy — 2 resources found
Jiepaivip.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js
0
72888
https://pic.zhifuok.com/yes/yindaozhanbeijing.gif
0
5946
First Contentful Paint (3G) — 2767 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Other

Reduce initial server response time — Root document took 1,250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.aaokok.com/?jiepaivip1
1248.768
Avoid multiple page redirects — Potential savings of 1,410 ms
Redirects can cause additional delays before the page can begin loading. Jiepaivip.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://jiepaivip.com/
630
https://xiao1.xiao301.org:1101/?u=http://jiepaivip.com/&p=/
780
https://www.aaokok.com/?jiepaivip1
0
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of jiepaivip.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Jiepaivip.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
62

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that jiepaivip.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.4.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://jiepaivip.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
7
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Charset declaration is missing or occurs too late in the HTML
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for jiepaivip.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of jiepaivip.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 5 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<script>
Syntax not understood
2
<!--
Syntax not understood
3
document.write(unescape("%3C%21DOCTYPE%20html%3E%0A%3Chtml%20lang%3D%22en%22%3E%0A%0A%3Chead%3E%0A%20%20%20%20%3Cmeta%20charset%3D%22UTF-8%22%3E%0A%20%20%20%20%3Ctitle%3E%u8857%u62CD%u864E%3C/title%3E%0A%20%20%20%20%3Cmeta%20http-equiv%3D%22X-UA-Compatible%22%20content%3D%22IE%3Dedge%22%3E%0A%20%20%20%20%3Cmeta%20name%3D%22viewport%22%20content%3D%22width%3Ddevice-width%2C%20initial-scale%3D1.0%22%3E%0A%20%20%20%20%3Ctitle%3E%3C/title%3E%0A%20%20%20%20%3Cstyle%3E%0A%20%20%20%20%20%20%20%20html%2C%0A%20%20%20%20%20%20%20%20body%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20height%3A%20100%25%3B%0A%20%20%20%20%20%20%20%20%7D%0A%0A%20%20%20%20%20%20%20%20body%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20background%3A%20url%28//pic.zhifuok.com/yes/yindaozhanbeijing.gif%29%3B%0A%20%20%20%20%20%20%20%20%7D%0A%0A%20%20%20%20%20%20%20%20a%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20text-decoration%3A%20none%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%3C/style%3E%0A%3Cscript%3E%0Avar%20_hmt%20%3D%20_hmt%20%7C%7C%20%5B%5D%3B%0A%28function%28%29%20%7B%0A%20%20var%20hm%20%3D%20document.createElement%28%22script%22%29%3B%0A%20%20hm.src%20%3D%20%22https%3A//hm.baidu.com/hm.js%3F47cf7c8db9bdb0690c697413fe0d8444%22%3B%0A%20%20var%20s%20%3D%20document.getElementsByTagName%28%22script%22%29%5B0%5D%3B%20%0A%20%20s.parentNode.insertBefore%28hm%2C%20s%29%3B%0A%7D%29%28%29%3B%0A%3C/script%3E%0A%3C/head%3E%0A%0A%3Cbody%3E%0A%20%20%20%20%3Cdiv%0A%20%20%20%20%20%20%20%20style%3D%22position%3A%20fixed%3Btop%3A%200px%3Bleft%3A%200px%3Bright%3A%200px%3Bbottom%3A%200px%3Bmargin%3A%20auto%3Bwidth%3A324px%3Bheight%3A%20300px%3Bfont-size%3A25px%3Bline-height%3A40px%3B%22%3E%0A%20%20%20%20%20%20%20%20%3Cdiv%20style%3D%22background%3A%20%23ff0101%3Btext-align%3A%20center%3Bpadding%3A20px%3Bcolor%3A%20%23f6f3ee%3Bborder-radius%3A5px%3B%22%3E%3Cspan%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20id%3D%22referrer%22%3E%u5F53%u524D%u57DF%u540D%u5373%u5C06%u5931%u6548%3Cbr%3E%u52A1%u5FC5%u4FDD%u5B58%u4EE5%u4E0B%u57DF%u540D%3Cbr%3E%3C/span%3E%u2193%u6C38%u4E45%u57DF%u540D%u2193%3Cbr%3Ewww.xxokok.com%3C/div%3E%0A%20%20%20%20%20%20%20%20%3Cdiv%20style%3D%22background%3A%20%236bc30d%3Btext-align%3A%20center%3Bpadding%3A10px%3Bcolor%3A%20%23f6f3ee%3Bmargin-top%3A%2020px%3Bcursor%3A%20pointer%3B%22%20onclick%3D%22openurl%28%29%22%3E%u70B9%20%u51FB%20%u8BBF%20%u95EE%3C/div%3E%0A%20%20%20%20%3C/div%3E%0A%20%20%20%20%3Cscript%3E%0A%20%20%20%20%20%20%20%20var%20url1%20%3D%20%27http%3A//%27%2C%20url2%20%3D%20%27301%27%2C%20url3%20%3D%20%27oksizu%27%2C%20url4%20%3D%20%27com%27%3B%0A%20%20%20%20%20%20%20%20var%20url5%20%3D%20%27https%3A//%27%2C%20url6%20%3D%20%27www%27%2C%20url7%20%3D%20%27ddokok%27%2C%20url8%20%3D%20%27com%27%3B%0A%20%20%20%20%20%20%20%20var%20url%20%3D%20url1%20+%20url2%20+%20%27.%27%20+%20url3%20+%20%27.%27%20+%20url4%3B%0A%20%20%20%20%20%20%20%20if%20%28document.referrer%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20//document.getElementById%28%27referrer%27%29.innerHTML%20%3D%20%27%27%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20var%20str%20%3D%20location.href%3B%0A%20%20%20%20%20%20%20%20var%20num%20%3D%20str.indexOf%28%22%3F%22%29%0A%20%20%20%20%20%20%20%20if%20%28num%20%3E%3D%200%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20str%20%3D%20str.substr%28num%20+%201%29%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20url%20%3D%20url5%20+%20url6%20+%20%27.%27%20+%20url7%20+%20%27.%27%20+%20url8%20+%20%27/%3Fhmsr%3D%27%20+%20str%20+%20%27%26hmpl%3D%26hmcu%3D%26hmkw%3D%26hmci%3D%27%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20function%20openurl%28%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20window.location.href%20%3D%20url%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%3C/script%3E%0A%20%20%20%20%3Cscript%20src%3D%22//zhuye.zhifuok.com/qq32593992/ok/zhuye/anniu/jquery1.42.min.js%22%3E%3C/script%3E%0A%20%20%20%20%3Cscript%20type%3D%22text/javascript%22%3E%0A%20%20%20%20%20%20%20%20setInterval%28%22removead%28%29%22%2C%201000%29%3B%0A%20%20%20%20%20%20%20%20function%20removead%28%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%24%28%27%23adline%27%29.nextAll%28%29.remove%28%29%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%3C/script%3E%0A%20%20%20%20%3Cdiv%20id%3D%22adline%22%20style%3D%22display%3Anone%3B%22%3E%u8857%u62CD%3C/div%3E%0A%3C/body%3E%0A%0A%3C/html%3E"));
Syntax not understood
4
//-->
Syntax not understood
5
</script>
Syntax not understood

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
30

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of jiepaivip.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of jiepaivip.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 128.1.138.159
Continent: Asia
Country: Hong Kong
Hong Kong Flag
Region: Central and Western District
City: Central
Longitude: 114.146
Latitude: 22.2795
Currencies: HKD
Languages: English
Chinese

Web Hosting Provider

Name IP Address
UCLOUD
Registration

Domain Registrant

Private Registration: No
Name: jiepai vip
Organization: jiepaivip
Country: CN
City: beijing
State: china
Post Code: 110011
Email:
Phone: Non-Public Data
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Name.com, Inc. 104.18.7.161
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
jiepaivip.com. 103.72.144.3 IN 600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 3rd December, 2022
Content-Type: text/html
Content-Length: 5521
Last-Modified: 6th November, 2022
Connection: keep-alive
Vary: Accept-Encoding
ETag: "6367dec4-1591"
Accept-Ranges: bytes

Whois Lookup

Created: 23rd November, 2011
Changed: 26th October, 2022
Expires: 23rd November, 2023
Registrar: Name.com, Inc.
Status: clientTransferProhibited
Nameservers: ns1.alidns.com
ns2.alidns.com
Owner Name: jiepai vip
Owner Organization: jiepaivip
Owner Street: beijing
Owner Post Code: 110011
Owner City: beijing
Owner State: china
Owner Country: CN
Owner Phone: Non-Public Data
Owner Email: https://www.name.com/contact-domain-whois/jiepaivip.com/registrant
Admin Name: jiepai vip
Admin Organization: jiepaivip
Admin Street: beijing
Admin Post Code: 110011
Admin City: beijing
Admin State: china
Admin Country: CN
Admin Phone: Non-Public Data
Admin Email: https://www.name.com/contact-domain-whois/jiepaivip.com/admin
Tech Name: jiepai vip
Tech Organization: jiepaivip
Tech Street: beijing
Tech Post Code: 110011
Tech City: beijing
Tech State: china
Tech Country: CN
Tech Phone: Non-Public Data
Tech Email: https://www.name.com/contact-domain-whois/jiepaivip.com/tech
Full Whois: Domain Name: JIEPAIVIP.COM
Registry Domain ID: 1688631478_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2022-10-26T16:41:21Z
Creation Date: 2011-11-23T18:19:07Z
Registrar Registration Expiration Date: 2023-11-23T18:19:07Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Reseller:
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: jiepai vip
Registrant Organization: jiepaivip
Registrant Street: beijing
Registrant City: beijing
Registrant State/Province: china
Registrant Postal Code: 110011
Registrant Country: CN
Registrant Phone: Non-Public Data
Registrant Email: https://www.name.com/contact-domain-whois/jiepaivip.com/registrant
Registry Admin ID: Not Available From Registry
Admin Name: jiepai vip
Admin Organization: jiepaivip
Admin Street: beijing
Admin City: beijing
Admin State/Province: china
Admin Postal Code: 110011
Admin Country: CN
Admin Phone: Non-Public Data
Admin Email: https://www.name.com/contact-domain-whois/jiepaivip.com/admin
Registry Tech ID: Not Available From Registry
Tech Name: jiepai vip
Tech Organization: jiepaivip
Tech Street: beijing
Tech City: beijing
Tech State/Province: china
Tech Postal Code: 110011
Tech Country: CN
Tech Phone: Non-Public Data
Tech Email: https://www.name.com/contact-domain-whois/jiepaivip.com/tech
Name Server: ns1.alidns.com
Name Server: ns2.alidns.com
DNSSEC: unSigned
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: +1.7203101849
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-12-03T15:57:05Z <<<

For more information on Whois status codes, please visit https://icann.org/epp


The data in the Name.com, Inc. WHOIS database is provided by Name.com, Inc. for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Name.com, Inc. does not guarantee its accuracy. Users accessing the Name.com, Inc. WHOIS service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Name.com, Inc., except as reasonably necessary to register domain names or modify existing registrations. When using the Name.com, Inc. WHOIS service, please consider the following: the WHOIS service is not a replacement for standard EPP commands to the SRS service. WHOIS is not considered authoritative for registered domain objects. The WHOIS service may be scheduled for downtime during production or OT&E maintenance periods. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis, for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://www.name.com/layered-access-request . Name.com, Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.



Nameservers

Name IP Address
ns1.alidns.com 47.118.199.215
ns2.alidns.com 139.224.142.126
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address