usagipoi.net

usagipoi.net may not be SSL secured

Free website and domain report on usagipoi.net

Last Updated: 26th September, 2023 Update Now
Overview

Snoop Summary for usagipoi.net

This is a free and comprehensive report about usagipoi.net. The domain usagipoi.net is currently hosted on a server located in United States with the IP address 199.59.243.223, where the local currency is USD and English is the local language. Our records indicate that usagipoi.net is privately registered by REDACTED FOR PRIVACY. If usagipoi.net 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 26th September, 2023.

About usagipoi.net

Site Preview: usagipoi.net usagipoi.net
Title:
Description: 米表网是聚名网旗下的域名批量管理展示网站,米表网不仅仅只是米表,同时米表网为域名投资者提供了多种域名出售页面、量身定制的米表管理系统,解决了域名投资者的域名管理难题,在米表网,您可以将您的域名批量上传,给您的域名更多展示空间,定制化的米表让用您的域名出售页更加便捷、美观!
Keywords and Tags: blogs, parked domain, pups, wiki
Related Terms:
Fav Icon:
Age: Over 1 year old
Domain Created: 15th October, 2022
Domain Updated: 16th October, 2022
Domain Expires: 15th October, 2023
Review

Snoop Score

Valuation

$10 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 10,873,232
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

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: usagipoi.net 12
Domain Name: usagipoi 8
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 67
Performance 82
Accessibility 76
Best Practices 83
SEO 73
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
82

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.
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).

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 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://usagipoi.net/
http/1.1
0
817.7349999969
265
0
301
text/html
http://www.usagipoi.net/index.php
http/1.1
818.09599999542
1530.6629999977
2283
6283
200
text/html
Document
https://hm.baidu.com/hm.js?87621b026e2d193014b36e3eb6c9ecc7
http/1.1
1545.7689999967
2658.1189999997
11964
30401
200
application/javascript
Script
https://jspassport.ssl.qhimg.com/11.0.1.js?d182b3f28525f2db83acfaaf6e696dba
h2
1549.2709999962
2757.3139999949
406
106
200
application/x-javascript
Script
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=556056888&si=87621b026e2d193014b36e3eb6c9ecc7&v=1.2.95&lv=1&sn=23758&r=0&ww=1350&ct=!!&u=http%3A%2F%2Fwww.usagipoi.net%2Findex.php&tt=%E4%BA%9A%E5%8D%9A%E5%9B%BD%E9%99%85%EF%BC%8C%E7%AC%AC%E4%B8%80%E4%BF%A1%E8%AA%89%E5%B9%B3%E5%8F%B0
http/1.1
2675.2720000004
4400.0919999962
299
43
200
image/gif
Image
https://s.ssl.qhres2.com/ssl/ab77b6ea7f3fbf79.js
h2
2759.3899999993
3062.9199999967
1097
478
200
application/javascript
Script
http://s.360.cn/so/zz.gif?url=http%3A%2F%2Fwww.usagipoi.net%2Findex.php&sid=d182b3f28525f2db83acfaaf6e696dba&token=dp1h8p2.bx3efd2n8i5/2t5efn2.dibo
http/1.1
3066.5259999951
3748.6040000003
240
0
200
image/gif
Image
https://vg07.cc/my/
h2
4551.2769999987
5009.944999998
2198
5950
200
text/html
Document
https://hm.baidu.com/hm.gif?hca=38A1828A23EEFC42&cc=1&ck=1&cl=24-bit&ds=800x600&vl=940&ep=2349%2C2349&et=3&ja=0&ln=en-us&lo=0&rnd=1859216911&si=87621b026e2d193014b36e3eb6c9ecc7&v=1.2.95&lv=1&sn=23758&r=0&ww=1350&u=http%3A%2F%2Fwww.usagipoi.net%2Findex.php
5015.0639999993
0
0
-1
Image
https://sdk.51.la/js-sdk-pro.min.js
http/1.1
5020.1919999963
5131.1270000006
13115
33924
200
application/javascript
Script
https://sdk.51.la/perf/js-sdk-perf.min.js
http/1.1
5020.3929999989
5161.963999999
11764
34386
200
application/javascript
Script
https://vg07.cc/my/js/link.js
h2
5020.5159999969
5097.7009999988
636
766
200
application/javascript
Script
https://vg07.cc/my/img/bg.png
h2
5165.3759999972
5949.3000000002
776399
776191
200
image/png
Image
https://vg07.cc/my/img/banner.png
h2
5175.1099999965
5875.3399999987
475942
475734
200
image/png
Image
https://vg07.cc/my/img/kf.png
h2
5175.3109999991
5413.4109999941
18326
18118
200
image/png
Image
https://cdn.openjquery.org/jquery/3.6.0/jquery.min.js
h2
5134.9730000002
5231.3759999961
2619
0
403
text/html
Script
https://hm.baidu.com/hm.js?33346c1e498dc0f5de395584001aea3a
http/1.1
5175.7059999945
6481.992999994
11621
30395
200
application/javascript
Script
https://collect-v6.51.la/v6/collect?dt=4
5161.7019999976
0
0
-1
XHR
https://vg07.cc/my/img/btn_1.png
h2
5177.7409999995
5332.3699999964
4171
3963
200
image/png
Image
https://vg07.cc/my/img/btn_2.png
h2
5177.9129999995
5414.1729999974
2484
2276
200
image/png
Image
https://vg07.cc/my/img/btn_3.png
h2
5178.5039999959
5414.4579999993
4260
4052
200
image/png
Image
https://vg07.cc/my/img/btn_4.png
h2
5178.5969999983
5489.4099999947
2635
2427
200
image/png
Image
https://collect-v6.51.la/health/collect
5373.9119999955
5379.0239999944
0
0
-1
Ping
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=2132419740&si=33346c1e498dc0f5de395584001aea3a&su=http%3A%2F%2Fwww.usagipoi.net%2F&v=1.2.95&lv=1&sn=23762&r=0&ww=1350&ct=!!&u=https%3A%2F%2Fvg07.cc%2Fmy%2F&tt=yb-ayx
6498.606000001
0
0
-1
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)
1554.946
10.066
1565.281
5.747
1571.037
75.386
2681.61
14.902
5035.052
11.004
5156.539
13.26
5169.865
14.338
5189.125
9.073
5198.209
54.491
6507.29
13.563
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

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Usagipoi.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Usagipoi.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Usagipoi.net should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Usagipoi.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 460 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://vg07.cc/my/
459.662
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Usagipoi.net 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.
URL Potential Savings (Ms)
https://vg07.cc/my/img/banner.png
0
Avoids enormous network payloads — Total size was 1,311 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://vg07.cc/my/img/bg.png
776399
https://vg07.cc/my/img/banner.png
475942
https://vg07.cc/my/img/kf.png
18326
https://sdk.51.la/js-sdk-pro.min.js
13115
https://hm.baidu.com/hm.js?87621b026e2d193014b36e3eb6c9ecc7
11964
https://sdk.51.la/perf/js-sdk-perf.min.js
11764
https://hm.baidu.com/hm.js?33346c1e498dc0f5de395584001aea3a
11621
https://vg07.cc/my/img/btn_3.png
4260
https://vg07.cc/my/img/btn_1.png
4171
https://vg07.cc/my/img/btn_4.png
2635
Avoids an excessive DOM size — 22 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
22
Maximum DOM Depth
4
Maximum Child Elements
7
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Usagipoi.net 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.0 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://vg07.cc/my/
180.706
25.517
2.861
Minimizes main-thread work — 0.3 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)
Style & Layout
124.701
Script Evaluation
86.106
Other
46.833
Rendering
14.584
Script Parsing & Compilation
8.534
Parse HTML & CSS
6.681
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 — 24 requests • 1,311 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
24
1342724
Image
11
1284756
Script
8
53222
Document
2
4481
Other
3
265
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
15
55673
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)
23884
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.
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.
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 usagipoi.net 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

Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Other

Eliminate render-blocking resources — Potential savings of 250 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Usagipoi.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://sdk.51.la/js-sdk-pro.min.js
13115
230
https://sdk.51.la/perf/js-sdk-perf.min.js
11764
230
Properly size images — Potential savings of 589 KiB
Images can slow down the page's load time. Usagipoi.net should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://vg07.cc/my/img/bg.png
776191
390902
https://vg07.cc/my/img/banner.png
475734
212283
Serve images in next-gen formats — Potential savings of 885 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://vg07.cc/my/img/bg.png
776191
495612.9
https://vg07.cc/my/img/banner.png
475734
410801.35
Avoid multiple page redirects — Potential savings of 380 ms
Redirects can cause additional delays before the page can begin loading. Usagipoi.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://usagipoi.net/
190
http://www.usagipoi.net/index.php
190
https://vg07.cc/my/
0
Serve static assets with an efficient cache policy — 12 resources found
Usagipoi.net 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)
http://s.360.cn/so/zz.gif?url=http%3A%2F%2Fwww.usagipoi.net%2Findex.php&sid=d182b3f28525f2db83acfaaf6e696dba&token=dp1h8p2.bx3efd2n8i5/2t5efn2.dibo
0
240
https://jspassport.ssl.qhimg.com/11.0.1.js?d182b3f28525f2db83acfaaf6e696dba
600000
406
https://vg07.cc/my/js/link.js
43200000
636
https://sdk.51.la/js-sdk-pro.min.js
1296000000
13115
https://sdk.51.la/perf/js-sdk-perf.min.js
1296000000
11764
https://vg07.cc/my/img/bg.png
2592000000
776399
https://vg07.cc/my/img/banner.png
2592000000
475942
https://vg07.cc/my/img/kf.png
2592000000
18326
https://vg07.cc/my/img/btn_3.png
2592000000
4260
https://vg07.cc/my/img/btn_1.png
2592000000
4171
https://vg07.cc/my/img/btn_4.png
2592000000
2635
https://vg07.cc/my/img/btn_2.png
2592000000
2484

Metrics

Cumulative Layout Shift — 0.396
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

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
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://vg07.cc/my/img/bg.png
https://vg07.cc/my/img/banner.png
https://vg07.cc/my/img/kf.png
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
76

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of usagipoi.net. 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.
`<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 alternate 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.

Contrast

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

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"]`
Usagipoi.net may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that usagipoi.net 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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
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

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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 — 3 insecure requests 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://usagipoi.net/
Allowed
http://www.usagipoi.net/index.php
Allowed
http://s.360.cn/so/zz.gif?url=http%3A%2F%2Fwww.usagipoi.net%2Findex.php&sid=d182b3f28525f2db83acfaaf6e696dba&token=dp1h8p2.bx3efd2n8i5/2t5efn2.dibo
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 403 (Forbidden)
ReferenceError: returnCitySN is not defined at http://www.usagipoi.net/index.php:251:13
TypeError: Cannot read properties of null (reading 'style') at http://www.usagipoi.net/index.php:269:9
TypeError: Cannot read properties of null (reading 'style') at http://www.usagipoi.net/index.php:269:9
TypeError: Cannot read properties of null (reading 'style') at http://www.usagipoi.net/index.php:269:9
73

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for usagipoi.net. 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 usagipoi.net 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

Page is 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.
Blocking Directive Source

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 usagipoi.net. 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 usagipoi.net 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) 67
Performance 78
Accessibility 76
Best Practices 83
SEO 77
PWA 20
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
78

Performance

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

Metrics

Time to Interactive — 3.5 s
The time taken for the page to become fully interactive.
Speed Index — 3.2 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 20 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).
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 — 60 ms
Users could experience a delay when interacting with the page.
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://usagipoi.net/
http/1.1
0
581.78500000031
253
0
301
text/html
http://www.usagipoi.net/index.php
http/1.1
582.09799999986
1354.3399999999
2283
6283
200
text/html
Document
https://hm.baidu.com/hm.js?87621b026e2d193014b36e3eb6c9ecc7
http/1.1
1365.7979999998
2441.3920000006
11964
30401
200
application/javascript
Script
https://jspassport.ssl.qhimg.com/11.0.1.js?d182b3f28525f2db83acfaaf6e696dba
1367.1380000005
3844.5650000003
0
0
-1
Script
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=476199749&si=87621b026e2d193014b36e3eb6c9ecc7&v=1.2.95&lv=1&sn=23781&r=0&ww=360&ct=!!&u=http%3A%2F%2Fwww.usagipoi.net%2Findex.php&tt=%E4%BA%9A%E5%8D%9A%E5%9B%BD%E9%99%85%EF%BC%8C%E7%AC%AC%E4%B8%80%E4%BF%A1%E8%AA%89%E5%B9%B3%E5%8F%B0
http/1.1
2454.1150000005
3568.327
299
43
200
image/gif
Image
https://vg07.cc/my/
h2
4368.0130000002
4684.354
2198
5950
200
text/html
Document
https://hm.baidu.com/hm.gif?hca=8B632271FD737745&cc=1&ck=1&cl=24-bit&ds=360x640&vl=640&ep=2241%2C2241&et=3&ja=0&ln=en-us&lo=0&rnd=366178640&si=87621b026e2d193014b36e3eb6c9ecc7&v=1.2.95&lv=1&sn=23781&r=0&ww=360&u=http%3A%2F%2Fwww.usagipoi.net%2Findex.php
4688.9600000004
0
0
-1
Image
https://sdk.51.la/js-sdk-pro.min.js
http/1.1
4693.1490000006
4800.4090000004
13115
33924
200
application/javascript
Script
https://sdk.51.la/perf/js-sdk-perf.min.js
http/1.1
4693.346
4763.0900000004
11764
34386
200
application/javascript
Script
https://vg07.cc/my/js/link.js
h2
4693.6919999998
4768.1680000005
636
766
200
application/javascript
Script
https://vg07.cc/my/img/bg.png
4693.3150000004
4907.2320000005
0
0
-1
Image
https://vg07.cc/my/img/banner.png
4693.4030000002
4907.1910000002
0
0
-1
Image
https://vg07.cc/my/img/kf.png
4693.4860000001
4907.1199999998
0
0
-1
Image
https://cdn.openjquery.org/jquery/3.6.0/jquery.min.js
h2
4769.1800000002
4795.1000000003
7286
25557
200
application/javascript
Script
https://hm.baidu.com/hm.js?33346c1e498dc0f5de395584001aea3a
4696.2020000001
4907.1450000001
0
0
-1
Script
https://collect-v6.51.la/v6/collect?dt=4
4820.4210000004
4907.0860000002
0
0
-1
XHR
https://vg07.cc/my/mobile.html
h2
4827.7040000003
4904.442
1764
4308
200
text/html
Document
https://sdk.51.la/js-sdk-pro.min.js
http/1.1
4910.4560000005
4910.5410000002
13115
33924
200
application/javascript
Script
https://sdk.51.la/perf/js-sdk-perf.min.js
http/1.1
4910.6010000005
4910.6810000003
11764
34386
200
application/javascript
Script
https://vg07.cc/my/js/link.js
h2
4911.0170000004
5301.246
636
766
200
application/javascript
Script
https://vg07.cc/my/img/mbg.png
h2
4911.1460000004
5272.6410000005
211942
211734
200
image/png
Image
https://vg07.cc/my/img/kf.png
h2
5302.7170000005
5449.8450000001
18326
18118
200
image/png
Image
https://cdn.openjquery.org/jquery/3.6.0/jquery.min.js
h2
5273.862
5355.3609999999
7290
25557
200
application/javascript
Script
https://hm.baidu.com/hm.js?33346c1e498dc0f5de395584001aea3a
http/1.1
5303.9269999999
6384.6149999999
11621
30395
200
application/javascript
Script
https://collect-v6.51.la/v6/collect?dt=4
http/1.1
4931.662
6319.8520000005
391
0
200
text/plain
XHR
https://collect-v6.51.la/health/collect
5136.2200000003
5137.4470000001
0
0
-1
Ping
https://vg07.cc/my/img/mbtn_1.png
h2
5305.2500000003
5380.4049999999
6734
6526
200
image/png
Image
https://vg07.cc/my/img/mbtn2.png
h2
5305.4499999998
5450.3380000006
10303
10095
200
image/png
Image
https://hm.baidu.com/hm.gif?cc=1&ck=1&cl=24-bit&ds=360x640&vl=653&et=0&ja=0&ln=en-us&lo=0&rnd=612516977&si=33346c1e498dc0f5de395584001aea3a&su=https%3A%2F%2Fvg07.cc%2Fmy%2F&v=1.2.95&lv=1&sn=23785&r=0&ww=367&ct=!!&u=https%3A%2F%2Fvg07.cc%2Fmy%2Fmobile.html&tt=%E7%88%B1%E6%B8%B8%E6%88%8F%E4%BD%93%E8%82%B2
http/1.1
6396.1900000004
8097.9930000003
299
43
200
image/gif
Image
https://collect-v6.51.la/health/collect
8362.3360000001
8365.5319999998
0
0
-1
Ping
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)
1375.184
7.16
1385.941
80.187
2461.161
10.906
4705.765
8.192
4820.962
7.591
4828.575
16.125
4924.934
6.51
4931.657
23.569
5322.715
52.601
5376.009
15.713
6405.658
8.727
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

