Tools & Wizards About Us
pos-ne.com screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

pos-ne.com

kb体育·(中国)有限公司官网

Page Load Speed

25.4 sec in total

First Response

963 ms

Resources Loaded

23.5 sec

Page Rendered

914 ms

pos-ne.com screenshot

About Website

Click here to check amazing Pos Ne content. Otherwise, check out these important facts you probably never knew about pos-ne.com

kb体育·(中国)有限公司官网有限公司的前身是中国人民解放军铁道兵，现为国务院国有资产监督管理委员会管理的特大型建筑企业，2007年11月5日在北京独家发起设立中国铁建股份有限公司（中文简称中国铁建，英文简称CRCC），2008年3月10日、13日分别在上海和香港上市（A股代码601186、H股代码1186），公司注册资本135.8亿元。自主研发的新一代汽车高强钢、取向电工钢、高等级家电用钢、能源...

Visit pos-ne.com

Key Findings

We analyzed Pos-ne.com page load time and found that the first response time was 963 ms and then it took 24.4 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.

Performance Metrics

pos-ne.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

1/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value25.3 s

0/100

10%

TBT (Total Blocking Time)

Value4,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.622

10/100

15%

TTI (Time to Interactive)

Value40.9 s

0/100

10%

Network Requests Diagram

pos-ne.com

963 ms

www.pos-ne.com

1097 ms

ky1.js

1157 ms

show.js

2491 ms

main_v4.621621451930097f33ce.bundle.css

360 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Pos-ne.com, 45% (30 requests) were made to User-assets.sxlcdn.com and 21% (14 requests) were made to Ptfafajs.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Ptfafajs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 931.1 kB (8%)

Content Size

11.6 MB

After Optimization

10.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pos-ne.com main page is 11.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 103.6 kB

  • Original 126.5 kB
  • After minification 126.1 kB
  • After compression 23.0 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 103.6 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 827.1 kB

  • Original 11.4 MB
  • After minification 10.6 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. Pos Ne images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 404 B

  • Original 6.0 kB
  • After minification 6.0 kB
  • After compression 5.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-14%

Potential reduce by 107 B

  • Original 755 B
  • After minification 755 B
  • After compression 648 B

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. Pos-ne.com needs all CSS files to be minified and compressed as it can save up to 107 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (23%)

Requests Now

44

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pos Ne. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pos-ne.com

pos-ne.com

963 ms

www.pos-ne.com

www.pos-ne.com

1097 ms

ky1.js

ky1.js

1157 ms

show.js

show.js

2491 ms

main_v4.621621451930097f33ce.bundle.css

main_v4.621621451930097f33ce.bundle.css

360 ms

detectIE-c385c24313ef0e9e4e7a1e131bf5e59f0fbd468f9f9ef44fd6739ae84ef0c0a4.js

detectIE-c385c24313ef0e9e4e7a1e131bf5e59f0fbd468f9f9ef44fd6739ae84ef0c0a4.js

355 ms

jquery.min.js

jquery.min.js

723 ms

i18n-2ace11ac644d0b40fb8b7cb65e9dd1e553022750e0254118dacbe1fe50735e97.js

i18n-2ace11ac644d0b40fb8b7cb65e9dd1e553022750e0254118dacbe1fe50735e97.js

144 ms

page-site-bundle.3ec07665adfc0f2ac46c.js

page-site-bundle.3ec07665adfc0f2ac46c.js

152 ms

ky1.js

ky1.js

217 ms

ky1.html

ky1.html

219 ms

Fiwd_mwxIXsK_-K96uIx8_za8pC7.png

Fiwd_mwxIXsK_-K96uIx8_za8pC7.png

396 ms

gongan-beian.png

gongan-beian.png

835 ms

FnznvTyx2lmMA3hzErYgzyKQQ8LI.png

FnznvTyx2lmMA3hzErYgzyKQQ8LI.png

371 ms

FgEmbE46j8WekuKXSizTHer1csFa.png

FgEmbE46j8WekuKXSizTHer1csFa.png

379 ms

Fiv5U0o0b5SJPUhiB4WS1MvWhglA.png

Fiv5U0o0b5SJPUhiB4WS1MvWhglA.png

388 ms

lg7jW5zLx_FQ9TxbNKTM1Y--jtEM.png

lg7jW5zLx_FQ9TxbNKTM1Y--jtEM.png

391 ms

FkcXGSPhBOda9XyC50SVaclKcfbn.png

FkcXGSPhBOda9XyC50SVaclKcfbn.png

391 ms

FrQSp4mpSWHJToPgkCzKkuNG1A-x.png

FrQSp4mpSWHJToPgkCzKkuNG1A-x.png

398 ms

FjXREKAR-CAAM-Nik-SGMBaxPUyH.png

FjXREKAR-CAAM-Nik-SGMBaxPUyH.png

392 ms

FhsTJmoQAvZNmKvX9_P-jKeregpY.png

FhsTJmoQAvZNmKvX9_P-jKeregpY.png

386 ms

FsGoDL0W1MMa7CwABDc7i_iyTiTW.png

FsGoDL0W1MMa7CwABDc7i_iyTiTW.png

395 ms

FrGvQrRtgZl5o7FIytlNuA-heQ5l.png

FrGvQrRtgZl5o7FIytlNuA-heQ5l.png

399 ms

FsO218HUklfU_n8M1O8tviptnNjE.png

FsO218HUklfU_n8M1O8tviptnNjE.png

412 ms

lqxH2xoEYO1Fp0GzB_98yJKcyzA1.png

lqxH2xoEYO1Fp0GzB_98yJKcyzA1.png

404 ms

FqL7kGRlaFwzC95iugZ6zS6INJqA.png

FqL7kGRlaFwzC95iugZ6zS6INJqA.png

403 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

886 ms

style.css

style.css

216 ms

link.js

link.js

432 ms

ky-section.png

ky-section.png

884 ms

ld-section.png

ld-section.png

1174 ms

jiuyou-section.png

jiuyou-section.png

1093 ms

hth-section.png

hth-section.png

1175 ms

anbo-section.png

anbo-section.png

2024 ms

dafa-section.png

dafa-section.png

1393 ms

kyhd.png

kyhd.png

12024 ms

activity.png

activity.png

20039 ms

FnznvTyx2lmMA3hzErYgzyKQQ8LI.png

FnznvTyx2lmMA3hzErYgzyKQQ8LI.png

31 ms

FgEmbE46j8WekuKXSizTHer1csFa.png

FgEmbE46j8WekuKXSizTHer1csFa.png

35 ms

FhsTJmoQAvZNmKvX9_P-jKeregpY.png

FhsTJmoQAvZNmKvX9_P-jKeregpY.png

40 ms

Fiv5U0o0b5SJPUhiB4WS1MvWhglA.png

Fiv5U0o0b5SJPUhiB4WS1MvWhglA.png

33 ms

lg7jW5zLx_FQ9TxbNKTM1Y--jtEM.png

lg7jW5zLx_FQ9TxbNKTM1Y--jtEM.png

37 ms

FkcXGSPhBOda9XyC50SVaclKcfbn.png

FkcXGSPhBOda9XyC50SVaclKcfbn.png

30 ms

FjXREKAR-CAAM-Nik-SGMBaxPUyH.png

FjXREKAR-CAAM-Nik-SGMBaxPUyH.png

36 ms

FmUdK0pzQwC2bsL6WA1affHFCJFp.png

FmUdK0pzQwC2bsL6WA1affHFCJFp.png

59 ms

FsGoDL0W1MMa7CwABDc7i_iyTiTW.png

FsGoDL0W1MMa7CwABDc7i_iyTiTW.png

48 ms

FrQSp4mpSWHJToPgkCzKkuNG1A-x.png

FrQSp4mpSWHJToPgkCzKkuNG1A-x.png

48 ms

FrGvQrRtgZl5o7FIytlNuA-heQ5l.png

FrGvQrRtgZl5o7FIytlNuA-heQ5l.png

48 ms

FqL7kGRlaFwzC95iugZ6zS6INJqA.png

FqL7kGRlaFwzC95iugZ6zS6INJqA.png

40 ms

lqxH2xoEYO1Fp0GzB_98yJKcyzA1.png

lqxH2xoEYO1Fp0GzB_98yJKcyzA1.png

50 ms

FsO218HUklfU_n8M1O8tviptnNjE.png

FsO218HUklfU_n8M1O8tviptnNjE.png

37 ms

bg.jpg

bg.jpg

2235 ms

css

css

1769 ms

paddle_prev_fff.525c063b989d5e545a0953ed272a7ba7.png

paddle_prev_fff.525c063b989d5e545a0953ed272a7ba7.png

818 ms

FjsgEOMhoik54KL65cGDD6_x4v6l.png

FjsgEOMhoik54KL65cGDD6_x4v6l.png

78 ms

paddle_next_fff.0e534757807692ac2e5343e66c97ab75.png

paddle_next_fff.0e534757807692ac2e5343e66c97ab75.png

860 ms

nav-prev.9b7656600ce9922302fa591f0be905b7.png

nav-prev.9b7656600ce9922302fa591f0be905b7.png

74 ms

nav-next.dacef369fbedad44046aa690538793ff.png

nav-next.dacef369fbedad44046aa690538793ff.png

75 ms

FjsgEOMhoik54KL65cGDD6_x4v6l.png

FjsgEOMhoik54KL65cGDD6_x4v6l.png

51 ms

OpenSans-Bold-webfont.2e90d5152ce92858b62ba053c7b9d2cb.woff

OpenSans-Bold-webfont.2e90d5152ce92858b62ba053c7b9d2cb.woff

13 ms

OpenSans-Semibold-webfont.697574b47bcfdd2c45e3e63c7380dd67.woff

OpenSans-Semibold-webfont.697574b47bcfdd2c45e3e63c7380dd67.woff

93 ms

OpenSans-Regular-webfont.79515ad0788973c533405f7012dfeccd.woff

OpenSans-Regular-webfont.79515ad0788973c533405f7012dfeccd.woff

93 ms

OpenSans-Light-webfont.45b47f3e9c7d74b80f5c6e0a3c513b23.woff

OpenSans-Light-webfont.45b47f3e9c7d74b80f5c6e0a3c513b23.woff

874 ms

css

css

217 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

1507 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

1497 ms

Accessibility Review

pos-ne.com accessibility score

79

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

High

Image elements do not have [alt] attributes

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

pos-ne.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pos-ne.com SEO score

77

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

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

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pos-ne.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 Pos-ne.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

pos-ne.com

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