Tools & Wizards About Us
nillkin.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

nillkin.com

NILLKIN耐尔金 智·简生活数码品牌

Page Load Speed

64.8 sec in total

First Response

2.1 sec

Resources Loaded

62.5 sec

Page Rendered

266 ms

nillkin.com screenshot

About Website

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

深圳市耐尔金科技有限公司|智·简生活数码品牌|NILLKIN 创新,简约,完美|NILLKIN 致力于3C数码产品的研发,生产

Visit nillkin.com

Key Findings

We analyzed Nillkin.com page load time and found that the first response time was 2.1 sec and then it took 62.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 44 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

nillkin.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

nillkin.com

2051 ms

8812 ms

style1.css

10005 ms

AC_RunActiveContent.js

10201 ms

index.css

911 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 87% of them (78 requests) were addressed to the original Nillkin.com, 11% (10 requests) were made to V3.jiathis.com and 1% (1 request) were made to Js.users.51.la. The less responsive or slowest element that took the longest time to load (20.9 sec) belongs to the original domain Nillkin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.8 kB (47%)

Content Size

375.6 kB

After Optimization

198.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nillkin.com main page is 375.6 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. 20% of websites need less resources to load. Images take 190.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 57.9 kB

  • Original 69.2 kB
  • After minification 62.0 kB
  • After compression 11.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 57.9 kB or 84% of the original size.

Image Optimization

-16%

Potential reduce by 30.2 kB

  • Original 190.0 kB
  • After minification 159.8 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. Obviously, Nillkin needs image optimization as it can save up to 30.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 20.1 kB

  • Original 37.8 kB
  • After minification 34.0 kB
  • After compression 17.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 20.1 kB or 53% of the original size.

CSS Optimization

-87%

Potential reduce by 68.7 kB

  • Original 78.6 kB
  • After minification 69.4 kB
  • After compression 9.9 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. Nillkin.com needs all CSS files to be minified and compressed as it can save up to 68.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (34%)

Requests Now

44

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nillkin.com

nillkin.com

2051 ms

8812 ms

style1.css

style1.css

10005 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

10201 ms

index.css

index.css

911 ms

project.js

project.js

19926 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

11875 ms

jquery.cycle.all_2.js

jquery.cycle.all_2.js

15131 ms

stat.asp

stat.asp

2163 ms

15106619.js

15106619.js

971 ms

jiathis_r.js

jiathis_r.js

726 ms

menu_bk.png

menu_bk.png

435 ms

cnweixin.png

cnweixin.png

4666 ms

weixin.png

weixin.png

446 ms

ks.png

ks.png

353 ms

ss.png

ss.png

783 ms

rz.png

rz.png

901 ms

rzbtn.png

rzbtn.png

3785 ms

logo1.gif

logo1.gif

2393 ms

cn_fw.gif

cn_fw.gif

915 ms

share.png

share.png

11138 ms

pro_item_new.png

pro_item_new.png

3008 ms

2016331194720933.jpg

2016331194720933.jpg

5615 ms

2016331185359377.jpg

2016331185359377.jpg

3728 ms

2016331165516314.jpg

2016331165516314.jpg

5204 ms

2016331155653985.jpg

2016331155653985.jpg

6291 ms

2016331144917953.jpg

2016331144917953.jpg

19849 ms

2016331123521869.jpg

2016331123521869.jpg

6060 ms

2016331112947842.jpg

2016331112947842.jpg

6597 ms

2016331125527993.jpg

2016331125527993.jpg

19986 ms

2016329175426803.jpg

2016329175426803.jpg

9192 ms

201632910318734.jpg

201632910318734.jpg

11466 ms

201511315347778.jpg

201511315347778.jpg

9401 ms

20151030135944709.jpg

20151030135944709.jpg

12823 ms

2015912164347779.jpg

2015912164347779.jpg

12956 ms

20159815114918.jpg

20159815114918.jpg

20018 ms

201551313427302.jpg

201551313427302.jpg

15434 ms

201647141739974.jpg

201647141739974.jpg

20023 ms

201647141543531.jpg

201647141543531.jpg

20023 ms

201641134025581.jpg

201641134025581.jpg

20023 ms

201641133919948.jpg

201641133919948.jpg

20028 ms

201639181058210.jpg

201639181058210.jpg

20030 ms

20163918845272.jpg

20163918845272.jpg

20030 ms

2016215172534758.jpg

2016215172534758.jpg

20030 ms

2016215172217859.jpg

2016215172217859.jpg

20031 ms

index_footer_bk.gif

index_footer_bk.gif

20030 ms

top.gif

top.gif

20016 ms

icon_9.gif

icon_9.gif

819 ms

jiathis_utility.html

jiathis_utility.html

11 ms

jiathis_share.css

jiathis_share.css

25 ms

ckepop.js

ckepop.js

13 ms

ckecenterpop.js

ckecenterpop.js

13 ms

plugin.client.js

plugin.client.js

10 ms

r.gif

r.gif

144 ms

img_exit.gif

img_exit.gif

21 ms

img_012.gif

img_012.gif

22 ms

jiathis_ico.png

jiathis_ico.png

39 ms

logo.png

logo.png

19697 ms

hotline.png

hotline.png

19616 ms

search.gif

search.gif

19604 ms

divLi_bk0.png

divLi_bk0.png

20212 ms

lineY.png

lineY.png

20094 ms

bg-kv.gif

bg-kv.gif

20078 ms

20164110734402.jpg

20164110734402.jpg

19608 ms

20164110237971.jpg

20164110237971.jpg

20032 ms

20163416487162.jpg

20163416487162.jpg

20287 ms

20162195543292.jpg

20162195543292.jpg

20236 ms

201612914148571.jpg

201612914148571.jpg

20331 ms

20151211125449872.jpg

20151211125449872.jpg

19784 ms

2015123125417184.jpg

2015123125417184.jpg

20376 ms

201512212331809.jpg

201512212331809.jpg

19929 ms

201511717912525.jpg

201511717912525.jpg

19699 ms

2015121135417109.jpg

2015121135417109.jpg

20387 ms

201512212349208.jpg

201512212349208.jpg

19794 ms

2015112791537158.jpg

2015112791537158.jpg

19583 ms

2015820132442192.jpg

2015820132442192.jpg

19867 ms

201562416613118.jpg

201562416613118.jpg

19531 ms

2015319114426713.jpg

2015319114426713.jpg

20853 ms

2015121135531221.jpg

2015121135531221.jpg

20722 ms

arrow_prev.png

arrow_prev.png

19551 ms

arrow_next.png

arrow_next.png

19404 ms

pages_index_bk.gif

pages_index_bk.gif

19966 ms

index_box_bk.gif

index_box_bk.gif

19630 ms

line_style.jpg

line_style.jpg

19961 ms

line_style_1.gif

line_style_1.gif

19961 ms

line_style_2.gif

line_style_2.gif

19957 ms

footer_bk.gif

footer_bk.gif

19955 ms

line.png

line.png

19955 ms

Count.asp

Count.asp

19955 ms

pro_item_style.png

pro_item_style.png

19955 ms

Accessibility Review

nillkin.com accessibility score

60

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.

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

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

nillkin.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

nillkin.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 doesn't use 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 Nillkin.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 Nillkin.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

nillkin.com

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