Properly size images
Images can slow down the page's load time. Usagipoi.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Usagipoi.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Usagipoi.net should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Usagipoi.net should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Usagipoi.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 80 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://vg07.cc/my/mobile.html
77.734
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Usagipoi.net 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 336 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://vg07.cc/my/img/mbg.png
211942
https://vg07.cc/my/img/kf.png
18326
https://sdk.51.la/js-sdk-pro.min.js
13115
https://sdk.51.la/js-sdk-pro.min.js
13115
https://hm.baidu.com/hm.js?87621b026e2d193014b36e3eb6c9ecc7
11964
https://sdk.51.la/perf/js-sdk-perf.min.js
11764
https://sdk.51.la/perf/js-sdk-perf.min.js
11764
https://hm.baidu.com/hm.js?33346c1e498dc0f5de395584001aea3a
11621
https://vg07.cc/my/img/mbtn2.png
10303
https://cdn.openjquery.org/jquery/3.6.0/jquery.min.js
7290
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
5
Maximum Child Elements
4
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Usagipoi.net 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.4 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://vg07.cc/my/mobile.html
686.22
63.2
9.94
Unattributable
165.42
8.568
0.46
https://hm.baidu.com/hm.js?87621b026e2d193014b36e3eb6c9ecc7
94.952
59.244
8.376
https://sdk.51.la/perf/js-sdk-perf.min.js
92.164
50.104
5.72
https://sdk.51.la/js-sdk-pro.min.js
69.312
58.848
7.46
https://vg07.cc/my/
61.792
58.344
1.164
https://hm.baidu.com/hm.js?33346c1e498dc0f5de395584001aea3a
58.732
51.1
1.132
Minimizes main-thread work — 1.3 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)
Style & Layout
526.652
Script Evaluation
381.748
Other
206.824
Rendering
103.328
Script Parsing & Compilation
37.208
Parse HTML & CSS
16.612
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 — 30 requests • 336 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
30
343983
Image
10
247903
Script
12
89191
Document
3
6245
Other
5
644
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
19
91444
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)
24183
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 — 5 long tasks 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://vg07.cc/my/mobile.html
630
160
https://vg07.cc/my/mobile.html
790
105
https://sdk.51.la/js-sdk-pro.min.js
3614
94
https://sdk.51.la/js-sdk-pro.min.js
2040
65
Unattributable
895
63
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 usagipoi.net 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.

Audits

First Meaningful Paint — 3.2 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 270 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Usagipoi.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://sdk.51.la/js-sdk-pro.min.js
13115
794
https://sdk.51.la/perf/js-sdk-perf.min.js
11764
794
Serve images in next-gen formats — Potential savings of 96 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://vg07.cc/my/img/mbg.png
211734
98121.05
Serve static assets with an efficient cache policy — 12 resources found
Usagipoi.net 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://cdn.openjquery.org/jquery/3.6.0/jquery.min.js
7200000
7290
https://cdn.openjquery.org/jquery/3.6.0/jquery.min.js
7200000
7286
https://vg07.cc/my/js/link.js
43200000
636
https://vg07.cc/my/js/link.js
43200000
636
https://sdk.51.la/js-sdk-pro.min.js
1296000000
13115
https://sdk.51.la/js-sdk-pro.min.js
1296000000
13115
https://sdk.51.la/perf/js-sdk-perf.min.js
1296000000
11764
https://sdk.51.la/perf/js-sdk-perf.min.js
1296000000
11764
https://vg07.cc/my/img/mbg.png
2592000000
211942
https://vg07.cc/my/img/kf.png
2592000000
18326
https://vg07.cc/my/img/mbtn2.png
2592000000
10303
https://vg07.cc/my/img/mbtn_1.png
2592000000
6734

