Tools & Wizards About Us
rnkey.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 50

    SEO

    Google-friendlier than
    19% of websites

rnkey.com

珠海云际科技有限公司官网-工业级PDA手持终端、数据采集器-物联网软件整体集成方案提供商、物流仓储软件、ERP/进销存软件、Wince/WinMobile/安卓设备/IOS平台/APP开发、微信公众平台开发、ERP对接PDA开发、移动智能办公、珠海软件开发、珠海软件定制、珠海网站建设、珠海PDA软件...

Page Load Speed

46.8 sec in total

First Response

2.8 sec

Resources Loaded

43.1 sec

Page Rendered

903 ms

rnkey.com screenshot

About Website

Click here to check amazing Rnkey content. Otherwise, check out these important facts you probably never knew about rnkey.com

珠海云际科技有限公司专业从事PDA手持终端、数据采集器、条码扫描枪软硬件研发,专门为中小型企业、工厂提供软件定制、软件开发、 OA办公系统、ERP生产管理软件、仓库管理软件、仓储条码管理软件、进销存软件、ERP管理系统、PDA对接网店管家。目前独立开发：《物联管家PDA系统》-网店管家PDA版 网店管家的好帮手，全面对接网店管家，研发Windows CE系统下的进销存配送系统

Visit rnkey.com

Key Findings

We analyzed Rnkey.com page load time and found that the first response time was 2.8 sec and then it took 44 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 22 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

rnkey.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value46.5 s

0/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

rnkey.com

2812 ms

styles.css

2194 ms

prettyPhoto.css

4367 ms

home.css

954 ms

lwn.css

1646 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 92% of them (81 requests) were addressed to the original Rnkey.com, 7% (6 requests) were made to Bdimg.share.baidu.com and 1% (1 request) were made to Api.share.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Rnkey.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 285.0 kB (73%)

Content Size

392.5 kB

After Optimization

107.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rnkey.com main page is 392.5 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. Javascripts take 151.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.8 kB

  • Original 41.5 kB
  • After minification 34.5 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 7.0 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.8 kB or 79% of the original size.

Image Optimization

-69%

Potential reduce by 77.0 kB

  • Original 111.6 kB
  • After minification 34.6 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, Rnkey needs image optimization as it can save up to 77.0 kB or 69% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 103.6 kB

  • Original 151.4 kB
  • After minification 145.9 kB
  • After compression 47.8 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 103.6 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 71.6 kB

  • Original 88.0 kB
  • After minification 71.2 kB
  • After compression 16.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. Rnkey.com needs all CSS files to be minified and compressed as it can save up to 71.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (48%)

Requests Now

64

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rnkey.com

rnkey.com

2812 ms

styles.css

styles.css

2194 ms

prettyPhoto.css

prettyPhoto.css

4367 ms

home.css

home.css

954 ms

lwn.css

lwn.css

1646 ms

lanrenzhijia.css

lanrenzhijia.css

1374 ms

jquery.min.js

jquery.min.js

10019 ms

jquery.tools.min.js

jquery.tools.min.js

2175 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

4066 ms

general.js

general.js

2648 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

2599 ms

home.js

home.js

3055 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

3115 ms

menu.css

menu.css

3496 ms

mootools-yui-compressed.js

mootools-yui-compressed.js

9363 ms

sexylightbox.v2.3.mootools.min.js

sexylightbox.v2.3.mootools.min.js

5592 ms

sexylightbox.css

sexylightbox.css

3906 ms

service.js

service.js

3828 ms

js.js

js.js

4071 ms

topnav_bg.png

topnav_bg.png

480 ms

rnkeylogo.png

rnkeylogo.png

3371 ms

slider1_image_3.jpg

slider1_image_3.jpg

14721 ms

slider1_image_2.jpg

slider1_image_2.jpg

13520 ms

slider1_image_1.jpg

slider1_image_1.jpg

10421 ms

title_bar_bg.gif

title_bar_bg.gif

434 ms

title_bar_shadow.gif

title_bar_shadow.gif

20463 ms

icon_rss.png

icon_rss.png

2583 ms

buttons_large_bg.png

buttons_large_bg.png

3505 ms

temp_img_1.png

temp_img_1.png

7010 ms

ico_plus.png

ico_plus.png

3941 ms

temp_img_2.png

temp_img_2.png

10101 ms

temp_img_3.png

temp_img_3.png

15941 ms

adbanner.gif

adbanner.gif

18834 ms

more.png

more.png

10925 ms

2114211961.jpg

2114211961.jpg

15769 ms

129122969.png

129122969.png

20458 ms

1554200189.jpg

1554200189.jpg

20459 ms

104099625.jpg

104099625.jpg

20328 ms

225711953.jpg

225711953.jpg

19612 ms

215044233.jpg

215044233.jpg

20459 ms

btm.gif

btm.gif

20023 ms

112111517.PNG

112111517.PNG

20459 ms

1141544389.png

1141544389.png

20460 ms

2048166577.png

2048166577.png

20461 ms

1154566161.png

1154566161.png

20463 ms

18477877.jpg

18477877.jpg

20463 ms

1723533181.png

1723533181.png

20465 ms

1818422721.png

1818422721.png

20465 ms

1335488877.png

1335488877.png

20465 ms

2040255001.png

2040255001.png

20465 ms

1359300549.png

1359300549.png

20466 ms

2321288569.jpg

2321288569.jpg

20387 ms

1810588185.png

1810588185.png

20386 ms

1857544433.png

1857544433.png

20387 ms

1852399609.png

1852399609.png

20388 ms

shell_v2.js

shell_v2.js

6752 ms

1152399873.png

1152399873.png

20051 ms

1437255369.jpg

1437255369.jpg

20050 ms

index_03.jpg

index_03.jpg

19879 ms

arrow.gif

arrow.gif

17983 ms

client.gif

client.gif

18305 ms

1.gif

1.gif

19518 ms

logger.js

logger.js

444 ms

bds_s_v2.js

bds_s_v2.js

515 ms

2.gif

2.gif

14902 ms

bdsstyle.css

bdsstyle.css

9704 ms

getnum

getnum

705 ms

3.gif

3.gif

13113 ms

4.gif

4.gif

11690 ms

5.gif

5.gif

11349 ms

6.gif

6.gif

8881 ms

7.gif

7.gif

7796 ms

8.gif

8.gif

6931 ms

9.gif

9.gif

6907 ms

is.png

is.png

2031 ms

sc.png

sc.png

293 ms

10.gif

10.gif

6440 ms

footer_bg.gif

footer_bg.gif

3494 ms

footer_top.gif

footer_top.gif

3272 ms

footer_highlight.png

footer_highlight.png

3847 ms

ico_arrow_blue.gif

ico_arrow_blue.gif

3069 ms

baiduv.png

baiduv.png

11366 ms

baidugw.png

baidugw.png

3891 ms

baiduxy.png

baiduxy.png

9067 ms

weixin.png

weixin.png

8168 ms

kf.gif

kf.gif

4426 ms

bgSexy.png

bgSexy.png

4913 ms

buttons.png

buttons.png

5239 ms

Accessibility Review

rnkey.com accessibility score

52

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

rnkey.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

rnkey.com SEO score

50

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Rnkey.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 Rnkey.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

rnkey.com

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