avsee.com

avsee.com is SSL secured

Free website and domain report on avsee.com

Last Updated: 2nd October, 2022 Update Now
Overview

Snoop Summary for avsee.com

This is a free and comprehensive report about avsee.com. Avsee.com is hosted in United States on a server with an IP address of 162.19.151.255, where USD is the local currency and the local language is English. Our records indicate that avsee.com is owned/operated by Hu Yanlin. Avsee.com has the potential to be earning an estimated $5 USD per day from advertising revenue. If avsee.com was to be sold it would possibly be worth $3,563 USD (based on the daily revenue potential of the website over a 24 month period). Avsee.com is quite popular with an estimated 1,708 daily unique visitors. This report was last updated 2nd October, 2022.

About avsee.com

Site Preview: avsee.com avsee.com
Title: woqing.com - 我请
Description:
Keywords and Tags: marketing, merchandising
Related Terms: avsee, avsee.tv
Fav Icon:
Age: Over 18 years old
Domain Created: 4th June, 2006
Domain Updated: 29th June, 2022
Domain Expires: 4th June, 2023
Review

Snoop Score

2/5

Valuation

$3,563 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 449,249
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: 1,708
Monthly Visitors: 51,977
Yearly Visitors: 623,313
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $148 USD
Yearly Revenue: $1,776 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: avsee.com 9
Domain Name: avsee 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 75
Performance 95
Accessibility 78
Best Practices 92
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://avsee.com/
Updated: 2nd October, 2022
Simulate loading on desktop
95

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 60 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 — 1.0 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 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://avsee.com/
http/1.1
0
306.07299995609
266
0
301
text/plain
https://avsee.com/
h2
306.46299989894
780.56599991396
3040
13020
200
text/html
Document
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
h2
789.30899989791
813.70999990031
29014
89664
200
application/javascript
Script
https://kit.fontawesome.com/5929f65a24.js
h2
789.66199979186
907.66999986954
4659
11090
200
text/javascript
Script
https://cdn.jsdelivr.net/npm/less
h2
789.98099989258
818.78399988636
47662
146335
200
application/javascript
Script
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro-v4-shims.min.js?token=5929f65a24
h2
917.6659998484
1056.1249998864
8089
27127
200
application/javascript
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro.min.js?token=5929f65a24
h2
918.4889998287
1050.9479998145
18158
61218
200
application/javascript
Fetch
https://avsee.com/styles.less
h2
931.48399982601
1355.387999909
3143
24675
200
application/octet-stream
XHR
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/sign-hanging.svg?token=5929f65a24
h2
1084.4789999537
1135.3289999533
826
726
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/file-magnifying-glass.svg?token=5929f65a24
h2
1085.7739998028
1111.9309999049
1050
1178
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/music.svg?token=5929f65a24
h2
1086.8059999775
1111.4999998827
887
775
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/snowflake.svg?token=5929f65a24
h2
1088.654999854
1112.4179998878
1626
2464
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/tv-retro.svg?token=5929f65a24
h2
1089.3170000054
1113.6509999633
979
1156
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/5.svg?token=5929f65a24
h2
1090.0299998466
1117.0599998441
806
600
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/1.svg?token=5929f65a24
h2
1091.1369998939
1121.5109999757
732
452
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/camera-movie.svg?token=5929f65a24
h2
1092.194999801
1216.2999999709
1002
1137
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/robot.svg?token=5929f65a24
h2
1093.2219999377
1215.8559998497
853
922
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/arrow-up-right-dots.svg?token=5929f65a24
h2
1094.6709997952
1129.6469999943
1256
1825
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/earth-europe.svg?token=5929f65a24
h2
1095.1979998499
1120.7779999822
2087
4064
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/shield-check.svg?token=5929f65a24
h2
1096.3709999342
1121.1889998522
795
599
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/heart.svg?token=5929f65a24
h2
1097.0469999593
1224.9849999789
756
520
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/light/envelope.svg?token=5929f65a24
h2
1098.0829999316
1217.5729998853
799
646
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/light/at.svg?token=5929f65a24
h2
1098.8319998141
1216.5669999085
1004
1036
200
image/svg+xml
Fetch
https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900,900italic&subset=latin,cyrillic
h2
1409.8739998881
1428.5849998705
1971
24745
200
text/css
XHR
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.0/css/bootstrap.min.css
h2
1552.4209998548
1582.1229999419
20231
114011
200
text/css
Stylesheet
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
h2
1567.4679998774
1570.9119997919
12087
11160
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1570.3729998786
1573.5479998402
11956
11028
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1662.6729997806
1956.3739998266
11968
11040
200
font/woff2
Font
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)
786.193
11.893
824.738
21.343
911.66
8.529
920.242
15.069
1059.171
18.366
1078.333
23.105
1122.924
11.489
1138.664
6.901
1146.411
5.828
1220.587
6.314
1231.371
6.062
1238.006
13.235
1357.457
56.876
1430.939
125.26
1556.216
158.876
1720.082
7.64
1727.864
50.257
1780.819
33.767
1814.762
43.618
1858.432
11.495
1967.716
15.873
3119.225
6.076
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. Avsee.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Avsee.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Avsee.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Avsee.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 19 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Avsee.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.0/css/bootstrap.min.css
20231
19843
Reduce unused JavaScript — Potential savings of 20 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://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
29014
20867
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
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 480 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://avsee.com/
475.097
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Avsee.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://avsee.com/
190
https://avsee.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Avsee.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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://avsee.com/
167
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 183 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.jsdelivr.net/npm/less
47662
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
29014
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.0/css/bootstrap.min.css
20231
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro.min.js?token=5929f65a24
18158
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
12087
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
11968
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11956
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro-v4-shims.min.js?token=5929f65a24
8089
https://kit.fontawesome.com/5929f65a24.js
4659
https://avsee.com/styles.less
3143
Uses efficient cache policy on static assets — 1 resource found
Avsee.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://cdn.jsdelivr.net/npm/less
604800000
47662
Avoids an excessive DOM size — 192 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
192
Maximum DOM Depth
10
Maximum Child Elements
21
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Avsee.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.3 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://avsee.com/
440.072
58.961
1.793
https://cdn.jsdelivr.net/npm/less
195.116
183.08
2.983
Unattributable
50.621
17.216
0.218
https://kit.fontawesome.com/5929f65a24.js
50
42.181
5.834
Minimizes main-thread work — 0.8 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
321.781
Style & Layout
241.604
Other
144.004
Rendering
30.636
Script Parsing & Compilation
12.675
Parse HTML & CSS
11.785
Garbage Collection
6.328
Keep request counts low and transfer sizes small — 28 requests • 183 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
28
187702
Script
3
81335
Other
20
47085
Font
3
36011
Stylesheet
1
20231
Document
1
3040
Image
0
0
Media
0
0
Third-party
25
181253
Minimize third-party usage — Third-party code blocked the main thread for 70 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)
47662
69.457
46364
0
37982
0
29014
0
20231
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 — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.10808448684528
0.0045096284344511
0.0045096284344511
0.00052034174243667
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `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.
Avoid long main-thread tasks — 3 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://cdn.jsdelivr.net/npm/less
1044
125
https://avsee.com/
377
79
https://cdn.jsdelivr.net/npm/less
757
57
Avoid non-composited animations — 110 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
n/a
n/a
Buy
n/a
n/a
n/a
n/a
n/a
n/a
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 avsee.com on mobile screens.
Avoids `unload` event listeners
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.

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.4 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.118
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Avsee.com 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://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
29014
310
https://kit.fontawesome.com/5929f65a24.js
4659
230
https://cdn.jsdelivr.net/npm/less
47662
350

Other

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
3.4439999144524
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.1749999616295
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
293.70100004598
78

Accessibility

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

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.

Audio and video

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

Contrast

Names and labels

Links do not 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.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that avsee.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.
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.
Name Version
jQuery
3.6.1
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.
URL Map URL
https://cdn.jsdelivr.net/npm/less
https://cdn.jsdelivr.net/npm/less.min.js.map
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://avsee.com/
Allowed
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for avsee.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 avsee.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.
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.

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 avsee.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 avsee.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) 71
Performance 62
Accessibility 78
Best Practices 92
SEO 92
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://avsee.com/
Updated: 2nd October, 2022
Simulate loading on mobile
62

Performance

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

Metrics

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

Other

Properly size images
Images can slow down the page's load time. Avsee.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Avsee.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Avsee.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Avsee.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 19 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Avsee.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.0/css/bootstrap.min.css
20207
19864
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
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 320 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://avsee.com/
324.532
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Avsee.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://avsee.com/
630
https://avsee.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Avsee.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 — Potential savings of 0 KiB
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.
URL Potential Savings (Bytes)
https://avsee.com/
167
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 183 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdn.jsdelivr.net/npm/less
47668
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
29014
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.0/css/bootstrap.min.css
20207
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro.min.js?token=5929f65a24
18169
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
12088
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
11968
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11956
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro-v4-shims.min.js?token=5929f65a24
8100
https://kit.fontawesome.com/5929f65a24.js
4652
https://avsee.com/styles.less
3142
Uses efficient cache policy on static assets — 1 resource found
Avsee.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://cdn.jsdelivr.net/npm/less
604800000
47668
Avoids an excessive DOM size — 192 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
192
Maximum DOM Depth
10
Maximum Child Elements
21
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Avsee.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.
Keep request counts low and transfer sizes small — 28 requests • 183 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
28
187866
Script
3
81334
Other
20
47261
Font
3
36012
Stylesheet
1
20207
Document
1
3052
Image
0
0
Media
0
0
Third-party
25
181420
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 — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.04309238688151
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `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.
Avoid long main-thread tasks — 10 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://cdn.jsdelivr.net/npm/less
4064
665
https://cdn.jsdelivr.net/npm/less
3039
245
https://avsee.com/
1159
179
https://avsee.com/
1512
117
https://avsee.com/
1421
91
https://kit.fontawesome.com/5929f65a24.js
2160
90
https://avsee.com/
1338
83
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
2537
63
https://kit.fontawesome.com/5929f65a24.js
2100
60
https://cdn.jsdelivr.net/npm/less
2837
52
Avoid non-composited animations — 105 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
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 avsee.com on mobile screens.
Avoids `unload` event listeners
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.

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

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://avsee.com/
http/1.1
0
350.99099995568
252
0
301
text/plain
https://avsee.com/
h2
351.32099990733
674.86099991947
3052
13020
200
text/html
Document
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
h2
685.91699993704
709.19999992475
29014
89664
200
application/javascript
Script
https://kit.fontawesome.com/5929f65a24.js
h2
686.21800001711
811.23999995179
4652
11090
200
text/javascript
Script
https://cdn.jsdelivr.net/npm/less
h2
686.77999998908
714.19199998491
47668
146335
200
application/javascript
Script
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro-v4-shims.min.js?token=5929f65a24
h2
816.58599991351
845.60200001579
8100
27127
200
application/javascript
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/js/pro.min.js?token=5929f65a24
h2
817.25500000175
843.59199996106
18169
61218
200
application/javascript
Fetch
https://avsee.com/styles.less
h2
829.53899994027
1142.8009999217
3142
24675
200
application/octet-stream
XHR
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/sign-hanging.svg?token=5929f65a24
h2
871.13999994472
896.51099999901
837
726
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/file-magnifying-glass.svg?token=5929f65a24
h2
872.38199997228
895.75699996203
1050
1178
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/music.svg?token=5929f65a24
h2
873.35999996867
896.22999995481
887
775
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/snowflake.svg?token=5929f65a24
h2
874.37299999874
903.16300000995
1626
2464
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/tv-retro.svg?token=5929f65a24
h2
875.33800001256
913.19399990607
968
1156
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/5.svg?token=5929f65a24
h2
876.35499995667
907.18899993226
795
600
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/1.svg?token=5929f65a24
h2
877.42899998557
902.49199990649
729
452
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/camera-movie.svg?token=5929f65a24
h2
878.63499997184
907.76099998038
1013
1137
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/robot.svg?token=5929f65a24
h2
879.31200000457
906.3839999726
864
922
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/arrow-up-right-dots.svg?token=5929f65a24
h2
880.37899998017
910.53599992301
1256
1825
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/duotone/earth-europe.svg?token=5929f65a24
h2
881.19899993762
916.44599998835
2076
4064
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/shield-check.svg?token=5929f65a24
h2
882.34399992507
913.58399996534
784
599
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/solid/heart.svg?token=5929f65a24
h2
883.18699994124
915.31800001394
756
520
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/light/envelope.svg?token=5929f65a24
h2
884.31999995373
915.99100001622
807
646
200
image/svg+xml
Fetch
https://ka-p.fontawesome.com/releases/v6.2.0/svgs/light/at.svg?token=5929f65a24
h2
884.74499993026
916.77299991716
1015
1036
200
image/svg+xml
Fetch
https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900,900italic&subset=latin,cyrillic
h2
1200.6790000014
1221.6649999609
2135
31122
200
text/css
XHR
https://maxcdn.bootstrapcdn.com/bootstrap/3.3.0/css/bootstrap.min.css
h2
1386.4779999712
1418.9079999924
20207
114011
200
text/css
Stylesheet
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
h2
1402.5989999063
1406.6650000168
12088
11160
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1406.4519999083
1410.4090000037
11956
11028
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1451.1929999571
1455.3689999739
11968
11040
200
font/woff2
Font
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)
680.001
11.634
720.367
15.809
818.939
13.005
849.08
14.924
864.832
22.621
906.656
7.952
925.954
7.038
933.035
6.244
944.06
5.379
949.502
5.4
958.729
5.597
1144.729
61.362
1223.673
166.317
1390.014
89.309
1484.049
6.647
1492.47
41.552
1534.404
45.377
1579.969
58.465
1638.493
15.588
1654.245
5.874
1662.177
5.57
1676.645
5.635
1710.377
6.534
1726.702
5.461
1760.251
5.314
1776.593
5.257
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.

Metrics

First Contentful Paint — 2.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.7 s
The time taken for the page to become fully interactive.
Speed Index — 3.5 s
The time taken for the page contents to be visibly populated.

Audits

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

Other

Reduce unused JavaScript — Potential savings of 20 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://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
29014
20867
Reduce JavaScript execution time — 1.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://avsee.com/
1547.652
163.66
7.396
https://cdn.jsdelivr.net/npm/less
954.92
901.236
9.38
Unattributable
205.672
84.02
0.836
https://kit.fontawesome.com/5929f65a24.js
163.28
132.312
22.576
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
78.228
63.052
6.316
Minimize main-thread work — 3.0 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
1344.28
Style & Layout
793.768
Other
595.788
Rendering
121.848
Script Parsing & Compilation
46.504
Parse HTML & CSS
40.36
Garbage Collection
33.792

Metrics

Total Blocking Time — 740 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 — 4.1 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 670 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 880 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Avsee.com 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://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js
29014
1230
https://kit.fontawesome.com/5929f65a24.js
4652
930
https://cdn.jsdelivr.net/npm/less
47668
1380
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2
4.0660001104698
https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
3.9570000953972
https://fonts.gstatic.com/s/roboto/v30/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
4.1760000167415
Reduce the impact of third-party code — Third-party code blocked the main thread for 780 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)
47668
750.444
46384
26.344
38147
0
29014
0
20207
0
First Contentful Paint (3G) — 5589 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
78

Accessibility

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

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.

Audio and video

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

Contrast

Names and labels

Links do not 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.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
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.
92

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that avsee.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.
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.
Name Version
jQuery
3.6.1
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.
URL Map URL
https://cdn.jsdelivr.net/npm/less
https://cdn.jsdelivr.net/npm/less.min.js.map
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://avsee.com/
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for avsee.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 avsee.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.
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.

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 avsee.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 avsee.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: 162.19.151.255
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
Failover IPs
Registration

Domain Registrant

Private Registration: No
Name:
Organization: Hu Yanlin
Country: CN
City:
State: Beijing
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Public Interest Registry 104.20.53.168
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

Issued To: avsee.com
Issued By: R3
Valid From: 27th August, 2022
Valid To: 25th November, 2022
Subject: CN = avsee.com
Hash: 9e4d052d
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x039823376A35B4CC57C89276020FF397A61F
Serial Number (Hex): 039823376A35B4CC57C89276020FF397A61F
Valid From: 27th August, 2024
Valid To: 25th November, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Aug 27 18:01:34.439 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:BF:FE:C5:54:14:9D:B9:60:34:E4:0E:
61:86:27:F4:EA:B0:74:D0:F1:1E:5D:9A:35:07:A8:17:
3F:65:1E:46:59:02:21:00:D7:3B:35:11:B7:11:BF:EE:
9C:24:42:78:0C:7C:0C:DC:26:E3:A0:10:31:5C:06:3D:
D3:74:22:68:9F:1D:B5:04
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Aug 27 18:01:35.045 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:77:27:D1:BD:70:CD:2A:3D:A9:25:9B:6B:
21:29:1B:7B:73:E7:52:81:D6:37:A8:54:33:47:4A:9E:
72:40:E9:BB:02:20:4C:D9:80:44:E6:50:FD:20:FC:29:
15:01:47:B8:86:AA:31:35:52:A8:37:8F:A0:C2:E9:60:
5F:94:1F:B4:5E:51
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:avsee.com
DNS:*.avsee.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
avsee.com. 162.19.151.255 IN 300

