33.6 sec in total
1.3 sec
31.5 sec
853 ms
Visit 2ptt.com now to see the best up-to-date 2 Ptt content and also check out these interesting facts you probably never knew about 2ptt.com
Visit 2ptt.comWe analyzed 2ptt.com page load time and found that the first response time was 1.3 sec and then it took 32.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
2ptt.com performance score
1285 ms
535 ms
811 ms
681 ms
1603 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original 2ptt.com, 22% (16 requests) were made to E.e701.net and 15% (11 requests) were made to Imgsrc.baidu.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source E.e701.net.
Page size can be reduced by 273.9 kB (49%)
556.7 kB
282.9 kB
In fact, the total size of 2ptt.com main page is 556.7 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. 30% of websites need less resources to load. Images take 277.6 kB which makes up the majority of the site volume.
Potential reduce by 46.9 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 9.6 kB, which is 17% 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 46.9 kB or 81% of the original size.
Potential reduce by 44.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, 2 Ptt needs image optimization as it can save up to 44.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 18.6 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 18.6 kB or 63% of the original size.
Potential reduce by 163.7 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. 2ptt.com needs all CSS files to be minified and compressed as it can save up to 163.7 kB or 85% of the original size.
Number of requests can be reduced by 14 (30%)
46
32
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Ptt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.2ptt.com
1285 ms
g_73.css
535 ms
index_24.css
811 ms
m.js
681 ms
z_stat.php
1603 ms
logo.png
634 ms
blank
92 ms
a9773912b31bb051ac6031cc367adab44bede08a.jpg
3570 ms
6a600c338744ebf893bc919adbf9d72a6159a742.jpg
7199 ms
8326cffc1e178a828c728108f403738da877e8c8.jpg
4178 ms
item-009C9C8C-D0D1364400000000040100001A409EA2.0.300x300.jpg
2219 ms
wapc-20110217233523-39368384.jpg
1324 ms
073637662.jpg
1265 ms
3c28af542f2d49f7-a4f58d55e25876cc-db6b81ec8e75692babb2967d81c606c4.jpg
150 ms
444c4e2f745162f8-80b3c3b4a16ce4ad-dbda4c472d45a02e37c18df2a335df51.jpg
1504 ms
314e251f95cad1c885715c6e7d3e6709c83d51b4.jpg
5696 ms
c8177f3e6709c93db773c8949b3df8dcd00054d4.jpg
3443 ms
045708285.jpg
1264 ms
08f790529822720e890e61467fcb0a46f31fab4e.jpg
19663 ms
item-003DBFF4-38AD6362000000000401000014F037D8.0.300x300.jpg
2419 ms
0eb30f2442a7d933bea8a297ad4bd11372f001d5.jpg
3548 ms
5ab5c9ea15ce36d33374c5d43af33a87e850b1e6.jpg
5259 ms
b48f8c5494eef01fe56a9a21e0fe9925bd317ddc.jpg
10116 ms
267f9e2f07082838b9679af0b899a9014d08f1e8.jpg
3591 ms
838ba61ea8d3fd1f015ce4de304e251f94ca5ff8.jpg
3188 ms
c2fdfc039245d6888f8cf440a4c27d1ed31b2443.jpg
5027 ms
14ce36d3d539b600d2a44953e950352ac75cb7e8.jpg
19653 ms
96dda144ad34598249e0a3760cf431adcaef84e8.jpg
6086 ms
a8773912b31bb0516f24f5cc367adab44bede0d6.jpg
5925 ms
2cf5e0fe9925bc317ba9477c5edf8db1ca137059.jpg
19653 ms
838ba61ea8d3fd1f507036e9314e251f94ca5fe3.jpg
11921 ms
20090405162405-1250791150.jpg
1554 ms
wapc-20110915203814-775423796.jpg
10663 ms
8d0f68c6acdc3885-19c639c9b99f07e9-31202282b6fdf9ddf30caee2cba948ba.jpg
1482 ms
444c4e2f745162f8-80b3c3b4a16ce4ad-4fd717238ad2c5f8b2ae0cef2d79e104.jpg
1479 ms
8d0f68c6acdc3885-19c639c9b99f07e9-620825c18856f6bad0b680cf5209928d.jpg
1480 ms
ttop.png
269 ms
index.php
2148 ms
index.php
2472 ms
pf.php
7732 ms
show.js
6153 ms
referer_error.png
4149 ms
dl.gif
1565 ms
dl.gif
1564 ms
show_2.php
2577 ms
show_0.php
4745 ms
show_lb.php
2308 ms
DiySize.php
3382 ms
blank
24 ms
073637662.jpg
84 ms
444c4e2f745162f8-80b3c3b4a16ce4ad-dbda4c472d45a02e37c18df2a335df51.jpg
134 ms
045708285.jpg
66 ms
8d0f68c6acdc3885-19c639c9b99f07e9-31202282b6fdf9ddf30caee2cba948ba.jpg
131 ms
444c4e2f745162f8-80b3c3b4a16ce4ad-4fd717238ad2c5f8b2ae0cef2d79e104.jpg
145 ms
8d0f68c6acdc3885-19c639c9b99f07e9-620825c18856f6bad0b680cf5209928d.jpg
147 ms
stat.htm
894 ms
core.php
4190 ms
global.css
1035 ms
960130.css
1373 ms
jquery1.9.0.js
19900 ms
common.js
13000 ms
referer_error.png
776 ms
global.css
1869 ms
960130.css
1992 ms
css.css
2102 ms
global.css
2247 ms
jquery.animate-colors-min.js
3455 ms
css.css
1352 ms
lb.js
1552 ms
dl.gif
268 ms
9.gif
4087 ms
app.gif
10035 ms
2ptt.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2ptt.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 2ptt.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.
2ptt.com
Open Graph description is not detected on the main page of 2 Ptt. 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: