Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

54.3 sec in total

First Response

15.2 sec

Resources Loaded

38.9 sec

Page Rendered

139 ms

2kk.us screenshot

About Website

Click here to check amazing 2 Kk content for China. Otherwise, check out these important facts you probably never knew about 2kk.us

Visit 2kk.us

Key Findings

We analyzed 2kk.us page load time and found that the first response time was 15.2 sec and then it took 39 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

2kk.us performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

2kk.us

15246 ms

exit.js

3863 ms

2246700.js

827 ms

stat.php

4247 ms

a1.jpg

155 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original 2kk.us, 9% (1 request) were made to Baiducdn.oss-cn-hangzhou.aliyuncs.com and 9% (1 request) were made to Js.users.51.la. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Vip.51.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.6 kB (67%)

Content Size

23.4 kB

After Optimization

7.8 kB

In fact, the total size of 2kk.us main page is 23.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 13.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.3 kB

  • Original 10.2 kB
  • After minification 10.1 kB
  • After compression 2.8 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 7.3 kB or 72% of the original size.

JavaScript Optimization

-63%

Potential reduce by 8.3 kB

  • Original 13.2 kB
  • After minification 13.1 kB
  • After compression 4.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 8.3 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

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

Accessibility Review

2kk.us accessibility score

68

Accessibility Issues

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

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

2kk.us best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

2kk.us SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2kk.us can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 2kk.us 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 2 Kk. 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: