Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    29% of websites

  • 62

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

17.4 sec in total

First Response

1.2 sec

Resources Loaded

15.9 sec

Page Rendered

333 ms

1616.net screenshot

About Website

Click here to check amazing 1616 content for China. Otherwise, check out these important facts you probably never knew about 1616.net

Visit 1616.net

Key Findings

We analyzed 1616.net page load time and found that the first response time was 1.2 sec and then it took 16.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

1616.net performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value5.2 s

61/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

1616.net

1164 ms

www.1616.net

387 ms

www_1616_0927.css

2456 ms

jquery-1.7.1.min.js

2769 ms

common.js

2230 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 30% of them (26 requests) were addressed to the original 1616.net, 23% (20 requests) were made to Pic2.kangjianw.com and 19% (17 requests) were made to R.61658.com. The less responsive or slowest element that took the longest time to load (7.6 sec) relates to the external source Pic2.kangjianw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (39%)

Content Size

3.5 MB

After Optimization

2.1 MB

In fact, the total size of 1616.net main page is 3.5 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. 30% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 46.8 kB

  • Original 65.1 kB
  • After minification 64.8 kB
  • After compression 18.3 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 46.8 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 113.6 kB

  • Original 1.8 MB
  • After minification 1.7 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. 1616 images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 896.5 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 329.9 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 896.5 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 302.5 kB

  • Original 360.9 kB
  • After minification 310.7 kB
  • After compression 58.4 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. 1616.net needs all CSS files to be minified and compressed as it can save up to 302.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (6%)

Requests Now

85

After Optimization

80

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

Accessibility Review

1616.net accessibility score

58

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

Best Practices

1616.net best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

1616.net SEO score

62

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1616.net 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 1616.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of 1616. 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: