Tools & Wizards About Us

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

audio160.com

【音响网】专注音响品牌整合与传播 - 音响行业门户

Page Load Speed

67.7 sec in total

First Response

6.1 sec

Resources Loaded

61.1 sec

Page Rendered

429 ms

About Website

Welcome to audio160.com homepage info - get ready to check Audio 160 best content for China right away, or after learning these important things about audio160.com

音响网专注音响品牌整合与传播,提供专业音响、汽车音响、家用音响,专业音响等品牌相关音响技术,音响论坛,音响故障分析,提供音响与音响最新品牌产品及资讯的专业音响行业门户平台网站。

Visit audio160.com

Key Findings

We analyzed Audio160.com page load time and found that the first response time was 6.1 sec and then it took 61.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

audio160.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value35.1 s

0/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.265

46/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

audio160.com

6122 ms

index2013.6.18.css

6839 ms

lrtk.css

882 ms

koala.min.1.5.js

7937 ms

jquery-1.7.min.js

12880 ms

Our browser made a total of 320 requests to load all elements on the main page. We found that 90% of them (288 requests) were addressed to the original Audio160.com, 6% (18 requests) were made to Ke.audio160.com and 3% (10 requests) were made to Ebook.audio160.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Audio160.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 466.0 kB (11%)

Content Size

4.3 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Audio160.com main page is 4.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 121.1 kB

  • Original 149.8 kB
  • After minification 145.7 kB
  • After compression 28.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 121.1 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 103.6 kB

  • Original 3.9 MB
  • After minification 3.8 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Audio 160 images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 198.8 kB

  • Original 262.9 kB
  • After minification 211.6 kB
  • After compression 64.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 198.8 kB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 42.5 kB

  • Original 50.3 kB
  • After minification 43.2 kB
  • After compression 7.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Audio160.com needs all CSS files to be minified and compressed as it can save up to 42.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (13%)

Requests Now

316

After Optimization

274

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 316 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Audio 160. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

audio160.com accessibility score

33

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

audio160.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

audio160.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Audio160.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Audio160.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Audio 160. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: