Tools & Wizards About Us
yinglizhe.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yinglizhe.com

東莞壓鑄模具制造廠|東莞鋁合金模具制造廠|東莞鋅合金壓鑄廠-奧德

Page Load Speed

3.4 sec in total

First Response

640 ms

Resources Loaded

2.6 sec

Page Rendered

148 ms

yinglizhe.com screenshot

About Website

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

東莞市長安奧德五金制品廠專業以鋅鋁合金電鍍,廣東壓鑄氧化,鋅鋁合金表面處理為生産線.想找東莞模具制造,東莞壓鑄模具制造廠,東莞鋅合金模具制造廠請緻電:0769-87094968

Visit yinglizhe.com

Key Findings

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

Performance Metrics

yinglizhe.com performance score

0

Network Requests Diagram

forum.php

640 ms

style_1_common.css

339 ms

style_1_forum_index.css

329 ms

common.js

525 ms

forum.js

355 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 96% of them (26 requests) were addressed to the original Yinglizhe.com, 4% (1 request) were made to Discuz.gtimg.cn. The less responsive or slowest element that took the longest time to load (640 ms) belongs to the original domain Yinglizhe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.1 kB (66%)

Content Size

23.1 kB

After Optimization

7.9 kB

  • HTML
  • JavaScript

In fact, the total size of Yinglizhe.com main page is 23.1 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. HTML takes 16.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 12.2 kB

  • Original 16.9 kB
  • After minification 16.8 kB
  • After compression 4.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. 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 12.2 kB or 72% of the original size.

JavaScript Optimization

-48%

Potential reduce by 2.9 kB

  • Original 6.2 kB
  • After minification 6.0 kB
  • After compression 3.2 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 2.9 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (54%)

Requests Now

26

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forum.php

forum.php

640 ms

style_1_common.css

style_1_common.css

339 ms

style_1_forum_index.css

style_1_forum_index.css

329 ms

common.js

common.js

525 ms

forum.js

forum.js

355 ms

logging.js

logging.js

355 ms

discuz_tips.js

discuz_tips.js

462 ms

background.png

background.png

175 ms

switch_width.png

switch_width.png

180 ms

logo.png

logo.png

174 ms

collapsed_no.gif

collapsed_no.gif

187 ms

forum.gif

forum.gif

187 ms

online_admin.gif

online_admin.gif

177 ms

online_supermod.gif

online_supermod.gif

338 ms

online_moderator.gif

online_moderator.gif

337 ms

online_member.gif

online_member.gif

349 ms

px.png

px.png

343 ms

newarow.gif

newarow.gif

345 ms

pn.png

pn.png

354 ms

nv.png

nv.png

483 ms

qmenu.png

qmenu.png

485 ms

nv_a.png

nv_a.png

511 ms

search.png

search.png

516 ms

pt_item.png

pt_item.png

499 ms

chart.png

chart.png

515 ms

titlebg.png

titlebg.png

627 ms

scrolltop.png

scrolltop.png

623 ms

SEO Factors

yinglizhe.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yinglizhe.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Yinglizhe.com main page’s claimed encoding is gbk. 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

yinglizhe.com

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