Metrics

First Contentful Paint — 3.2 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 4.2 s
The timing of the largest text or image that is painted.

Other

Avoid multiple page redirects — Potential savings of 2,040 ms
Redirects can cause additional delays before the page can begin loading. Usagipoi.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://usagipoi.net/
630
http://www.usagipoi.net/index.php
630
https://vg07.cc/my/
780
https://vg07.cc/my/mobile.html
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
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://vg07.cc/my/img/mbg.png
https://vg07.cc/my/img/kf.png
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
First Contentful Paint (3G) — 6393 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
76

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of usagipoi.net. 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.
`<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 alternate 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.

Contrast

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

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"]`
Usagipoi.net may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that usagipoi.net 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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
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

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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 — 2 insecure requests 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://usagipoi.net/
Allowed
http://www.usagipoi.net/index.php
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_TIMED_OUT
ReferenceError: returnCitySN is not defined at http://www.usagipoi.net/index.php:251:13
TypeError: Cannot read properties of null (reading 'style') at http://www.usagipoi.net/index.php:269:9
TypeError: Cannot read properties of null (reading 'style') at http://www.usagipoi.net/index.php:269:9
TypeError: Cannot read properties of null (reading 'style') at http://www.usagipoi.net/index.php:269:9
77

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for usagipoi.net. 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 usagipoi.net 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.
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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

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.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

Page is 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.
Blocking Directive Source

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

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 usagipoi.net. This includes details about web app manifests.

PWA Optimized

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 usagipoi.net 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
Content is not 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.
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: 199.59.243.223
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Bodis, LLC
Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: REDACTED FOR PRIVACY
Country: US
City: REDACTED FOR PRIVACY
State: MI
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Gname.com Pte. Ltd. 8.216.130.44
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
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
usagipoi.net. 199.59.243.223 IN 10800

NS Records

Host Nameserver Class TTL
usagipoi.net. ns1.bodis.com. IN 600
usagipoi.net. ns2.bodis.com. IN 600

SOA Records

Domain Name Primary NS Responsible Email TTL
usagipoi.net. ns1.bodis.com. dnsadmin.bodis.com. 10800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: openresty
Date: 17th March, 2023
Content-Type: text/html; charset=UTF-8
Cache-Control: post-check=0, pre-check=0
Expires: 1st January, 1970
Connection: keep-alive
Set-Cookie: *
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4pamkAQVSQuqYsKx3YzdUHCvbVZvFUsCAwEAAQ==_HK9KLXg7cnc4AYi2++o74TMMbuYGDTQP/IIgf04X2zvHpvKHel9F5vL13yN1eMIGYG4swEZSHl1QNp7j526aWQ==
Accept-CH: sec-ch-prefers-color-scheme
Critical-CH: sec-ch-prefers-color-scheme
Vary: sec-ch-prefers-color-scheme
Pragma: no-cache

Whois Lookup

Created: 15th October, 2022
Changed: 16th October, 2022
Expires: 15th October, 2023
Registrar: Gname 006 Inc
Status: clientTransferProhibited
Nameservers: ns1.bodis.com
ns2.bodis.com
Full Whois: Domain Name: USAGIPOI.NET
Registry Domain ID: 2732295966_DOMAIN_NET-VRSN
Registrar WHOIS Server: www.gname.com/whois
Registrar URL: http://www.gname.com
Updated Date: 2022-10-16T22:13:19Z
Creation Date: 2022-10-15T18:34:44Z
Registry Expiry Date: 2023-10-15T18:34:44Z
Registrar: Gname 006 Inc
Registrar IANA ID: 3946
Registrar Abuse Contact Email: ZYS@GNAME.COM
Registrar Abuse Contact Phone: +65 31581391
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.BODIS.COM
Name Server: NS2.BODIS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2023-03-17T14:43:30Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
ns1.bodis.com 185.85.196.36
ns2.bodis.com 199.59.243.150
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$1,765 USD 2/5
$189 USD 1/5
$3,264 USD 2/5
$964 USD 1/5
$326 USD 1/5