Tools & Wizards About Us
engkoo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

engkoo.com

微软小英

Page Load Speed

12.7 sec in total

First Response

2.6 sec

Resources Loaded

9.9 sec

Page Rendered

185 ms

engkoo.com screenshot

About Website

Click here to check amazing Engkoo content for China. Otherwise, check out these important facts you probably never knew about engkoo.com

微软小英是微软亚洲研究院开发的免费的英语学习公众号，包括英语口语和词汇的专项训练，以及中英翻译等多种功能，目前为Beta版本。希望小英能成为你的良师益友，陪你一起把英语学得棒棒哒！

Visit engkoo.com

Key Findings

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

Performance Metrics

engkoo.com performance score

0

Network Requests Diagram

engkoo.com

2585 ms

pinyin.engkoo.com

3974 ms

WebsiteMaster.css

698 ms

Homepage.css

698 ms

banner_1.png

1038 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Engkoo.com, 67% (16 requests) were made to Pinyin.engkoo.com and 21% (5 requests) were made to V3.jiathis.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Pinyin.engkoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.6 kB (45%)

Content Size

314.5 kB

After Optimization

174.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Engkoo.com main page is 314.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. Images take 135.8 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 4.8 kB

  • Original 7.8 kB
  • After minification 7.7 kB
  • After compression 3.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 4.8 kB or 61% of the original size.

Image Optimization

-14%

Potential reduce by 18.8 kB

  • Original 135.8 kB
  • After minification 117.0 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, Engkoo needs image optimization as it can save up to 18.8 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

-60%

Potential reduce by 72.0 kB

  • Original 119.5 kB
  • After minification 119.0 kB
  • After compression 47.4 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 72.0 kB or 60% of the original size.

CSS Optimization

-87%

Potential reduce by 44.9 kB

  • Original 51.5 kB
  • After minification 48.2 kB
  • After compression 6.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. Engkoo.com needs all CSS files to be minified and compressed as it can save up to 44.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (18%)

Requests Now

22

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

engkoo.com

engkoo.com

2585 ms

pinyin.engkoo.com

pinyin.engkoo.com

3974 ms

WebsiteMaster.css

WebsiteMaster.css

698 ms

Homepage.css

Homepage.css

698 ms

banner_1.png

banner_1.png

1038 ms

tile_engine.png

tile_engine.png

730 ms

tile_vmode.png

tile_vmode.png

818 ms

tile_fastfluid.png

tile_fastfluid.png

1042 ms

tile_engmode.png

tile_engmode.png

1040 ms

ftr.png

ftr.png

1409 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

520 ms

MasterPage.js

MasterPage.js

887 ms

jia.js

jia.js

496 ms

o_code.keep.js

o_code.keep.js

1039 ms

msra_logo_122x49.png

msra_logo_122x49.png

1056 ms

bg_repeater.png

bg_repeater.png

709 ms

jiathis_utility.html

jiathis_utility.html

10 ms

jiathis_share.css

jiathis_share.css

16 ms

plugin.client.js

plugin.client.js

20 ms

jiathis_ico.png

jiathis_ico.png

21 ms

banner_2.png

banner_2.png

1389 ms

banner_3.png

banner_3.png

1045 ms

banner_4.png

banner_4.png

1293 ms

cnt;C1;619;.;2hQf+o0iYRGiJqfUXRjnwt0twhU=;

cnt;C1;619;.;2hQf+o0iYRGiJqfUXRjnwt0twhU=;

402 ms

SEO Factors

engkoo.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

engkoo.com

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