6.1 sec in total
761 ms
4.3 sec
1 sec
Visit potchinese.com now to see the best up-to-date Potchinese content and also check out these interesting facts you probably never knew about potchinese.com
Visit potchinese.comWe analyzed Potchinese.com page load time and found that the first response time was 761 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
potchinese.com performance score
761 ms
127 ms
130 ms
140 ms
142 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 26% of them (19 requests) were addressed to the original Potchinese.com, 6% (4 requests) were made to Taiwtp1.com and 6% (4 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Sjpic4.sdvuc.com.
Page size can be reduced by 182.7 kB (66%)
275.2 kB
92.5 kB
In fact, the total size of Potchinese.com main page is 275.2 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. 45% of websites need less resources to load. HTML takes 104.8 kB which makes up the majority of the site volume.
Potential reduce by 93.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. This page needs HTML code to be minified as it can gain 46.8 kB, which is 45% 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 93.4 kB or 89% of the original size.
Potential reduce by 1.9 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. Potchinese images are well optimized though.
Potential reduce by 5.8 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 5.8 kB or 14% of the original size.
Potential reduce by 81.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. Potchinese.com needs all CSS files to be minified and compressed as it can save up to 81.6 kB or 79% of the original size.
Number of requests can be reduced by 17 (31%)
55
38
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potchinese. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
potchinese.com
761 ms
stui_default.css
127 ms
zui.css
130 ms
ribiav.php
140 ms
DL.js
142 ms
DP2.js
153 ms
cookie.js
135 ms
kakaxiaikakaxi.php
151 ms
20190928.js
1052 ms
jQuery.js
198 ms
style.css
186 ms
co.js
135 ms
hm.js
1511 ms
jquery.lazyload.min.js
138 ms
language.js
139 ms
bg_icon.jpg
66 ms
logo.gif
314 ms
icon_seacrh.png
122 ms
ribiav.html
133 ms
8babb2d6ae744d9a955c1af413edc0b7.gif
1000 ms
O1CN01tjzAup2Imjb8FL1oh_!!133635909329.jpg
343 ms
618943ad0992480faecb963d7e614e65.gif
1466 ms
dc13a1883d9c4733a52c8b8c8ffab7db.gif
1331 ms
B406E9DE-0B2B-5648-33-E643D1876FE1.blpha
805 ms
ate.css
75 ms
zui.css
134 ms
e0b4ad53309b4c0980b2ceb461415106.gif
1598 ms
sdfghgfdsasdfghjkjhgfdsasdfghjklkjh.gif
1086 ms
e27e16f06bd973f89ff8eb016904fb5c.gif
602 ms
b5e6a8ddb5974273b8afbd7c2ac2ac52.gif
1470 ms
df0515659c031251093942922779f350.gif
547 ms
0106c120009zhkgar5827.gif
106 ms
3154a49b5a6e403c83b0bb5370d2a08c.gif
681 ms
4d9cdc0aca84405a8f5677662b44c5f2.gif
1301 ms
94747760f9a86fa539e3ba23345db0a4.gif
208 ms
dc0247b33019ed0ca09c321bb6fb4656.gif
577 ms
5e6be8ccb1a44f20876d70c0a1264649.gif
1468 ms
d0e972505dec4c1cb1fa32986988764b.gif
948 ms
960160.gif
687 ms
500-500.gif
783 ms
x7rjyj.gif
1481 ms
7cff7f9497f46e78d22b810e62c790e2.gif
2209 ms
fa2a2c1b0061034a191bc829cd166d6e
1164 ms
ptv300.gif
1585 ms
45kcge.gif
1221 ms
290299ed48d84c7b99d8fbd8a96a254c
1002 ms
zlzp5w.gif
780 ms
2ef8f38182c5058d1904e6ab845a827a.gif
542 ms
0101w120009v3adjs2A70.gif
166 ms
0105w12000a0is2hcC9E1.gif
154 ms
200200.gif
685 ms
load.jpg
87 ms
play.png
73 ms
0
1792 ms
01A6m22348i6ptf5c037E.gif
408 ms
e27e16f06bd973f89ff8eb016904fb5c.gif
315 ms
df0515659c031251093942922779f350.gif
318 ms
3154a49b5a6e403c83b0bb5370d2a08c.gif
255 ms
94747760f9a86fa539e3ba23345db0a4.gif
79 ms
dc0247b33019ed0ca09c321bb6fb4656.gif
332 ms
960160.gif
651 ms
hm.js
1002 ms
2ef8f38182c5058d1904e6ab845a827a.gif
270 ms
200200.gif
612 ms
sv
72 ms
pv.php
296 ms
element.js
67 ms
push.js
470 ms
11.0.1.js
1032 ms
hm.gif
536 ms
hm.gif
324 ms
ab77b6ea7f3fbf79.js
259 ms
potchinese.com SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potchinese.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Potchinese.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.
potchinese.com
Open Graph description is not detected on the main page of Potchinese. 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: