Tools & Wizards About Us
201.pigai.org screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

201.pigai.org

批改网—秒批作文，两千万人使用的在线英文写作平台

Page Load Speed

10.1 sec in total

First Response

2.1 sec

Resources Loaded

7.9 sec

Page Rendered

106 ms

201.pigai.org screenshot

About Website

Welcome to 201.pigai.org homepage info - get ready to check 201 Pigai best content for China right away, or after learning these important things about 201.pigai.org

批改网基于语料库和云计算技术提供英语作文自动在线批改服务；能及时给出作文的分数、评语以及按句点评，能够提高老师批改英语作文的工作效率，提高学生的英语写作能力。目前已经超过5000所学校在使用我们的服务！

Visit 201.pigai.org

Key Findings

We analyzed 201.pigai.org page load time and found that the first response time was 2.1 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

201.pigai.org performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

Network Requests Diagram

201.pigai.org

2087 ms

jquery-min.js

1723 ms

login_2013.css

1031 ms

2020.js

1070 ms

jsencrypt.min.js

1543 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 201.pigai.org, 99% (88 requests) were made to Cdn3.pigai.org. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cdn3.pigai.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.8 kB (12%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 201.pigai.org main page is 1.7 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 29.5 kB

  • Original 35.7 kB
  • After minification 31.4 kB
  • After compression 6.2 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 4.3 kB, which is 12% 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 29.5 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 72.6 kB

  • Original 1.5 MB
  • After minification 1.4 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. 201 Pigai images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 103.9 kB

  • Original 155.6 kB
  • After minification 154.7 kB
  • After compression 51.7 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.9 kB or 67% of the original size.

CSS Optimization

-73%

Potential reduce by 4.9 kB

  • Original 6.7 kB
  • After minification 6.0 kB
  • After compression 1.8 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. 201.pigai.org needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

88

After Optimization

88

  • Images
  • JavaScript
  • CSS

The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 201 Pigai. According to our analytics all requests are already optimized.

Network Requests Diagram

201.pigai.org

201.pigai.org

2087 ms

jquery-min.js

jquery-min.js

1723 ms

login_2013.css

login_2013.css

1031 ms

2020.js

2020.js

1070 ms

jsencrypt.min.js

jsencrypt.min.js

1543 ms

logo_2018.png

logo_2018.png

255 ms

banner_1.jpg

banner_1.jpg

818 ms

gb1.png

gb1.png

237 ms

kuaishu.png

kuaishu.png

252 ms

li_1.png

li_1.png

462 ms

banner_2.jpg

banner_2.jpg

1439 ms

bwtt_2024.jpg

bwtt_2024.jpg

1108 ms

bg2.png

bg2.png

484 ms

login_bt.png

login_bt.png

486 ms

oauth.png

oauth.png

698 ms

wx.png

wx.png

716 ms

dd.png

dd.png

742 ms

student.png

student.png

932 ms

teacher.png

teacher.png

958 ms

bisai_bg.png

bisai_bg.png

974 ms

l_daxing1z.jpg

l_daxing1z.jpg

1083 ms

l_chenjinglun.jpg

l_chenjinglun.jpg

1227 ms

l_gongdafuz.jpg

l_gongdafuz.jpg

1219 ms

s_tsinghua.jpg

s_tsinghua.jpg

1282 ms

s_nju.jpg

s_nju.jpg

1335 ms

s_fudan.jpg

s_fudan.jpg

1348 ms

s_sccd7.jpg

s_sccd7.jpg

1471 ms

s_rdfz.png

s_rdfz.png

1489 ms

s_scss.jpg

s_scss.jpg

1588 ms

l_chengdusywgy.jpg

l_chengdusywgy.jpg

1605 ms

s_nwpu.jpg

s_nwpu.jpg

1591 ms

s_sjtu.jpg

s_sjtu.jpg

1690 ms

s_xjtu.jpg

s_xjtu.jpg

1723 ms

l_shanxikangjie.jpg

l_shanxikangjie.jpg

1788 ms

l_linfenyizhong.jpg

l_linfenyizhong.jpg

1911 ms

l_chengduwgy.jpg

l_chengduwgy.jpg

1836 ms

s_yzu.jpg

s_yzu.jpg

1867 ms

s_scau.jpg

s_scau.jpg

1947 ms

s_ntu.jpg

s_ntu.jpg

1979 ms

l_gzshiqizhong.jpg

l_gzshiqizhong.jpg

2105 ms

l_gzxiguanwgy.jpg

l_gzxiguanwgy.jpg

2037 ms

l_gzshisanzhong.jpg

l_gzshisanzhong.jpg

1899 ms

s_niit.jpg

s_niit.jpg

1965 ms

s_sdu.jpg

s_sdu.jpg

1937 ms

s_ahu.jpg

s_ahu.jpg

1751 ms

l_huchengzx.jpg

l_huchengzx.jpg

1880 ms

l_balizhuangds.jpg

l_balizhuangds.jpg

1943 ms

l_caochangdi.jpg

l_caochangdi.jpg

1704 ms

s_sysu.jpg

s_sysu.jpg

1712 ms

s_xidian.jpg

s_xidian.jpg

1703 ms

s_cnu.jpg

s_cnu.jpg

1641 ms

l_chaoyjyfs.jpg

l_chaoyjyfs.jpg

1678 ms

bjcysby.png

bjcysby.png

1721 ms

l_chaoywgy.jpg

l_chaoywgy.jpg

1718 ms

s_hlju.gif

s_hlju.gif

1593 ms

s_hainnu.gif

s_hainnu.gif

1570 ms

s_bjtu.jpg

s_bjtu.jpg

1483 ms

l_bashizsywyh.jpg

l_bashizsywyh.jpg

1628 ms

l_jiushiqiz.jpg

l_jiushiqiz.jpg

1710 ms

l_qishiyiz.jpg

l_qishiyiz.jpg

1601 ms

s_fmmu.jpg

s_fmmu.jpg

1563 ms

whu.gif

whu.gif

1495 ms

gxnu.gif

gxnu.gif

1473 ms

l_shiliuzhong.jpg

l_shiliuzhong.jpg

1613 ms

l_shiqizhong.jpg

l_shiqizhong.jpg

1583 ms

l_gaojiayuanz.jpg

l_gaojiayuanz.jpg

1602 ms

s_cqu.jpg

s_cqu.jpg

1563 ms

s_sut.jpg

s_sut.jpg

1573 ms

s_lnpu.jpg

s_lnpu.jpg

1577 ms

l_heizhuanghuz.jpg

l_heizhuanghuz.jpg

2022 ms

l_jinzhanxiao.jpg

l_jinzhanxiao.jpg

1587 ms

l_jinsongyiz.jpg

l_jinsongyiz.jpg

1561 ms

s_nedu.jpg

s_nedu.jpg

1537 ms

l_jiushisiz.jpg

l_jiushisiz.jpg

1646 ms

l_louzizhuang.jpg

l_louzizhuang.jpg

1640 ms

l_minzu.jpg

l_minzu.jpg

1600 ms

l_shibalidianz.jpg

l_shibalidianz.jpg

1586 ms

l_xinjiaoyu.jpg

l_xinjiaoyu.jpg

1577 ms

l_yinghuayuan.jpg

l_yinghuayuan.jpg

1742 ms

l_zhongyangsw.jpg

l_zhongyangsw.jpg

1744 ms

l_dougezhuang.jpg

l_dougezhuang.jpg

1717 ms

l_sanfanchaoy.jpg

l_sanfanchaoy.jpg

1595 ms

l_zhongkeyuanfs.jpg

l_zhongkeyuanfs.jpg

1579 ms

l_lingnanhp.jpg

l_lingnanhp.jpg

1629 ms

l_gzdiyizx.jpg

l_gzdiyizx.jpg

1809 ms

l_meishanwgy.jpg

l_meishanwgy.jpg

1749 ms

l_scjianyang.jpg

l_scjianyang.jpg

1803 ms

qq-online.png

qq-online.png

1585 ms

weixin.jpg

weixin.jpg

1580 ms

Accessibility Review

201.pigai.org accessibility score

75

Accessibility Issues

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

201.pigai.org best practices score

67

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

201.pigai.org SEO score

62

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

Image elements do not have [alt] attributes

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 201.pigai.org 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 201.pigai.org 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

201.pigai.org

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