Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

avgoogle.com

avgoogle.com may not be SSL secured

Free website and domain report on avgoogle.com

Last Updated: 22nd April, 2024
Overview

Snoop Summary for avgoogle.com

This is a free and comprehensive report about avgoogle.com. The domain avgoogle.com is currently hosted on a server located in San Mateo, California in United States with the IP address 47.254.33.193, where USD is the local currency and the local language is English. Avgoogle.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If avgoogle.com was to be sold it would possibly be worth $813 USD (based on the daily revenue potential of the website over a 24 month period). Avgoogle.com is somewhat popular with an estimated 386 daily unique visitors. This report was last updated 22nd April, 2024.

About avgoogle.com

Site Preview: avgoogle.com avgoogle.com
Title:
Description: 旅色网汇集全球所有优秀网站，是中国最大最全的国外网站大全和国内网址导航，包括美国、韩国、日本等126个国家的音乐、电影、游戏、小说、博客等15万个网站。
Keywords and Tags: 旅色网址大全
Related Terms:
Fav Icon:
Age: Over 14 years old
Domain Created: 27th December, 2009
Domain Updated: 25th January, 2024
Domain Expires: 27th December, 2024
Review

Snoop Score

1/5

Valuation

$813 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,106,477
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: 386
Monthly Visitors: 11,749
Yearly Visitors: 140,890
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $33 USD
Yearly Revenue: $402 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: avgoogle.com 12
Domain Name: avgoogle 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 55
Performance 99
Accessibility 48
Best Practices 75
SEO 55
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.lvse.com/site/google-com-3.html
Updated: 2nd January, 2023
Simulate loading on desktop
99

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for avgoogle.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 — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 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).
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.005
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 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://avgoogle.com/
http/1.1
0
259.40699997591
312
0
301
text/html
http://www.lvse.com/site/google-com-3.html
http/1.1
259.7769999993
488.41300001368
5739
17895
200
text/html
Document
http://img1.lvse.com/js/jquery-1.6.2.min.js
http/1.1
494.81599999126
884.2130000121
91820
91556
200
application/javascript
Script
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
http/1.1
495.14800001634
886.44299999578
9711
9449
200
application/javascript
Script
http://www.lvse.com/js/lvse.comm.js
http/1.1
495.61099999119
882.59799999651
42374
42096
200
application/javascript
Script
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
http/1.1
496.12299998989
1007.08999997
24420
24171
200
text/css
Stylesheet
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
http/1.1
496.27800000599
798.52299997583
23382
23133
200
text/css
Stylesheet
http://img.lvse.com/images/i.png
http/1.1
913.91499998281
1157.7769999858
5266
5017
200
image/png
Image
http://w.cnzz.com/c.php?id=30060690
http/1.1
891.85600000201
1877.3919999949
671
0
200
application/javascript
Script
http://img.lvse.com/images/bj.gif
http/1.1
1011.3709999714
1253.0629999819
415
169
200
image/gif
Image
http://img.lvse.com/images/lvse_index_bg.png
http/1.1
1011.9849999901
1347.5059999619
7471
7222
200
image/png
Image
http://img.lvse.com/images/search_logo.png
http/1.1
1012.3819999862
1416.0750000156
2567
2319
200
image/png
Image
http://img.lvse.com/images/lvse_search_bg.gif
http/1.1
1012.6840000157
1237.5260000117
3717
3469
200
image/gif
Image
http://www.lvse.com/output/block/json/login_out_box_2/1672649741074
http/1.1
1105.3330000141
1355.1279999665
947
1413
200
text/html
XHR
http://img.lvse.com/images/main.png
http/1.1
1366.4080000017
1766.7059999658
2331
2083
200
image/png
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)
492.433
10.823
893.727
16.238
910.016
5.903
1011.398
91.54
1107.417
79.911
1189.083
51.578
1241.576
5.177
1365.328
11.444
1880.373
10.302
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. Avgoogle.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Avgoogle.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 9 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Avgoogle.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
6500
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
2927
Minify JavaScript — Potential savings of 11 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Avgoogle.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.lvse.com/js/lvse.comm.js
42374
11174
Reduce unused CSS — Potential savings of 41 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Avgoogle.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)
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
21300
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
20966
Reduce unused JavaScript — Potential savings of 80 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://img1.lvse.com/js/jquery-1.6.2.min.js
91820
47140
http://www.lvse.com/js/lvse.comm.js
42374
35218
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 130 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://img1.lvse.com/js/jquery-1.6.2.min.js
91556
59445
http://www.lvse.com/js/lvse.comm.js
42096
29753
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24171
19333
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23133
18536
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
9449
6336
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 230 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://www.lvse.com/site/google-com-3.html
229.63
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Avgoogle.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://avgoogle.com/
190
http://www.lvse.com/site/google-com-3.html
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Avgoogle.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 216 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://img1.lvse.com/js/jquery-1.6.2.min.js
91820
http://www.lvse.com/js/lvse.comm.js
42374
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
9711
http://img.lvse.com/images/lvse_index_bg.png
7471
http://www.lvse.com/site/google-com-3.html
5739
http://img.lvse.com/images/i.png
5266
http://img.lvse.com/images/lvse_search_bg.gif
3717
http://img.lvse.com/images/search_logo.png
2567
Avoids an excessive DOM size — 197 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
197
Maximum DOM Depth
form#login_form > span > a > span
8
Maximum Child Elements
body
16
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Avgoogle.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.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)
http://www.lvse.com/site/google-com-3.html
266.76
6.421
2.121
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
228.014
Script Evaluation
31.63
Other
28.64
Rendering
17.768
Parse HTML & CSS
6.793
Script Parsing & Compilation
5.153
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 — 15 requests • 216 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
15
221143
Script
4
144576
Stylesheet
2
47802
Image
6
21767
Document
1
5739
Other
2
1259
Media
0
0
Font
0
0
Third-party
2
983
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.0048490791816245
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
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.
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.

Other

Eliminate render-blocking resources — Potential savings of 310 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Avgoogle.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)
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
230
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
230
http://img1.lvse.com/js/jquery-1.6.2.min.js
91820
350
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
9711
230
http://www.lvse.com/js/lvse.comm.js
42374
230

Other

Serve static assets with an efficient cache policy — 12 resources found
Avgoogle.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)
http://img1.lvse.com/js/jquery-1.6.2.min.js
0
91820
http://www.lvse.com/js/lvse.comm.js
0
42374
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
0
24420
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
0
23382
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
0
9711
http://img.lvse.com/images/lvse_index_bg.png
0
7471
http://img.lvse.com/images/i.png
0
5266
http://img.lvse.com/images/lvse_search_bg.gif
0
3717
http://img.lvse.com/images/search_logo.png
0
2567
http://img.lvse.com/images/main.png
0
2331
http://img.lvse.com/images/bj.gif
0
415
http://w.cnzz.com/c.php?id=30060690
1800000
671
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
http://img.lvse.com/images/i.png
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avgoogle.com on mobile screens.
48

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of avgoogle.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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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 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"]`
Avgoogle.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
信息提示
对不起，您所访问的页面不存在！ 如果您是站长提交网站，请尽快做好我站友情连接，以便我站尽快审核收录！
网站轮播
商城轮播

Internationalization and localization

`<html>` element does not have 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.
Failing Elements
html

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div#main > div#notice_msg_box > p > img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
div#login_out_box > form#login_form > span > input
div#login_out_box > form#login_form > span > input
ul > li.searchcontent > form#searchForm > input#key_word
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.

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

Best Practices

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

Audits

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

Audits

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

Audits

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
1.6.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 15 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://avgoogle.com/
Allowed
http://www.lvse.com/site/google-com-3.html
Allowed
http://img1.lvse.com/js/jquery-1.6.2.min.js
Allowed
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
Allowed
http://www.lvse.com/js/lvse.comm.js
Allowed
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
Allowed
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
Allowed
http://img.lvse.com/images/i.png
Allowed
http://w.cnzz.com/c.php?id=30060690
Allowed
http://img.lvse.com/images/bj.gif
Allowed
http://img.lvse.com/images/lvse_index_bg.png
Allowed
http://img.lvse.com/images/search_logo.png
Allowed
http://img.lvse.com/images/lvse_search_bg.gif
Allowed
http://www.lvse.com/output/block/json/login_out_box_2/1672649741074
Allowed
http://img.lvse.com/images/main.png
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
7
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
55

SEO

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

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

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avgoogle.com on mobile screens.

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
div#main > div#notice_msg_box > p > img

Crawling and Indexing

Links are not 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 not valid — 319 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!-- /home/www/lvse/lvse/lvse/html/bf5/bf5173d0ba1a85f6510f4e5570bc771a.html --><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Unknown directive
2
<html>
Syntax not understood
3
<head>
Syntax not understood
4
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Syntax not understood
5
<title>优秀网站大全</title>
Syntax not understood
6
<meta name="description" content="">
Syntax not understood
7
<meta name="keywords" content="旅色网址大全">
Syntax not understood
8
<!-- script type="text/javascript" src="http://lib.sinaapp.com/js/jquery/1.6.2/jquery.min.js"></script -->
Unknown directive
9
<script type="text/javascript" src="http://img1.lvse.com/js/jquery-1.6.2.min.js"></script>
Unknown directive
10
<script type="text/javascript" src="http://img1.lvse.com/js/jquery.simplemodal-1.3.js"></script>
Unknown directive
11
<script type="text/javascript" >
Syntax not understood
12
var APP_BASE_URL = 'http://www.lvse.com';
Unknown directive
13
</script>
Syntax not understood
15
<script type="text/javascript" src="http://www.lvse.com/js/lvse.comm.js"></script>
Unknown directive
17
<link rel="stylesheet" type="text/css" href="http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css" />
Unknown directive
18
<link rel="stylesheet" type="text/css" href="http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css" />
Unknown directive
21
</head>
Syntax not understood
22
<body>
Syntax not understood
24
<a name="top"></a>
Syntax not understood
25
<style>
Syntax not understood
30
.search_box #key_word{*width:486px;}
Syntax not understood
32
</style>
Syntax not understood
33
<div id="bar">
Syntax not understood
34
<div id="barleft" style="width:702px;line-height:28px;">
Unknown directive
35
<div id="top_bar_menu">
Syntax not understood
36
<a href="http://www.lvse.com/" class="on" >首页</a>
Unknown directive
37
｜<a href="http://www.lvse.com/guowai" >国外网站</a>
Unknown directive
38
｜<a href="http://www.lvse.com/zhongguo" >国内网站 </a>
Unknown directive
39
｜<a href="http://mall.lvse.com/" >商城大全</a>
Unknown directive
40
｜<a href="http://www.lvse.com/latest/" >更新列表</a>
Unknown directive
41
｜<a href="http://www.lvse.com/jietu" >截图</a>
Unknown directive
42
｜<a href="http://www.lvse.com/zhuanti" >专题 </a>
Unknown directive
43
｜<a href="http://www.lvse.com/fanyi" >翻译</a>
Unknown directive
44
｜<a href="http://alexa.lvse.com" >工具</a>
Unknown directive
45
｜<a href="http://www.lvse.com/news" >新闻</a>
Unknown directive
46
｜<a href="http://www.lvse.com/manage" >运营</a>
Unknown directive
47
｜<a href="http://www.lvse.com/help" >帮助</a>
Unknown directive
48
｜<a href="http://www.lvse.com/submit" >提交网站</a>
Unknown directive
49
</div>
Syntax not understood
51
</div>
Syntax not understood
52
<div id="barright" style="width:276px;">
Unknown directive
53
<ul>
Syntax not understood
54
<li ><i> </i><a id="lvse_set_homepage" href="javascript:void(0);" ohref="http://www.lvse.com/" onclick="lvse.event_stat('set_home_page','http://www.lvse.com/');lvse_setHomePage(this, 'http://www.lvse.com/')" rel="nofollow">设为首页</a></li>
Unknown directive
55
<li class="fav"><i> </i><a href="javascript:addBookmark('优秀网站大全','http://www.lvse.com/robots.txt')" onclick="lvse.event_stat('add_bookmark','http://www.lvse.com/robots.txt');" rel="nofollow">加入收藏</a></li>
Unknown directive
56
<li class="msg"><i> </i><a target="_blank" href="http://www.lvse.com/guestbook" rel="nofollow">网友留言</a></li></ul>
Unknown directive
57
<!-- div id="login_out_bar" style="float:right;margin-right:5px;">
Unknown directive
58
<input class="loin_bt" type="button" value="登入" style="margin-right:5px;" onclick="window.location.href='http://www.lvse.com/login';">
Unknown directive
59
<input class="register_bt" type="button" value="注册" onclick="window.location.href='http://www.lvse.com/register';">
Unknown directive
60
</div -->
Syntax not understood
61
</div>
Syntax not understood
62
</div>
Syntax not understood
63
<div id="top"><a id="gotop"></a>
Syntax not understood
64
<a href="/"><div title="优秀网站大全" id="toplogo" style="width:180px;"></div></a>
Unknown directive
65
<div id="login_out_bar"></div>
Syntax not understood
66
<div id="top_search">
Syntax not understood
67
<div class="search_box">
Syntax not understood
68
<style>#se_logo{_width:30px;_margin:0px}.search_box #key_word{background-position-y: -112px;width: 410px;}.search_box ul{float:left;margin:0px;}</style>
Syntax not understood
69
<div id="se_logo"><span></span></div>
Syntax not understood
70
<ul> <li class="search_tags">
Syntax not understood
71
<a class="on search_tag" default_se="baidu" search_tag="web_page">网页</a>
Syntax not understood
72
<a class="search_tag" default_se="lvse" search_tag="site">网站</a>
Syntax not understood
73
<a class="search_tag" default_se="baidu" search_tag="news">新闻</a>
Syntax not understood
74
<a class="search_tag" default_se="baidu" search_tag="video">视频</a>
Syntax not understood
75
<a class="search_tag" default_se="baidu" search_tag="image">图片</a>
Syntax not understood
76
<a class="search_tag" default_se="baidu" search_tag="map">地图</a>
Syntax not understood
77
<a class="search_tag" default_se="baidu" search_tag="music">音乐</a>
Syntax not understood
78
<a class="search_tag" default_se="taobao" search_tag="shopping">购物</a>
Syntax not understood
79
<a class="search_tag" default_se="baidu" search_tag="know">知道</a>
Syntax not understood
80
<a class="search_tag" default_se="baidu" search_tag="wiki">百科</a>
Syntax not understood
81
<a class="search_tag" default_se="lvse" search_tag="wenzhang">文章</a>
Syntax not understood
82
</li>
Syntax not understood
83
<li class="searchcontent">
Syntax not understood
84
<form style="margin:0px;padding:0px;" method="post" action="" target="_blank" name="search" id="searchForm" charset="gbk" accept-charset="gb2312">
Unknown directive
85
<input type="text" obaiduSug="2" value="" class="searchtext" name="q" id="key_word">
Syntax not understood
86
<input type="hidden" ref="tn" name="tn" value="95426075_hao_pg" />
Syntax not understood
87
<span class="buttonv search_bt" id="search_bt">搜 索 </span>
Syntax not understood
88
</form></li>
Syntax not understood
89
</ul>
Syntax not understood
90
</div>
Syntax not understood
91
<script type="text/javascript">
Syntax not understood
92
var search_tag = 'web_page';
Syntax not understood
93
var se_define_4_baidu = {
Syntax not understood
94
"web_page" : {"se" : "baidu" ,"key_name" : "wd" ,"charset" : "utf-8","method" : "get","action" : "https://www.baidu.com/s"},
Unknown directive
95
"site" : {"se" : "lvse" ,"key_name" : "q" ,"charset" : "utf-8","method" : "post","action" : "http://www.lvse.com/search/site/(*)"},
Unknown directive
96
"news" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://news.baidu.com/ns"},
Unknown directive
97
"video" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://video.baidu.com/v"},
Unknown directive
98
"image" : {"se" : "baidu" ,"key_name" : "word","charset" : "gb2312","method" : "get","action" : "http://image.baidu.com/i"},
Unknown directive
99
"map" : {"se" : "baidu" ,"key_name" : "s" ,"charset" : "gbk","method" : "post","action" : "http://map.baidu.com/?newmap=1&s=(.*)&c=1"},
Unknown directive
100
"music" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://mp3.baidu.com/m"},
Unknown directive
101
"shopping" : {"se" : "taobao","key_name" : "q" ,"charset" : "utf-8","method" : "get","action" : "http://s.taobao.com/search"},
Unknown directive
102
"know" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://zhidao.baidu.com/search"},
Unknown directive
103
"wiki" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://baike.baidu.com/searchword/"},
Unknown directive
104
"wenzhang" : {"se" : "lvse" ,"key_name" : "q" ,"charset" : "utf-8","method" : "post","action" : "http://www.lvse.com/search/wenzhang/(*)"}
Unknown directive
105
};
Syntax not understood
107
$(function(){
Syntax not understood
108
$('.search_tag').click(function(){
Syntax not understood
109
search_tag= $(this).attr('search_tag');
Syntax not understood
110
se_define_4_baidu[search_tag]['se']=="lvse" ? $('#searchForm').attr("accept-charset","utf-8") : $('#searchForm').attr("accept-charset","gb2312");
Syntax not understood
111
$('#se_logo span').removeClass().addClass('se_logo_' + se_define_4_baidu[search_tag]['se']);
Syntax not understood
112
$('#se_logo span').html("<a target='_blank' style ='display: block; width:78px;height:35px;text-decoration: none;' href=http://www."+se_define_4_baidu[search_tag]['se']+".com" + (se_define_4_baidu[search_tag]['se'] == 'baidu' ? '?' : '') + "> </a>");
Syntax not understood
114
$('.search_tag').removeClass('on');
Syntax not understood
115
$('.search_tag[search_tag=' + search_tag + ']').addClass('on');
Syntax not understood
116
});
Syntax not understood
117
$('.search_tag[search_tag=web_page]').click();
Syntax not understood
120
$('#search_bt').click(function(){
Syntax not understood
121
var search_from = se_define_4_baidu[search_tag]['se'];
Syntax not understood
122
var search_value = $('#key_word').val();
Syntax not understood
123
var err_msg = '';
Syntax not understood
124
!/\S/.test(search_value) && (err_msg = '请输入搜索内容！');
Syntax not understood
126
if (err_msg != ''){
Syntax not understood
127
alert(err_msg);
Syntax not understood
128
return false;
Syntax not understood
129
}else{
Syntax not understood
131
$('#searchForm').attr({
Syntax not understood
132
'method' : se_define_4_baidu[search_tag]['method'],
Unknown directive
133
'charset' : se_define_4_baidu[search_tag]['charset'],
Unknown directive
134
'action' : se_define_4_baidu[search_tag]['action'].replace('(*)',encodeURIComponent(search_value)).replace('(.*)',encodeURIComponent('s&wd='+search_value))
Unknown directive
135
});
Syntax not understood
136
if (search_tag == 'shopping'){
Syntax not understood
137
$('#searchForm').find('input[ref="tn"]').attr('name','');
Syntax not understood
138
$('#searchForm').find('input[ref="pid"]').attr('name','pid');
Syntax not understood
139
}else{
Syntax not understood
140
$('#searchForm').find('input[ref="tn"]').attr('name','tn');
Syntax not understood
141
$('#searchForm').find('input[ref="pid"]').attr('name','');
Syntax not understood
142
}
Syntax not understood
143
$('#key_word').attr('name',se_define_4_baidu[search_tag]['key_name']);
Syntax not understood
144
document.charset = se_define_4_baidu[search_tag]['charset'];
Syntax not understood
145
$('#searchForm').get(0).submit();
Syntax not understood
146
document.charset = 'utf-8';
Syntax not understood
147
}
Syntax not understood
148
return false;
Syntax not understood
149
});
Syntax not understood
150
$('#key_word').keydown(function(event){
Syntax not understood
151
if(event.keyCode == 13) {
Syntax not understood
152
var search_from = se_define_4_baidu[search_tag]['se'];
Syntax not understood
153
var search_value= $('#key_word').val();
Syntax not understood
154
var err_msg = '';
Syntax not understood
155
!/\S/.test(search_value) && (err_msg = '请输入搜索内容！');
Syntax not understood
157
if (err_msg != ''){
Syntax not understood
158
alert(err_msg);
Syntax not understood
159
return false;
Syntax not understood
160
}else{
Syntax not understood
161
$('#searchForm').attr({
Syntax not understood
162
'method' : se_define_4_baidu[search_tag]['method'],
Unknown directive
163
'charset' : se_define_4_baidu[search_tag]['charset'],
Unknown directive
164
'action' : se_define_4_baidu[search_tag]['action'].replace('(*)',encodeURIComponent(search_value)).replace('(.*)',encodeURIComponent('s&wd='+search_value))
Unknown directive
165
});
Syntax not understood
166
if (search_tag == 'shopping'){
Syntax not understood
167
$('#searchForm').find('input[ref="tn"]').attr('name','');
Syntax not understood
168
$('#searchForm').find('input[ref="pid"]').attr('name','pid');
Syntax not understood
169
}else{
Syntax not understood
170
$('#searchForm').find('input[ref="tn"]').attr('name','tn');
Syntax not understood
171
$('#searchForm').find('input[ref="pid"]').attr('name','');
Syntax not understood
172
}
Syntax not understood
173
$('#key_word').attr('name',se_define_4_baidu[search_tag]['key_name']);
Syntax not understood
174
}
Syntax not understood
175
document.charset = se_define_4_baidu[search_tag]['charset'];
Syntax not understood
176
setTimeout(function(){document.charset = 'utf-8';},500);
Syntax not understood
177
return true;
Syntax not understood
178
}
Syntax not understood
179
}).focus(function(){
Syntax not understood
180
$('#key_word').get(0).select();
Syntax not understood
181
});
Syntax not understood
183
$('.search_box .search_bt').click(function(){this.blur();});
Syntax not understood
185
$('.searchtext').focus(function(){
Syntax not understood
186
if(typeof(BaiduSuggestion) == 'undefined'){
Syntax not understood
187
$.getScript("http://img.lvse.com/js/baidu_opensug.js",function(){
Unknown directive
188
setTimeout(function(){
Syntax not understood
189
BaiduSuggestion.bind('key_word',{"sugSubmit":false},function(txt){
Unknown directive
190
$('#key_word').val(txt);
Syntax not understood
191
$('#search_bt').click();
Syntax not understood
192
});
Syntax not understood
193
},500);
Syntax not understood
194
});
Syntax not understood
195
}
Syntax not understood
196
});
Syntax not understood
197
});
Syntax not understood
198
</script>
Syntax not understood
199
</div>
Syntax not understood
200
</div>
Syntax not understood
203
<div id="ad_banner_outer">
Syntax not understood
204
</div>
Syntax not understood
205
<script type="text/javascript" >
Syntax not understood
206
$(function(){
Syntax not understood
207
if (window.no_ad) {
Syntax not understood
208
return '';
Syntax not understood
209
}
Syntax not understood
210
$.get('/output/block/html/202/0/' + (new Date()).getTime(),function(html){
Syntax not understood
211
$('#ad_banner_outer').html(html);
Syntax not understood
212
});
Syntax not understood
213
});
Syntax not understood
214
</script>
Syntax not understood
216
<div id="crumbs">您的位置：
Syntax not understood
217
<a href="http://www.lvse.com/" rel="nofollow">首页</a>
Unknown directive
218
 > 找不到页面</div>
Syntax not understood
220
<script type="text/javascript" >
Syntax not understood
221
load_userinfo(null,'login_out_box_2');
Syntax not understood
222
</script>
Syntax not understood
226
<div id="main">
Syntax not understood
228
<div id="notice_msg_box" class="lvse_border_lt fff_bg">
Syntax not understood
229
<div class="lvse_bg lvse_inline_border_bottom hieht_25">
Syntax not understood
230
<h2>信息提示</h2>
Syntax not understood
231
</div>
Syntax not understood
232
<p><img src="http://img.lvse.com/images/i.png" /><span class="notice_msg">对不起，您所访问的页面不存在！</span></p>
Unknown directive
233
<br style="clear:both" />
Unknown directive
234
</div>
Syntax not understood
235
<script type="text/javascript" >
Syntax not understood
236
window.no_ad = true;
Syntax not understood
237
</script>
Syntax not understood
238
</div>
Syntax not understood
239
<div class="cleardiv"></div>
Syntax not understood
240
<div class="lvse_border_lt lvse_bg hieht_25" id="rand_sites_list">
Syntax not understood
241
<h2>网站轮播</h2>
Syntax not understood
242
<ul>
Syntax not understood
243
<li>
Syntax not understood
244
<span class="site_name"><a href="http://www.lvse.com/site/t-fumu-com-2412.html">父母网微博</a></span>
Unknown directive
245
</li>
Syntax not understood
246
<li>
Syntax not understood
247
<span class="site_name"><a href="http://www.lvse.com/site/kishairlines-ir-2719.html">基什航空</a></span>
Unknown directive
248
</li>
Syntax not understood
249
<li>
Syntax not understood
250
<span class="site_name"><a href="http://www.lvse.com/site/hostucan-cn-5594.html">主机点评网</a></span>
Unknown directive
251
</li>
Syntax not understood
252
<li>
Syntax not understood
253
<span class="site_name"><a href="http://www.lvse.com/site/1stenglish-com-601.html">第一英语在线</a></span>
Unknown directive
254
</li>
Syntax not understood
255
<li>
Syntax not understood
256
<span class="site_name"><a href="http://www.lvse.com/site/wiki-ename-cn-1648.html">域名百科</a></span>
Unknown directive
257
</li>
Syntax not understood
258
<li>
Syntax not understood
259
<span class="site_name"><a href="http://www.lvse.com/site/31jiaju-com-5460.html">中国家具网</a></span>
Unknown directive
260
</li>
Syntax not understood
261
<li>
Syntax not understood
262
<span class="site_name"><a href="http://www.lvse.com/site/cbrx-com-602.html">赤壁热线</a></span>
Unknown directive
263
</li>
Syntax not understood
264
<li>
Syntax not understood
265
<span class="site_name"><a href="http://www.lvse.com/site/zhhzw-com-2218.html">中华合租网</a></span>
Unknown directive
266
</li>
Syntax not understood
267
<li>
Syntax not understood
268
<span class="site_name"><a href="http://www.lvse.com/site/dailybooth-com-1207.html">Dailybooth</a></span>
Unknown directive
269
</li>
Syntax not understood
270
<li>
Syntax not understood
271
<span class="site_name"><a href="http://www.lvse.com/site/qdppc-com-3537.html">起点手机论坛</a></span>
Unknown directive
272
</li>
Syntax not understood
273
<li>
Syntax not understood
274
<span class="site_name"><a href="http://www.lvse.com/site/clarin-com-841.html">阿根廷号角报</a></span>
Unknown directive
275
</li>
Syntax not understood
276
<li>
Syntax not understood
277
<span class="site_name"><a href="http://www.lvse.com/site/whst-com-cn-1288.html">SEO优化协会</a></span>
Unknown directive
278
</li>
Syntax not understood
279
<li>
Syntax not understood
280
<span class="site_name"><a href="http://www.lvse.com/site/hisuppliers-com-521.html">中国供应商网</a></span>
Unknown directive
281
</li>
Syntax not understood
282
<li>
Syntax not understood
283
<span class="site_name"><a href="http://www.lvse.com/site/down60-cn-2046.html">网络营销软件下载站</a></span>
Unknown directive
284
</li>
Syntax not understood
285
</ul>
Syntax not understood
286
<div class="cleardiv"></div>
Syntax not understood
287
</div>
Syntax not understood
288
<div class="cleardiv"></div>
Syntax not understood
289
<div class="lvse_border_lt lvse_bg hieht_25" id="rand_shops_list">
Syntax not understood
290
<h2>商城轮播</h2>
Syntax not understood
291
<ul>
Syntax not understood
292
<li>
Syntax not understood
293
<span class="shop_name"><a href="http://www.lvse.com/shop/qiangzhiling-tmall-com-2867.html">蔷栀灵旗舰店</a></span>
Unknown directive
294
</li>
Syntax not understood
295
<li>
Syntax not understood
296
<span class="shop_name"><a href="http://www.lvse.com/shop/lommass-tmall-com-2181.html">龙马仕化妆品旗舰店</a></span>
Unknown directive
297
</li>
Syntax not understood
298
<li>
Syntax not understood
299
<span class="shop_name"><a href="http://www.lvse.com/shop/baimeizhi-tmall-com-758.html">柏美芝服饰旗舰店</a></span>
Unknown directive
300
</li>
Syntax not understood
301
<li>
Syntax not understood
302
<span class="shop_name"><a href="http://www.lvse.com/shop/yiman-tmall-com-6832.html">goulber旗舰店</a></span>
Unknown directive
303
</li>
Syntax not understood
304
<li>
Syntax not understood
305
<span class="shop_name"><a href="http://www.lvse.com/shop/pkbuyer-tmall-com-5478.html">pkbuyer旗舰店</a></span>
Unknown directive
306
</li>
Syntax not understood
307
<li>
Syntax not understood
308
<span class="shop_name"><a href="http://www.lvse.com/shop/yayiman-tmall-com-2477.html">雅伊漫服饰旗舰店</a></span>
Unknown directive
309
</li>
Syntax not understood
310
<li>
Syntax not understood
311
<span class="shop_name"><a href="http://www.lvse.com/shop/roxiexh-tmall-com-8548.html">roxie喜亨专卖店</a></span>
Unknown directive
312
</li>
Syntax not understood
313
<li>
Syntax not understood
314
<span class="shop_name"><a href="http://www.lvse.com/shop/bommie-tmall-com-8374.html">bommie旗舰店</a></span>
Unknown directive
315
</li>
Syntax not understood
316
<li>
Syntax not understood
317
<span class="shop_name"><a href="http://www.lvse.com/shop/pearlion-tmall-com-4324.html">泊莉恩官方旗舰店</a></span>
Unknown directive
318
</li>
Syntax not understood
319
<li>
Syntax not understood
320
<span class="shop_name"><a href="http://www.lvse.com/shop/chuancheng-tmall-com-3420.html">传承旗舰店</a></span>
Unknown directive
321
</li>
Syntax not understood
322
<li>
Syntax not understood
323
<span class="shop_name"><a href="http://www.lvse.com/shop/zhenzhen-tmall-com-9054.html">蓁蓁旗舰店</a></span>
Unknown directive
324
</li>
Syntax not understood
325
<li>
Syntax not understood
326
<span class="shop_name"><a href="http://www.lvse.com/shop/vmaddest-tmall-com-9014.html">vmaddest旗舰店</a></span>
Unknown directive
327
</li>
Syntax not understood
328
<li>
Syntax not understood
329
<span class="shop_name"><a href="http://www.lvse.com/shop/aowei-tmall-com-9050.html">傲威旗舰店</a></span>
Unknown directive
330
</li>
Syntax not understood
331
<li>
Syntax not understood
332
<span class="shop_name"><a href="http://www.lvse.com/shop/shehexw-tmall-com-5087.html">shehe秀沃专卖店</a></span>
Unknown directive
333
</li>
Syntax not understood
334
</ul>
Syntax not understood
335
<div class="cleardiv"></div>
Syntax not understood
336
</div>
Syntax not understood
337
<div class="cleardiv"></div>
Syntax not understood
338
<div id="guide">
Syntax not understood
339
<a href="http://www.lvse.com/about_us" rel="nofollow">关于我们</a> | <a href="http://www.lvse.com/contact" rel="nofollow">联系我们</a> | <a href="http://www.lvse.com/submit" rel="nofollow">贡献网站</a> | <a href="http://www.lvse.com/disclaimer" rel="nofollow">免责声明</a> | <a href="http://www.lvse.com/friend_links" rel="nofollow">友情链接</a> | <a href="http://www.lvse.com/guestbook" rel="nofollow">意见反馈</a> | <a href="http://www.lvse.com/sitemap" rel="nofollow">网站地图</a> |<a href="http://www.lvse.com/support" rel="nofollow">网站帮助</a>| <a href="#gotop" rel="nofollow">返回顶部</a>
Unknown directive
340
</div>
Syntax not understood
341
<div id="foot">目前共收录网站 <span class="site_num_txt">209920</span> 个网站 <span class="site_num_txt">183</span> 个国家 广告客服QQ：3250470014<br />旅色网 版权所有 Copyright © 2011
Syntax not understood
342
<script src='http://w.cnzz.com/c.php?id=30060690' language='JavaScript'></script>
Unknown directive
343
<!--<a href="http://trust.360.cn/search.php" target="_blank" title="360优秀网站"><img src="http://trust.360.cn/img.php?sn=1644&id=5" border="0" /></a>-->
Unknown directive
344
</div>
Syntax not understood
345
</body>
Syntax not understood
346
</html>
Syntax not understood
347
<!-- cached @ 2022-08-30 10:34:03 -->
Unknown directive

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

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

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avgoogle.com on 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.
Avg. (All Categories) 47
Performance 85
Accessibility 48
Best Practices 58
SEO 46
PWA 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.lvse.com/site/google-com-3.html
Updated: 2nd January, 2023
Simulate loading on mobile
85

Performance

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

Metrics

Time to Interactive — 3.0 s
The time taken for the page to become fully interactive.
Speed Index — 3.1 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).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
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://avgoogle.com/
http/1.1
0
201.16799976677
300
0
301
text/html
http://www.lvse.com/site/google-com-3.html
http/1.1
201.5999997966
277.48299995437
5739
17895
200
text/html
Document
http://img1.lvse.com/js/jquery-1.6.2.min.js
http/1.1
286.64600010961
651.12400008366
91820
91556
200
application/javascript
Script
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
http/1.1
286.75099974498
510.33800002187
9711
9449
200
application/javascript
Script
http://www.lvse.com/js/lvse.comm.js
http/1.1
286.85700008646
503.47700016573
42374
42096
200
application/javascript
Script
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
http/1.1
287.10100008175
501.9729998894
24420
24171
200
text/css
Stylesheet
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
http/1.1
287.38800017163
581.77000004798
23382
23133
200
text/css
Stylesheet
http://img.lvse.com/images/i.png
http/1.1
658.72900001705
2815.1030000299
5266
5017
200
image/png
Image
http://w.cnzz.com/c.php?id=30060690
287.25000005215
10476.106999908
0
0
-1
Script
http://www.lvse.com/output/block/json/login_out_box_2/1672649758931
http/1.1
686.96000007913
836.94500010461
947
1413
200
text/html
XHR
http://img.lvse.com/images/bj.gif
http/1.1
688.08100000024
893.32399982959
415
169
200
image/gif
Image
http://img.lvse.com/images/lvse_index_bg.png
http/1.1
688.93699999899
846.96399979293
7471
7222
200
image/png
Image
http://img.lvse.com/images/search_logo.png
http/1.1
689.35000011697
761.49699976668
2567
2319
200
image/png
Image
http://img.lvse.com/images/lvse_search_bg.gif
http/1.1
689.56599989906
831.43599983305
3717
3469
200
image/gif
Image
http://img.lvse.com/images/main.png
http/1.1
886.13699981943
957.88299990818
2331
2083
200
image/png
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)
281.459
10.606
660.437
17.484
677.953
9.837
687.802
99.507
789.312
88.796
879.784
5.004
885.395
66.78
953.383
7.035
10477.643
16.599
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. Avgoogle.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Avgoogle.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 9 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Avgoogle.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
6500
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
2927
Minify JavaScript — Potential savings of 11 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Avgoogle.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.lvse.com/js/lvse.comm.js
42374
11174
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
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)
http://www.lvse.com/site/google-com-3.html
76.878
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Avgoogle.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://avgoogle.com/
630
http://www.lvse.com/site/google-com-3.html
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Avgoogle.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 215 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://img1.lvse.com/js/jquery-1.6.2.min.js
91820
http://www.lvse.com/js/lvse.comm.js
42374
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
9711
http://img.lvse.com/images/lvse_index_bg.png
7471
http://www.lvse.com/site/google-com-3.html
5739
http://img.lvse.com/images/i.png
5266
http://img.lvse.com/images/lvse_search_bg.gif
3717
http://img.lvse.com/images/search_logo.png
2567
Avoids an excessive DOM size — 197 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
197
Maximum DOM Depth
form#login_form > span > a > span
8
Maximum Child Elements
body
16
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Avgoogle.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.2 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)
http://www.lvse.com/site/google-com-3.html
1160.936
27.384
9.008
http://img1.lvse.com/js/jquery-1.6.2.min.js
153.776
119.104
7.684
Unattributable
78.284
7.44
0
Minimizes main-thread work — 1.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
993.672
Script Evaluation
160.52
Other
122.472
Rendering
79.344
Parse HTML & CSS
27.588
Script Parsing & Compilation
20.724
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 — 15 requests • 215 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
15
220460
Script
4
143905
Stylesheet
2
47802
Image
6
21767
Document
1
5739
Other
2
1247
Media
0
0
Font
0
0
Third-party
2
300
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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.0027901902483724
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)
http://www.lvse.com/site/google-com-3.html
1302
199
http://www.lvse.com/site/google-com-3.html
1501
178
http://www.lvse.com/site/google-com-3.html
1679
134
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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

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

Audits

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

Other

Reduce unused CSS — Potential savings of 41 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Avgoogle.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)
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
21300
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
20966
Reduce unused JavaScript — Potential savings of 80 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://img1.lvse.com/js/jquery-1.6.2.min.js
91820
47140
http://www.lvse.com/js/lvse.comm.js
42374
35218
Enable text compression — Potential savings of 130 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://img1.lvse.com/js/jquery-1.6.2.min.js
91556
59445
http://www.lvse.com/js/lvse.comm.js
42096
29753
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24171
19333
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23133
18536
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
9449
6336

Metrics

First Contentful Paint — 3.0 s
The time taken for the first image or text on the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 1,520 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Avgoogle.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)
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
24420
1080
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
23382
1080
http://img1.lvse.com/js/jquery-1.6.2.min.js
91820
1680
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
9711
780
http://www.lvse.com/js/lvse.comm.js
42374
1230
Serve static assets with an efficient cache policy — 11 resources found
Avgoogle.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)
http://img1.lvse.com/js/jquery-1.6.2.min.js
0
91820
http://www.lvse.com/js/lvse.comm.js
0
42374
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
0
24420
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
0
23382
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
0
9711
http://img.lvse.com/images/lvse_index_bg.png
0
7471
http://img.lvse.com/images/i.png
0
5266
http://img.lvse.com/images/lvse_search_bg.gif
0
3717
http://img.lvse.com/images/search_logo.png
0
2567
http://img.lvse.com/images/main.png
0
2331
http://img.lvse.com/images/bj.gif
0
415
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
http://img.lvse.com/images/i.png
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avgoogle.com on mobile screens.
First Contentful Paint (3G) — 6167 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
48

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of avgoogle.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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<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 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"]`
Avgoogle.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
信息提示
对不起，您所访问的页面不存在！ 如果您是站长提交网站，请尽快做好我站友情连接，以便我站尽快审核收录！
网站轮播
商城轮播

Internationalization and localization

`<html>` element does not have 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.
Failing Elements
html

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
div#main > div#notice_msg_box > p > img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
div#login_out_box > form#login_form > span > input
div#login_out_box > form#login_form > span > input
ul > li.searchcontent > form#searchForm > input#key_word
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.

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

Best Practices

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

Audits

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

Audits

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

Audits

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
1.6.2
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 — 15 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://avgoogle.com/
Allowed
http://www.lvse.com/site/google-com-3.html
Allowed
http://img1.lvse.com/js/jquery-1.6.2.min.js
Allowed
http://img1.lvse.com/js/jquery.simplemodal-1.3.js
Allowed
http://www.lvse.com/js/lvse.comm.js
Allowed
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css
Allowed
http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css
Allowed
http://img.lvse.com/images/i.png
Allowed
http://w.cnzz.com/c.php?id=30060690
Allowed
http://www.lvse.com/output/block/json/login_out_box_2/1672649758931
Allowed
http://img.lvse.com/images/bj.gif
Allowed
http://img.lvse.com/images/lvse_index_bg.png
Allowed
http://img.lvse.com/images/search_logo.png
Allowed
http://img.lvse.com/images/lvse_search_bg.gif
Allowed
http://img.lvse.com/images/main.png
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
7
Medium

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
http://img.lvse.com/images/i.png
128 x 128
128 x 128
256 x 256

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

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
SHOW DETAILS
Failed to load resource: net::ERR_TIMED_OUT
46

SEO

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

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

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avgoogle.com on mobile screens.
Document doesn't use 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 not 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 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
div#main > div#notice_msg_box > p > img

Crawling and Indexing

Links are not 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 not valid — 319 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!-- /home/www/lvse/lvse/lvse/html/bf5/bf5173d0ba1a85f6510f4e5570bc771a.html --><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Unknown directive
2
<html>
Syntax not understood
3
<head>
Syntax not understood
4
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Syntax not understood
5
<title>优秀网站大全</title>
Syntax not understood
6
<meta name="description" content="">
Syntax not understood
7
<meta name="keywords" content="旅色网址大全">
Syntax not understood
8
<!-- script type="text/javascript" src="http://lib.sinaapp.com/js/jquery/1.6.2/jquery.min.js"></script -->
Unknown directive
9
<script type="text/javascript" src="http://img1.lvse.com/js/jquery-1.6.2.min.js"></script>
Unknown directive
10
<script type="text/javascript" src="http://img1.lvse.com/js/jquery.simplemodal-1.3.js"></script>
Unknown directive
11
<script type="text/javascript" >
Syntax not understood
12
var APP_BASE_URL = 'http://www.lvse.com';
Unknown directive
13
</script>
Syntax not understood
15
<script type="text/javascript" src="http://www.lvse.com/js/lvse.comm.js"></script>
Unknown directive
17
<link rel="stylesheet" type="text/css" href="http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/global.css" />
Unknown directive
18
<link rel="stylesheet" type="text/css" href="http://cdn.lvse.com/cdn/1652968737_20220830/lvse/views/styles/lvse_20120809/css/page.404_not_found.css" />
Unknown directive
21
</head>
Syntax not understood
22
<body>
Syntax not understood
24
<a name="top"></a>
Syntax not understood
25
<style>
Syntax not understood
30
.search_box #key_word{*width:486px;}
Syntax not understood
32
</style>
Syntax not understood
33
<div id="bar">
Syntax not understood
34
<div id="barleft" style="width:702px;line-height:28px;">
Unknown directive
35
<div id="top_bar_menu">
Syntax not understood
36
<a href="http://www.lvse.com/" class="on" >首页</a>
Unknown directive
37
｜<a href="http://www.lvse.com/guowai" >国外网站</a>
Unknown directive
38
｜<a href="http://www.lvse.com/zhongguo" >国内网站 </a>
Unknown directive
39
｜<a href="http://mall.lvse.com/" >商城大全</a>
Unknown directive
40
｜<a href="http://www.lvse.com/latest/" >更新列表</a>
Unknown directive
41
｜<a href="http://www.lvse.com/jietu" >截图</a>
Unknown directive
42
｜<a href="http://www.lvse.com/zhuanti" >专题 </a>
Unknown directive
43
｜<a href="http://www.lvse.com/fanyi" >翻译</a>
Unknown directive
44
｜<a href="http://alexa.lvse.com" >工具</a>
Unknown directive
45
｜<a href="http://www.lvse.com/news" >新闻</a>
Unknown directive
46
｜<a href="http://www.lvse.com/manage" >运营</a>
Unknown directive
47
｜<a href="http://www.lvse.com/help" >帮助</a>
Unknown directive
48
｜<a href="http://www.lvse.com/submit" >提交网站</a>
Unknown directive
49
</div>
Syntax not understood
51
</div>
Syntax not understood
52
<div id="barright" style="width:276px;">
Unknown directive
53
<ul>
Syntax not understood
54
<li ><i> </i><a id="lvse_set_homepage" href="javascript:void(0);" ohref="http://www.lvse.com/" onclick="lvse.event_stat('set_home_page','http://www.lvse.com/');lvse_setHomePage(this, 'http://www.lvse.com/')" rel="nofollow">设为首页</a></li>
Unknown directive
55
<li class="fav"><i> </i><a href="javascript:addBookmark('优秀网站大全','http://www.lvse.com/robots.txt')" onclick="lvse.event_stat('add_bookmark','http://www.lvse.com/robots.txt');" rel="nofollow">加入收藏</a></li>
Unknown directive
56
<li class="msg"><i> </i><a target="_blank" href="http://www.lvse.com/guestbook" rel="nofollow">网友留言</a></li></ul>
Unknown directive
57
<!-- div id="login_out_bar" style="float:right;margin-right:5px;">
Unknown directive
58
<input class="loin_bt" type="button" value="登入" style="margin-right:5px;" onclick="window.location.href='http://www.lvse.com/login';">
Unknown directive
59
<input class="register_bt" type="button" value="注册" onclick="window.location.href='http://www.lvse.com/register';">
Unknown directive
60
</div -->
Syntax not understood
61
</div>
Syntax not understood
62
</div>
Syntax not understood
63
<div id="top"><a id="gotop"></a>
Syntax not understood
64
<a href="/"><div title="优秀网站大全" id="toplogo" style="width:180px;"></div></a>
Unknown directive
65
<div id="login_out_bar"></div>
Syntax not understood
66
<div id="top_search">
Syntax not understood
67
<div class="search_box">
Syntax not understood
68
<style>#se_logo{_width:30px;_margin:0px}.search_box #key_word{background-position-y: -112px;width: 410px;}.search_box ul{float:left;margin:0px;}</style>
Syntax not understood
69
<div id="se_logo"><span></span></div>
Syntax not understood
70
<ul> <li class="search_tags">
Syntax not understood
71
<a class="on search_tag" default_se="baidu" search_tag="web_page">网页</a>
Syntax not understood
72
<a class="search_tag" default_se="lvse" search_tag="site">网站</a>
Syntax not understood
73
<a class="search_tag" default_se="baidu" search_tag="news">新闻</a>
Syntax not understood
74
<a class="search_tag" default_se="baidu" search_tag="video">视频</a>
Syntax not understood
75
<a class="search_tag" default_se="baidu" search_tag="image">图片</a>
Syntax not understood
76
<a class="search_tag" default_se="baidu" search_tag="map">地图</a>
Syntax not understood
77
<a class="search_tag" default_se="baidu" search_tag="music">音乐</a>
Syntax not understood
78
<a class="search_tag" default_se="taobao" search_tag="shopping">购物</a>
Syntax not understood
79
<a class="search_tag" default_se="baidu" search_tag="know">知道</a>
Syntax not understood
80
<a class="search_tag" default_se="baidu" search_tag="wiki">百科</a>
Syntax not understood
81
<a class="search_tag" default_se="lvse" search_tag="wenzhang">文章</a>
Syntax not understood
82
</li>
Syntax not understood
83
<li class="searchcontent">
Syntax not understood
84
<form style="margin:0px;padding:0px;" method="post" action="" target="_blank" name="search" id="searchForm" charset="gbk" accept-charset="gb2312">
Unknown directive
85
<input type="text" obaiduSug="2" value="" class="searchtext" name="q" id="key_word">
Syntax not understood
86
<input type="hidden" ref="tn" name="tn" value="95426075_hao_pg" />
Syntax not understood
87
<span class="buttonv search_bt" id="search_bt">搜 索 </span>
Syntax not understood
88
</form></li>
Syntax not understood
89
</ul>
Syntax not understood
90
</div>
Syntax not understood
91
<script type="text/javascript">
Syntax not understood
92
var search_tag = 'web_page';
Syntax not understood
93
var se_define_4_baidu = {
Syntax not understood
94
"web_page" : {"se" : "baidu" ,"key_name" : "wd" ,"charset" : "utf-8","method" : "get","action" : "https://www.baidu.com/s"},
Unknown directive
95
"site" : {"se" : "lvse" ,"key_name" : "q" ,"charset" : "utf-8","method" : "post","action" : "http://www.lvse.com/search/site/(*)"},
Unknown directive
96
"news" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://news.baidu.com/ns"},
Unknown directive
97
"video" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://video.baidu.com/v"},
Unknown directive
98
"image" : {"se" : "baidu" ,"key_name" : "word","charset" : "gb2312","method" : "get","action" : "http://image.baidu.com/i"},
Unknown directive
99
"map" : {"se" : "baidu" ,"key_name" : "s" ,"charset" : "gbk","method" : "post","action" : "http://map.baidu.com/?newmap=1&s=(.*)&c=1"},
Unknown directive
100
"music" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://mp3.baidu.com/m"},
Unknown directive
101
"shopping" : {"se" : "taobao","key_name" : "q" ,"charset" : "utf-8","method" : "get","action" : "http://s.taobao.com/search"},
Unknown directive
102
"know" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://zhidao.baidu.com/search"},
Unknown directive
103
"wiki" : {"se" : "baidu" ,"key_name" : "word","charset" : "gbk","method" : "get","action" : "http://baike.baidu.com/searchword/"},
Unknown directive
104
"wenzhang" : {"se" : "lvse" ,"key_name" : "q" ,"charset" : "utf-8","method" : "post","action" : "http://www.lvse.com/search/wenzhang/(*)"}
Unknown directive
105
};
Syntax not understood
107
$(function(){
Syntax not understood
108
$('.search_tag').click(function(){
Syntax not understood
109
search_tag= $(this).attr('search_tag');
Syntax not understood
110
se_define_4_baidu[search_tag]['se']=="lvse" ? $('#searchForm').attr("accept-charset","utf-8") : $('#searchForm').attr("accept-charset","gb2312");
Syntax not understood
111
$('#se_logo span').removeClass().addClass('se_logo_' + se_define_4_baidu[search_tag]['se']);
Syntax not understood
112
$('#se_logo span').html("<a target='_blank' style ='display: block; width:78px;height:35px;text-decoration: none;' href=http://www."+se_define_4_baidu[search_tag]['se']+".com" + (se_define_4_baidu[search_tag]['se'] == 'baidu' ? '?' : '') + "> </a>");
Syntax not understood
114
$('.search_tag').removeClass('on');
Syntax not understood
115
$('.search_tag[search_tag=' + search_tag + ']').addClass('on');
Syntax not understood
116
});
Syntax not understood
117
$('.search_tag[search_tag=web_page]').click();
Syntax not understood
120
$('#search_bt').click(function(){
Syntax not understood
121
var search_from = se_define_4_baidu[search_tag]['se'];
Syntax not understood
122
var search_value = $('#key_word').val();
Syntax not understood
123
var err_msg = '';
Syntax not understood
124
!/\S/.test(search_value) && (err_msg = '请输入搜索内容！');
Syntax not understood
126
if (err_msg != ''){
Syntax not understood
127
alert(err_msg);
Syntax not understood
128
return false;
Syntax not understood
129
}else{
Syntax not understood
131
$('#searchForm').attr({
Syntax not understood
132
'method' : se_define_4_baidu[search_tag]['method'],
Unknown directive
133
'charset' : se_define_4_baidu[search_tag]['charset'],
Unknown directive
134
'action' : se_define_4_baidu[search_tag]['action'].replace('(*)',encodeURIComponent(search_value)).replace('(.*)',encodeURIComponent('s&wd='+search_value))
Unknown directive
135
});
Syntax not understood
136
if (search_tag == 'shopping'){
Syntax not understood
137
$('#searchForm').find('input[ref="tn"]').attr('name','');
Syntax not understood
138
$('#searchForm').find('input[ref="pid"]').attr('name','pid');
Syntax not understood
139
}else{
Syntax not understood
140
$('#searchForm').find('input[ref="tn"]').attr('name','tn');
Syntax not understood
141
$('#searchForm').find('input[ref="pid"]').attr('name','');
Syntax not understood
142
}
Syntax not understood
143
$('#key_word').attr('name',se_define_4_baidu[search_tag]['key_name']);
Syntax not understood
144
document.charset = se_define_4_baidu[search_tag]['charset'];
Syntax not understood
145
$('#searchForm').get(0).submit();
Syntax not understood
146
document.charset = 'utf-8';
Syntax not understood
147
}
Syntax not understood
148
return false;
Syntax not understood
149
});
Syntax not understood
150
$('#key_word').keydown(function(event){
Syntax not understood
151
if(event.keyCode == 13) {
Syntax not understood
152
var search_from = se_define_4_baidu[search_tag]['se'];
Syntax not understood
153
var search_value= $('#key_word').val();
Syntax not understood
154
var err_msg = '';
Syntax not understood
155
!/\S/.test(search_value) && (err_msg = '请输入搜索内容！');
Syntax not understood
157
if (err_msg != ''){
Syntax not understood
158
alert(err_msg);
Syntax not understood
159
return false;
Syntax not understood
160
}else{
Syntax not understood
161
$('#searchForm').attr({
Syntax not understood
162
'method' : se_define_4_baidu[search_tag]['method'],
Unknown directive
163
'charset' : se_define_4_baidu[search_tag]['charset'],
Unknown directive
164
'action' : se_define_4_baidu[search_tag]['action'].replace('(*)',encodeURIComponent(search_value)).replace('(.*)',encodeURIComponent('s&wd='+search_value))
Unknown directive
165
});
Syntax not understood
166
if (search_tag == 'shopping'){
Syntax not understood
167
$('#searchForm').find('input[ref="tn"]').attr('name','');
Syntax not understood
168
$('#searchForm').find('input[ref="pid"]').attr('name','pid');
Syntax not understood
169
}else{
Syntax not understood
170
$('#searchForm').find('input[ref="tn"]').attr('name','tn');
Syntax not understood
171
$('#searchForm').find('input[ref="pid"]').attr('name','');
Syntax not understood
172
}
Syntax not understood
173
$('#key_word').attr('name',se_define_4_baidu[search_tag]['key_name']);
Syntax not understood
174
}
Syntax not understood
175
document.charset = se_define_4_baidu[search_tag]['charset'];
Syntax not understood
176
setTimeout(function(){document.charset = 'utf-8';},500);
Syntax not understood
177
return true;
Syntax not understood
178
}
Syntax not understood
179
}).focus(function(){
Syntax not understood
180
$('#key_word').get(0).select();
Syntax not understood
181
});
Syntax not understood
183
$('.search_box .search_bt').click(function(){this.blur();});
Syntax not understood
185
$('.searchtext').focus(function(){
Syntax not understood
186
if(typeof(BaiduSuggestion) == 'undefined'){
Syntax not understood
187
$.getScript("http://img.lvse.com/js/baidu_opensug.js",function(){
Unknown directive
188
setTimeout(function(){
Syntax not understood
189
BaiduSuggestion.bind('key_word',{"sugSubmit":false},function(txt){
Unknown directive
190
$('#key_word').val(txt);
Syntax not understood
191
$('#search_bt').click();
Syntax not understood
192
});
Syntax not understood
193
},500);
Syntax not understood
194
});
Syntax not understood
195
}
Syntax not understood
196
});
Syntax not understood
197
});
Syntax not understood
198
</script>
Syntax not understood
199
</div>
Syntax not understood
200
</div>
Syntax not understood
203
<div id="ad_banner_outer">
Syntax not understood
204
</div>
Syntax not understood
205
<script type="text/javascript" >
Syntax not understood
206
$(function(){
Syntax not understood
207
if (window.no_ad) {
Syntax not understood
208
return '';
Syntax not understood
209
}
Syntax not understood
210
$.get('/output/block/html/202/0/' + (new Date()).getTime(),function(html){
Syntax not understood
211
$('#ad_banner_outer').html(html);
Syntax not understood
212
});
Syntax not understood
213
});
Syntax not understood
214
</script>
Syntax not understood
216
<div id="crumbs">您的位置：
Syntax not understood
217
<a href="http://www.lvse.com/" rel="nofollow">首页</a>
Unknown directive
218
 > 找不到页面</div>
Syntax not understood
220
<script type="text/javascript" >
Syntax not understood
221
load_userinfo(null,'login_out_box_2');
Syntax not understood
222
</script>
Syntax not understood
226
<div id="main">
Syntax not understood
228
<div id="notice_msg_box" class="lvse_border_lt fff_bg">
Syntax not understood
229
<div class="lvse_bg lvse_inline_border_bottom hieht_25">
Syntax not understood
230
<h2>信息提示</h2>
Syntax not understood
231
</div>
Syntax not understood
232
<p><img src="http://img.lvse.com/images/i.png" /><span class="notice_msg">对不起，您所访问的页面不存在！</span></p>
Unknown directive
233
<br style="clear:both" />
Unknown directive
234
</div>
Syntax not understood
235
<script type="text/javascript" >
Syntax not understood
236
window.no_ad = true;
Syntax not understood
237
</script>
Syntax not understood
238
</div>
Syntax not understood
239
<div class="cleardiv"></div>
Syntax not understood
240
<div class="lvse_border_lt lvse_bg hieht_25" id="rand_sites_list">
Syntax not understood
241
<h2>网站轮播</h2>
Syntax not understood
242
<ul>
Syntax not understood
243
<li>
Syntax not understood
244
<span class="site_name"><a href="http://www.lvse.com/site/t-fumu-com-2412.html">父母网微博</a></span>
Unknown directive
245
</li>
Syntax not understood
246
<li>
Syntax not understood
247
<span class="site_name"><a href="http://www.lvse.com/site/kishairlines-ir-2719.html">基什航空</a></span>
Unknown directive
248
</li>
Syntax not understood
249
<li>
Syntax not understood
250
<span class="site_name"><a href="http://www.lvse.com/site/hostucan-cn-5594.html">主机点评网</a></span>
Unknown directive
251
</li>
Syntax not understood
252
<li>
Syntax not understood
253
<span class="site_name"><a href="http://www.lvse.com/site/1stenglish-com-601.html">第一英语在线</a></span>
Unknown directive
254
</li>
Syntax not understood
255
<li>
Syntax not understood
256
<span class="site_name"><a href="http://www.lvse.com/site/wiki-ename-cn-1648.html">域名百科</a></span>
Unknown directive
257
</li>
Syntax not understood
258
<li>
Syntax not understood
259
<span class="site_name"><a href="http://www.lvse.com/site/31jiaju-com-5460.html">中国家具网</a></span>
Unknown directive
260
</li>
Syntax not understood
261
<li>
Syntax not understood
262
<span class="site_name"><a href="http://www.lvse.com/site/cbrx-com-602.html">赤壁热线</a></span>
Unknown directive
263
</li>
Syntax not understood
264
<li>
Syntax not understood
265
<span class="site_name"><a href="http://www.lvse.com/site/zhhzw-com-2218.html">中华合租网</a></span>
Unknown directive
266
</li>
Syntax not understood
267
<li>
Syntax not understood
268
<span class="site_name"><a href="http://www.lvse.com/site/dailybooth-com-1207.html">Dailybooth</a></span>
Unknown directive
269
</li>
Syntax not understood
270
<li>
Syntax not understood
271
<span class="site_name"><a href="http://www.lvse.com/site/qdppc-com-3537.html">起点手机论坛</a></span>
Unknown directive
272
</li>
Syntax not understood
273
<li>
Syntax not understood
274
<span class="site_name"><a href="http://www.lvse.com/site/clarin-com-841.html">阿根廷号角报</a></span>
Unknown directive
275
</li>
Syntax not understood
276
<li>
Syntax not understood
277
<span class="site_name"><a href="http://www.lvse.com/site/whst-com-cn-1288.html">SEO优化协会</a></span>
Unknown directive
278
</li>
Syntax not understood
279
<li>
Syntax not understood
280
<span class="site_name"><a href="http://www.lvse.com/site/hisuppliers-com-521.html">中国供应商网</a></span>
Unknown directive
281
</li>
Syntax not understood
282
<li>
Syntax not understood
283
<span class="site_name"><a href="http://www.lvse.com/site/down60-cn-2046.html">网络营销软件下载站</a></span>
Unknown directive
284
</li>
Syntax not understood
285
</ul>
Syntax not understood
286
<div class="cleardiv"></div>
Syntax not understood
287
</div>
Syntax not understood
288
<div class="cleardiv"></div>
Syntax not understood
289
<div class="lvse_border_lt lvse_bg hieht_25" id="rand_shops_list">
Syntax not understood
290
<h2>商城轮播</h2>
Syntax not understood
291
<ul>
Syntax not understood
292
<li>
Syntax not understood
293
<span class="shop_name"><a href="http://www.lvse.com/shop/qiangzhiling-tmall-com-2867.html">蔷栀灵旗舰店</a></span>
Unknown directive
294
</li>
Syntax not understood
295
<li>
Syntax not understood
296
<span class="shop_name"><a href="http://www.lvse.com/shop/lommass-tmall-com-2181.html">龙马仕化妆品旗舰店</a></span>
Unknown directive
297
</li>
Syntax not understood
298
<li>
Syntax not understood
299
<span class="shop_name"><a href="http://www.lvse.com/shop/baimeizhi-tmall-com-758.html">柏美芝服饰旗舰店</a></span>
Unknown directive
300
</li>
Syntax not understood
301
<li>
Syntax not understood
302
<span class="shop_name"><a href="http://www.lvse.com/shop/yiman-tmall-com-6832.html">goulber旗舰店</a></span>
Unknown directive
303
</li>
Syntax not understood
304
<li>
Syntax not understood
305
<span class="shop_name"><a href="http://www.lvse.com/shop/pkbuyer-tmall-com-5478.html">pkbuyer旗舰店</a></span>
Unknown directive
306
</li>
Syntax not understood
307
<li>
Syntax not understood
308
<span class="shop_name"><a href="http://www.lvse.com/shop/yayiman-tmall-com-2477.html">雅伊漫服饰旗舰店</a></span>
Unknown directive
309
</li>
Syntax not understood
310
<li>
Syntax not understood
311
<span class="shop_name"><a href="http://www.lvse.com/shop/roxiexh-tmall-com-8548.html">roxie喜亨专卖店</a></span>
Unknown directive
312
</li>
Syntax not understood
313
<li>
Syntax not understood
314
<span class="shop_name"><a href="http://www.lvse.com/shop/bommie-tmall-com-8374.html">bommie旗舰店</a></span>
Unknown directive
315
</li>
Syntax not understood
316
<li>
Syntax not understood
317
<span class="shop_name"><a href="http://www.lvse.com/shop/pearlion-tmall-com-4324.html">泊莉恩官方旗舰店</a></span>
Unknown directive
318
</li>
Syntax not understood
319
<li>
Syntax not understood
320
<span class="shop_name"><a href="http://www.lvse.com/shop/chuancheng-tmall-com-3420.html">传承旗舰店</a></span>
Unknown directive
321
</li>
Syntax not understood
322
<li>
Syntax not understood
323
<span class="shop_name"><a href="http://www.lvse.com/shop/zhenzhen-tmall-com-9054.html">蓁蓁旗舰店</a></span>
Unknown directive
324
</li>
Syntax not understood
325
<li>
Syntax not understood
326
<span class="shop_name"><a href="http://www.lvse.com/shop/vmaddest-tmall-com-9014.html">vmaddest旗舰店</a></span>
Unknown directive
327
</li>
Syntax not understood
328
<li>
Syntax not understood
329
<span class="shop_name"><a href="http://www.lvse.com/shop/aowei-tmall-com-9050.html">傲威旗舰店</a></span>
Unknown directive
330
</li>
Syntax not understood
331
<li>
Syntax not understood
332
<span class="shop_name"><a href="http://www.lvse.com/shop/shehexw-tmall-com-5087.html">shehe秀沃专卖店</a></span>
Unknown directive
333
</li>
Syntax not understood
334
</ul>
Syntax not understood
335
<div class="cleardiv"></div>
Syntax not understood
336
</div>
Syntax not understood
337
<div class="cleardiv"></div>
Syntax not understood
338
<div id="guide">
Syntax not understood
339
<a href="http://www.lvse.com/about_us" rel="nofollow">关于我们</a> | <a href="http://www.lvse.com/contact" rel="nofollow">联系我们</a> | <a href="http://www.lvse.com/submit" rel="nofollow">贡献网站</a> | <a href="http://www.lvse.com/disclaimer" rel="nofollow">免责声明</a> | <a href="http://www.lvse.com/friend_links" rel="nofollow">友情链接</a> | <a href="http://www.lvse.com/guestbook" rel="nofollow">意见反馈</a> | <a href="http://www.lvse.com/sitemap" rel="nofollow">网站地图</a> |<a href="http://www.lvse.com/support" rel="nofollow">网站帮助</a>| <a href="#gotop" rel="nofollow">返回顶部</a>
Unknown directive
340
</div>
Syntax not understood
341
<div id="foot">目前共收录网站 <span class="site_num_txt">209920</span> 个网站 <span class="site_num_txt">183</span> 个国家 广告客服QQ：3250470014<br />旅色网 版权所有 Copyright © 2011
Syntax not understood
342
<script src='http://w.cnzz.com/c.php?id=30060690' language='JavaScript'></script>
Unknown directive
343
<!--<a href="http://trust.360.cn/search.php" target="_blank" title="360优秀网站"><img src="http://trust.360.cn/img.php?sn=1644&id=5" border="0" /></a>-->
Unknown directive
344
</div>
Syntax not understood
345
</body>
Syntax not understood
346
</html>
Syntax not understood
347
<!-- cached @ 2022-08-30 10:34:03 -->
Unknown directive

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

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

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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of avgoogle.com on 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: 47.254.33.193
Continent: North America
Country: United States
United States Flag
Region: California
City: San Mateo
Longitude: -122.3276
Latitude: 37.5507
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
ALICLOUD-US
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
eName Technology Co.,Ltd. 117.25.139.79
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

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: 26th March, 2023
Content-Type: text/html; charset=utf-8
Connection: keep-alive

Whois Lookup

Created: 27th December, 2009
Changed: 25th January, 2024
Expires: 27th December, 2024
Registrar: eName Technology Co.,Ltd.
Status: clientTransferProhibited
clientDeleteProhibited
Nameservers: ns3.dns.com
ns4.dns.com
Owner State: guang dong
Owner Country: CN
Owner Email: https://whois.ename.net/contact/avgoogle.com
Admin Email: https://whois.ename.net/contact/avgoogle.com
Tech Email: https://whois.ename.net/contact/avgoogle.com
Full Whois: Domain Name: avgoogle.com
Registry Domain ID: 1580062024_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.ename.com
Registrar URL: http://www.ename.net
Updated Date: 2024-01-25T06:53:33Z
Creation Date: 2009-12-27T19:42:26Z
Registrar Registration Expiration Date: 2024-12-27T19:42:26Z
Registrar: eName Technology Co.,Ltd.
Registrar IANA ID: 1331
Registrar Abuse Contact Email: abuse@ename.com
Registrar Abuse Contact Phone: +86.4000044400
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Registrant State/Province: guang dong
Registrant Country: CN
Registrant Email: https://whois.ename.net/contact/avgoogle.com
Admin Email: https://whois.ename.net/contact/avgoogle.com
Tech Email: https://whois.ename.net/contact/avgoogle.com
Name Server:ns3.dns.com
Name Server:ns4.dns.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-04-23T06:14:28Z <<<

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
View Raw Whois

Nameservers

Name IP Address
ns3.dns.com 218.98.111.173
ns4.dns.com 183.253.57.199
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
avgoogle.cc
0/5
avgoogle.info
0/5
avgoogle.net
$848 USD 1/5
avgoogle.tv
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
2345wang.com
0/5
myarticle.com
$13,704 USD 3/5
tahoo.com
0/5
taoba.com
$3,921 USD 3/5
yougoogle.com
0/5
Love W3 Snoop?
Update Now

Recently Updated

instagram.com
naturisten.se
eastanime.com
woprime.com
pornxia.com
stickmanhook911.com
trueluvv.com
womensjournal.com
roblox.com
velvetclassic.net

Recently Viewed

thecityoflights.net
szbbw.net
aaaacccc.com
l-eco.fr
jor-alkhaer.com
quicksellthemes.com
genprison.net
biasy.net
smeeo.com
ziffdavisenterprise.com