NS Records

Host Nameserver Class TTL
avsee.com. ns1.uniregistry-dns.net. IN 300
avsee.com. ns2.uniregistry-dns.com. IN 300
avsee.com. ns2.uniregistry-dns.net. IN 300
avsee.com. ns1.uniregistry-dns.com. IN 300

SOA Records

Domain Name Primary NS Responsible Email TTL
avsee.com. ns1.uniregistry-dns.net. dns.uniregistry.net. 300

TXT Records

Host Value Class TTL
avsee.com. v=spf1 IN 300

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 2nd October, 2022
Content-Type: text/html; charset=utf-8
Server: Powered by DomainStaff.com and Love
Last-Modified: 30th September, 2022
ETag: W/"6336d2bb-32dc"
X-Frame-Options: SAMEORIGIN
X-UA-Device: pc
X-Varnish: 5551721 5255903
Age: 0
Accept-Ranges: bytes
Vary: Accept-Encoding, User-Agent
x-cache: HIT
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Powered-By: DomainStaff.com
Content-Length: 13020
Connection: keep-alive

Whois Lookup

Created: 4th June, 2006
Changed: 29th June, 2022
Expires: 4th June, 2023
Registrar: GoDaddy Online Services Cayman Islands Ltd.
Status: clientTransferProhibited
Nameservers: ns1.uniregistry-dns.com
ns1.uniregistry-dns.net
ns2.uniregistry-dns.com
ns2.uniregistry-dns.net
Owner Organization: Hu Yanlin
Owner State: Beijing
Owner Country: CN
Owner Email: https://uniregistry.com/whois/contact/avsee.com?landerid=whois
Admin Email: https://uniregistry.com/whois/contact/avsee.com?landerid=whois
Tech Email: https://uniregistry.com/whois/contact/avsee.com?landerid=whois
Full Whois: Domain Name: avsee.com
Registry Domain ID: 471491489_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.uniregistrar.com
Registrar URL: http://uniregistry.com
Updated Date: 2022-06-29T01:00:35Z
Creation Date: 2006-06-04T01:47:19Z
Registrar Registration Expiration Date: 2023-06-04T01:47:19Z
Registrar: GoDaddy Online Services Cayman Islands Ltd.
Registrar IANA ID: 1659
Registrar Abuse Contact Email: abuse@uniregistry.com
Registrar Abuse Contact Phone: +1.4426008800
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Hu Yanlin
Registrant State/Province: Beijing
Registrant Country: CN
Registrant Email: https://uniregistry.com/whois/contact/avsee.com?landerid=whois
Admin Email: https://uniregistry.com/whois/contact/avsee.com?landerid=whois
Tech Email: https://uniregistry.com/whois/contact/avsee.com?landerid=whois
Name Server: NS2.UNIREGISTRY-DNS.COM
Name Server: NS2.UNIREGISTRY-DNS.NET
Name Server: NS1.UNIREGISTRY-DNS.NET
Name Server: NS1.UNIREGISTRY-DNS.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-06-29T01:00:35Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
ns1.uniregistry-dns.com 54.76.92.141
ns1.uniregistry-dns.net 52.49.180.240
ns2.uniregistry-dns.com 52.26.68.78
ns2.uniregistry-dns.net 52.38.7.42
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address