6 sec in total
1.2 sec
4.5 sec
294 ms
Click here to check amazing Lax V2EX content for China. Otherwise, check out these important facts you probably never knew about lax.v2ex.com
Visit lax.v2ex.comWe analyzed Lax.v2ex.com page load time and found that the first response time was 1.2 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lax.v2ex.com performance score
1210 ms
1074 ms
858 ms
308 ms
177 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 25% of them (19 requests) were addressed to the original Lax.v2ex.com, 68% (52 requests) were made to Cdn.v2ex.co and 4% (3 requests) were made to Cdn.v2ex.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cdn.v2ex.com.
Page size can be reduced by 545.4 kB (57%)
962.2 kB
416.8 kB
In fact, the total size of Lax.v2ex.com main page is 962.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. 40% of websites need less resources to load. Javascripts take 582.1 kB which makes up the majority of the site volume.
Potential reduce by 70.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 11.3 kB, which is 14% 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 70.4 kB or 85% of the original size.
Potential reduce by 8.6 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. Lax V2EX images are well optimized though.
Potential reduce by 397.9 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 397.9 kB or 68% of the original size.
Potential reduce by 68.5 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. Lax.v2ex.com needs all CSS files to be minified and compressed as it can save up to 68.5 kB or 84% of the original size.
Number of requests can be reduced by 30 (40%)
75
45
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lax V2EX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lax.v2ex.com
1210 ms
basic.css
1074 ms
style.css
858 ms
desktop.css
308 ms
tomorrow.css
177 ms
highlight.pack.js
296 ms
font-awesome.min.css
6 ms
jquery.js
1671 ms
jquery-ui.js
1891 ms
jquery.autosize.js
1490 ms
jquery.textcomplete.css
6 ms
v2ex.js
5 ms
select2.css
6 ms
select2.min.js
963 ms
selectboxit.css
8 ms
selectboxit.min.js
8 ms
jquery.textcomplete.min.js
8 ms
logo@2x.png
134 ms
qbar_light@2x.png
50 ms
100offer_20150925_big-fs8.png
98 ms
37038_normal.png
132 ms
58407_normal.png
181 ms
58816_normal.png
184 ms
70644_normal.png
183 ms
37540_normal.png
182 ms
116132_normal.png
184 ms
49763_normal.png
202 ms
38453_normal.png
239 ms
116882_normal.png
243 ms
149668_normal.png
245 ms
fef95fe420ff76d7881216a5858e9d67
393 ms
76873_normal.png
245 ms
66443_normal.png
281 ms
b4f0d52f0f70c02a9d4d6744e4425efe
476 ms
113030_normal.png
322 ms
112888_normal.png
324 ms
10287a1e66ea8abcc189c5bde56b1c80
519 ms
129982_normal.png
361 ms
4867_normal.png
401 ms
103636_normal.png
402 ms
47978_normal.png
441 ms
113080_normal.png
470 ms
83254_normal.png
481 ms
6b9264d33380de7718fb008d79f66787
638 ms
4f68a7dc3ce11c833f84f797e9635210
720 ms
163545_normal.png
550 ms
119683_normal.png
552 ms
125532_normal.png
561 ms
83491_normal.png
595 ms
114196_normal.png
629 ms
5781_normal.png
632 ms
36819_normal.png
640 ms
78007_normal.png
674 ms
eac18a2f4fa00286b293801f826ce521
866 ms
shadow_light.png
83 ms
bg_blended_light.png
84 ms
rss.png
84 ms
do.png
84 ms
lang_zhcn_32.png
84 ms
21225_normal.png
624 ms
fontawesome-webfont.woff
23 ms
34db9802c937285bb6ea0bf30e8cac83
776 ms
analytics.js
6 ms
prum.min.js
18 ms
collect
15 ms
53c3d09071b4239ae2ba98637086ce65
797 ms
686f3b4887fb523bb364c287a7456ca0
950 ms
a3ea89a680bd289270b248e39506d747
1012 ms
63aa1415f8d30c64f04000cc77f0153c
920 ms
123610_normal.png
769 ms
542da60bdb8dc58c9c25d76c70e006b3
922 ms
145627_normal.png
804 ms
38523_normal.png
792 ms
18346_normal.png
844 ms
52784_normal.png
867 ms
8509ed5054cef8bc3fafd7dd6e9a8947
1108 ms
a5657dcc3ada481de3a72d7b0bf2d578
1051 ms
lax.v2ex.com SEO score
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lax.v2ex.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Lax.v2ex.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.
lax.v2ex.com
Open Graph description is not detected on the main page of Lax V2EX. 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: