Tools & Wizards About Us
oxe.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

oxe.cn

防水蜡_地板防水蜡_木蜡油_玻璃钢脱模蜡|抛光蜡|汽车抛光蜡|汽车抛光蜡价格|抛光蜡配方|抛光蜡价格_抛光蜡生产厂家_抛光蜡厂家_抛光蜡批发_静音防水蜡—苏州布鲁泽新材料有限公司

Page Load Speed

66 sec in total

First Response

5.6 sec

Resources Loaded

58 sec

Page Rendered

2.4 sec

oxe.cn screenshot

About Website

Click here to check amazing Oxe content. Otherwise, check out these important facts you probably never knew about oxe.cn

苏州布鲁泽新材料有限公司源自德国鲁尔区的技术传承，专业致力于防水蜡_地板防水蜡_木蜡油_玻璃钢脱模蜡抛光蜡、汽车抛光蜡、汽车抛光蜡价格、抛光蜡配方、抛光蜡价格、抛光蜡生产厂家、抛光蜡厂家、抛光蜡批发、静音防水蜡致力于特种蜡的衍生应用的研发、生产及销售。苏州布鲁泽新材料有限公司,欢迎来电咨询！

Visit oxe.cn

Key Findings

We analyzed Oxe.cn page load time and found that the first response time was 5.6 sec and then it took 60.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. Unfortunately, there were 24 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

oxe.cn performance score

0

Network Requests Diagram

oxe.cn

5627 ms

css.css

1525 ms

jquery.js

19798 ms

jquery-1.7.2.min.js

5667 ms

17326500.js

743 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Oxe.cn, 58% (47 requests) were made to Lunkuoyi.cn and 22% (18 requests) were made to Walechina.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Qiao.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 334.3 kB (33%)

Content Size

1.0 MB

After Optimization

674.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oxe.cn main page is 1.0 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. 25% of websites need less resources to load. Images take 695.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 105.3 kB

  • Original 119.7 kB
  • After minification 112.2 kB
  • After compression 14.4 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 105.3 kB or 88% of the original size.

Image Optimization

-14%

Potential reduce by 98.5 kB

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

JavaScript Optimization

-65%

Potential reduce by 109.8 kB

  • Original 168.9 kB
  • After minification 168.8 kB
  • After compression 59.1 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 109.8 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 20.8 kB

  • Original 25.4 kB
  • After minification 17.7 kB
  • After compression 4.6 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. Oxe.cn needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (13%)

Requests Now

56

After Optimization

49

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oxe. 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

oxe.cn

oxe.cn

5627 ms

css.css

css.css

1525 ms

jquery.js

jquery.js

19798 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

5667 ms

17326500.js

17326500.js

743 ms

p-bg1.jpg

p-bg1.jpg

349 ms

changcheng.jpg

changcheng.jpg

1993 ms

2015431012380.jpg

2015431012380.jpg

3347 ms

mingzhu.jpg

mingzhu.jpg

2882 ms

xinan.jpg

xinan.jpg

2969 ms

yaxin.jpg

yaxin.jpg

3716 ms

zhonghe.jpg

zhonghe.jpg

3661 ms

zhongnan.jpg

zhongnan.jpg

4565 ms

ql.jpg

ql.jpg

3750 ms

wuhu.jpg

wuhu.jpg

3767 ms

zhonghang.jpg

zhonghang.jpg

3433 ms

dazhong.jpg

dazhong.jpg

3914 ms

yuyao.jpg

yuyao.jpg

5562 ms

tezhou.jpg

tezhou.jpg

4715 ms

fenshi.jpg

fenshi.jpg

4601 ms

danchi.jpg

danchi.jpg

4180 ms

jinrong.jpg

jinrong.jpg

6440 ms

cf.jpg

cf.jpg

4596 ms

ntn.jpg

ntn.jpg

5082 ms

sb.jpg

sb.jpg

5056 ms

top_bg.gif

top_bg.gif

382 ms

top_banner.gif

top_banner.gif

743 ms

1d.jpg

1d.jpg

7185 ms

F_FT.gif

F_FT.gif

758 ms

dian.jpg

dian.jpg

771 ms

SP2000-D.png

SP2000-D.png

19934 ms

jd.jpg

jd.jpg

2419 ms

j1.jpg

j1.jpg

1562 ms

bg_on.png

bg_on.png

1177 ms

j2.jpg

j2.jpg

2444 ms

j3.jpg

j3.jpg

8464 ms

rj.jpg

rj.jpg

2325 ms

r1.jpg

r1.jpg

5703 ms

r2.jpg

r2.jpg

7057 ms

cpys.jpg

cpys.jpg

2885 ms

ys1.jpg

ys1.jpg

4570 ms

ys2.jpg

ys2.jpg

9082 ms

ys3.jpg

ys3.jpg

10480 ms

ys4.jpg

ys4.jpg

19930 ms

ys5.jpg

ys5.jpg

8914 ms

GJ.gif

GJ.gif

19929 ms

FW.JPG

FW.JPG

10203 ms

FW1.gif

FW1.gif

18612 ms

RS2600.PNG

RS2600.PNG

18243 ms

RS1600.PNG

RS1600.PNG

19190 ms

ra16.png

ra16.png

19928 ms

ra160.png

ra160.png

19929 ms

SP3000.JPG

SP3000.JPG

19928 ms

SP1000-D.png

SP1000-D.png

19929 ms

RS395C.JPG

RS395C.JPG

19929 ms

RS390C.JPG

RS390C.JPG

19928 ms

2015112161229.jpg

2015112161229.jpg

19929 ms

2015112161005.jpg

2015112161005.jpg

19929 ms

RS295C.jpg

RS295C.jpg

19929 ms

2015112162007.jpg

2015112162007.jpg

19929 ms

2015112161737.jpg

2015112161737.jpg

19638 ms

h.js

h.js

1864 ms

2015112131543.jpg

2015112131543.jpg

19559 ms

2015112131139.jpg

2015112131139.jpg

20191 ms

2015112130537.jpg

2015112130537.jpg

20176 ms

RC120H.JPG

RC120H.JPG

20164 ms

RC120C.JPG

RC120C.JPG

19757 ms

bx.jpg

bx.jpg

20372 ms

21.gif

21.gif

863 ms

b.js

b.js

2125 ms

hm.gif

hm.gif

838 ms

DXKH.jpg

DXKH.jpg

19608 ms

p-bg2.jpg

p-bg2.jpg

19516 ms

bsl.js

bsl.js

1929 ms

Enter.php

Enter.php

1206 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

7167 ms

main.css

main.css

672 ms

fix.css

fix.css

946 ms

version.js

version.js

952 ms

01.jpg

01.jpg

20490 ms

button_11.gif

button_11.gif

458 ms

SEO Factors

oxe.cn SEO score

0

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 Oxe.cn 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 Oxe.cn 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

oxe.cn

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