Tools & Wizards About Us
ingkee.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

ingkee.com

映客直播－看直播,玩直播,尽在映客APP

Page Load Speed

5.5 sec in total

First Response

1.4 sec

Resources Loaded

3.8 sec

Page Rendered

219 ms

ingkee.com screenshot

About Website

Visit ingkee.com now to see the best up-to-date Ingkee content for China and also check out these interesting facts you probably never knew about ingkee.com

映客直播,实时、高清、快捷、流畅的视频直播平台,中国全新的视频社交媒体,明星大咖、网络红人、时尚娱乐、高颜值、视频交友等尽在映客直播app

Visit ingkee.com

Key Findings

We analyzed Ingkee.com page load time and found that the first response time was 1.4 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

ingkee.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

ingkee.com

1427 ms

normalize.min.css

384 ms

index.css

238 ms

new-cn.css

460 ms

animate.min.css

468 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 42% of them (15 requests) were addressed to the original Ingkee.com, 50% (18 requests) were made to Img.ikstatic.cn and 6% (2 requests) were made to Static.inke.cn. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ingkee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.6 kB (15%)

Content Size

498.3 kB

After Optimization

421.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ingkee.com main page is 498.3 kB. 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 275.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 58.0 kB

  • Original 68.8 kB
  • After minification 68.8 kB
  • After compression 10.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 58.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 25 B

  • Original 275.0 kB
  • After minification 275.0 kB

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. Ingkee images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 16.9 kB

  • Original 141.6 kB
  • After minification 141.3 kB
  • After compression 124.7 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 16.9 kB or 12% of the original size.

CSS Optimization

-13%

Potential reduce by 1.7 kB

  • Original 12.9 kB
  • After minification 12.9 kB
  • After compression 11.2 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. Ingkee.com needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (85%)

Requests Now

34

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ingkee.com

ingkee.com

1427 ms

normalize.min.css

normalize.min.css

384 ms

index.css

index.css

238 ms

new-cn.css

new-cn.css

460 ms

animate.min.css

animate.min.css

468 ms

xgplayer.min.js

xgplayer.min.js

1170 ms

xgplayer-flv.min.js

xgplayer-flv.min.js

1192 ms

md5.min.js

md5.min.js

512 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

412 ms

wow.min.js

wow.min.js

690 ms

base.js

base.js

703 ms

header-control.js

header-control.js

706 ms

xgplayer_plugins.js

xgplayer_plugins.js

922 ms

index.js

index.js

937 ms

new-cn.js

new-cn.js

942 ms

wenwangwen.js

wenwangwen.js

1152 ms

MTQ5NjczMjc0MTUxOCM0NTgjanBn.jpg

MTQ5NjczMjc0MTUxOCM0NTgjanBn.jpg

393 ms

new-cn.css

new-cn.css

718 ms

MTYwNDYzMzMzNDYzNiMgNDIjcG5n.png

MTYwNDYzMzMzNDYzNiMgNDIjcG5n.png

516 ms

MTYwNDYzMjY5MTU5NyM0OTAjcG5n.png

MTYwNDYzMjY5MTU5NyM0OTAjcG5n.png

450 ms

MTYwNDYzMzA3MTA2OCMxMTUjcG5n.png

MTYwNDYzMzA3MTA2OCMxMTUjcG5n.png

453 ms

MTYwNDM3MTEyMjI1MiM2OTQjcG5n.png

MTYwNDM3MTEyMjI1MiM2OTQjcG5n.png

457 ms

MTYwNDYzMjIwMzM5NiM5MzMjcG5n.png

MTYwNDYzMjIwMzM5NiM5MzMjcG5n.png

464 ms

MTYwNDM5OTI5ODY0NCM3NTkjcG5n.png

MTYwNDM5OTI5ODY0NCM3NTkjcG5n.png

469 ms

MTYwNDY0NTAwMjgzNiM5NjAjcG5n.png

MTYwNDY0NTAwMjgzNiM5NjAjcG5n.png

473 ms

MTYwNDYzMTM3NzAxMCMxMzYjcG5n.png

MTYwNDYzMTM3NzAxMCMxMzYjcG5n.png

480 ms

MTYwNDg4Nzk2MTQ0NiMxMzIjcG5n.png

MTYwNDg4Nzk2MTQ0NiMxMzIjcG5n.png

28 ms

MTYwNDg4Nzk4MzA3NCM0ODIjcG5n.png

MTYwNDg4Nzk4MzA3NCM0ODIjcG5n.png

23 ms

MTYwNDYzMTkxMTQxNSM5MjcjcG5n.png

MTYwNDYzMTkxMTQxNSM5MjcjcG5n.png

22 ms

MTYwNDYzMTg5NzM5NSM4NTIjcG5n.png

MTYwNDYzMTg5NzM5NSM4NTIjcG5n.png

24 ms

MTYwNDg4NzQyNzU2OCMxMTEjcG5n.png

MTYwNDg4NzQyNzU2OCMxMTEjcG5n.png

21 ms

MTYwNDc0MzQwNDU4NSMxOTYjcG5n.png

MTYwNDc0MzQwNDU4NSMxOTYjcG5n.png

25 ms

MTYwNDg4NzgzMDQyOSM5NDQjcG5n.png

MTYwNDg4NzgzMDQyOSM5NDQjcG5n.png

40 ms

MTYwNDYzMTEzMDAyMSMxOTUjcG5n.png

MTYwNDYzMTEzMDAyMSMxOTUjcG5n.png

41 ms

MTYwNDg4NzIzMzcxOSM2OTgjcG5n.png

MTYwNDg4NzIzMzcxOSM2OTgjcG5n.png

44 ms

hm.js

hm.js

1161 ms

Accessibility Review

ingkee.com accessibility score

67

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

ingkee.com best practices score

67

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

Page has valid source maps

SEO Factors

ingkee.com SEO score

54

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

High

robots.txt is not valid

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ingkee.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Ingkee.com 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

ingkee.com

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