23.1 sec in total
310 ms
21.9 sec
934 ms
Click here to check amazing Zuo content. Otherwise, check out these important facts you probably never knew about zuo.la
佐拉(Zola),真名周曙光,男,漢族,民國七十年生,原籍湖南,現居中華民國台灣省花蓮縣瑞穗鄉,網絡工程師,摄影师,獨立寫作者,無黨派人士,行為藝術家,異議人士,以客串公民記者聞名。2008年德國之聲國際博客大賽中文評委。2009年擔任荷蘭國際電台新聞比賽中文評委。2010年獲得美國國務院「民主是甚麼」短文競賽冠軍。這是佐拉親自維護的官方網站。
Visit zuo.laWe analyzed Zuo.la page load time and found that the first response time was 310 ms and then it took 22.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
zuo.la performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value3.3 s
68/100
25%
Value5.9 s
48/100
10%
Value180 ms
91/100
30%
Value0
100/100
15%
Value4.2 s
85/100
10%
310 ms
668 ms
670 ms
258 ms
1675 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 39% of them (82 requests) were addressed to the original Zuo.la, 6% (13 requests) were made to Twoo.com and 6% (13 requests) were made to A.disquscdn.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Messenger.services.live.com.
Page size can be reduced by 1.5 MB (42%)
3.6 MB
2.1 MB
In fact, the total size of Zuo.la main page is 3.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.0 kB or 73% of the original size.
Potential reduce by 60.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. Zuo images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 67% of the original size.
Potential reduce by 233.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. Zuo.la needs all CSS files to be minified and compressed as it can save up to 233.7 kB or 82% of the original size.
Number of requests can be reduced by 100 (55%)
181
81
The browser has sent 181 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zuo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
zuo.la
310 ms
default.css
668 ms
nivo-slider.css
670 ms
jquery-1.2.6.js
258 ms
style.css
1675 ms
ffwidget2.css
6 ms
jquery-1.7.1.min.js
1689 ms
jquery.nivo.slider.js
1682 ms
v1.jsx
63 ms
widget.js
63 ms
gfc_widget
11 ms
widget.php
13 ms
badge_code_v2.gne
145 ms
friendfeed.js
8 ms
logo.gif
7 ms
home.gif
5 ms
index.jpg
7 ms
namecard_front.jpg
11 ms
namecard_back.jpg
9 ms
shenzhen.jpg
10 ms
longjingcun.jpg
12 ms
dameisha.jpg
18 ms
sailimulake.jpg
15 ms
yili.jpg
16 ms
naked.jpg
20 ms
mask.jpg
28 ms
wuping.jpg
27 ms
zhangzhou.jpg
23 ms
dayanqiao.jpg
31 ms
liangmin.jpg
35 ms
beijing.jpg
32 ms
ningxiang.jpg
38 ms
flag.jpg
37 ms
crossegfw.jpg
38 ms
caonima.jpg
42 ms
whatsdemocracy.jpg
47 ms
tamsui.jpg
52 ms
style.css
6 ms
nav_bar.css
90 ms
presenceimage
19812 ms
zola.gif
141 ms
head-bg.png
153 ms
twitter_bubble_logo.gif
41 ms
35px_logo_zola.png
47 ms
fanfou.png
40 ms
twitter.png
42 ms
xml.gif
41 ms
white-grad.png
43 ms
loading.gif
41 ms
hightecklowlife.jpg
43 ms
zola_v.png
44 ms
twcounter.gif
44 ms
travle-map.gif
45 ms
110_b2.gif
45 ms
zuola.com.favicons.png
46 ms
zuo.la.favicons.png
47 ms
wikipedia.favicons.png
46 ms
wealink.favicons.png
48 ms
slidershare_favicons.png
48 ms
youtube.favicons.png
49 ms
6.favicons.png
48 ms
verisignlabs.favicons.png
52 ms
google.reader.favicons.png
49 ms
picasa.favicons.png
50 ms
delicious.favicons.png
52 ms
twitter.favicons.png
52 ms
fanfou.favicons.png
53 ms
bullog.favicons.png
51 ms
tor.favicons.png
97 ms
flickr.favicons.png
54 ms
douban.favicons.png
52 ms
facebook.favicons.png
54 ms
google.favicons.png
53 ms
amazon.favicons.png
55 ms
arrow.gif
54 ms
arrow_2.gif
55 ms
api
107 ms
zuola
70 ms
favicon.gif
70 ms
videoseries
154 ms
47004
19693 ms
embed.js
224 ms
Show
359 ms
flickr.png
21 ms
4751731086_c09458fd29_t.jpg
197 ms
5277875347_7e51b44778_t.jpg
190 ms
p
59 ms
4397657083_2e8c74c98d_t.jpg
193 ms
4692882424_5d6e520d93_t.jpg
165 ms
widget2.css
124 ms
640xNxhigh_tech_low_life-1.jpg.pagespeed.ic_.4CaZyZyA1S.jpg
78 ms
IMG_0224.JPG
25 ms
2.jpg
113 ms
embed
27 ms
delicious.png
5 ms
blog.png
7 ms
picasa.png
5 ms
3001634
56 ms
embed
167 ms
3495970
52 ms
349 ms
blog.friendfeed.com
219 ms
www-embed-player-vfl5foy2V.css
212 ms
www-embed-player.js
282 ms
base.js
409 ms
02424c9533b4f8a9c4a1af88ac26fac3embedcompiled_fastui.css
3 ms
02424c9533b4f8a9c4a1af88ac26fac3embedcompiled__en.js
119 ms
client.js
242 ms
427 ms
widget-top-border.png
131 ms
comment-lighter.png
36 ms
widget-bottom-bg.png
31 ms
bottom_shopping.gif
31 ms
articleitems.gif
39 ms
bottom_qa.gif
37 ms
bottom_help.gif
73 ms
feed_button.png
73 ms
ga.js
37 ms
googlelogo_color_150x54dp.png
76 ms
__utm.gif
46 ms
cb=gapi.loaded_0
45 ms
postmessageRelay
177 ms
veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js
13 ms
ad_status.js
87 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
71 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
90 ms
lounge.load.d074862f091cd9585b295f3979a4eb15.js
68 ms
www.twoo.com
312 ms
1077434459-postmessagerelay.js
51 ms
rpc:shindig_random.js
32 ms
lounge.f668c82e65f78693a6a62a5c7d3e54b8.css
22 ms
config.js
15 ms
common.bundle.2604ea86c00f3bcc98e8fdc57114c1cc.js
92 ms
zh.js
30 ms
lounge.bundle.453d0281788b539960d8683df769dd95.js
40 ms
cb=gapi.loaded_0
16 ms
logo-plus.png
42 ms
googlelogo_color_46x16dp.png
161 ms
proxy.html
343 ms
blank.gif
123 ms
menu_arrow_open.gif
121 ms
icon_print.gif
182 ms
btn_menu6.gif
180 ms
combined_v22.png
200 ms
homepage.css
56 ms
logo-twoo-springme.png
436 ms
webcore.js
287 ms
cedexis.js
257 ms
beach-at-dusk@2x_optimized.jpg
430 ms
appstore.png
431 ms
playstore.png
429 ms
loader-animated.gif
435 ms
blank.gif
457 ms
ga.js
361 ms
loader.5cc23909da9c4a9874500d7a85c4125f.gif
182 ms
discovery.449c10a436c997c3eee5afd5021da3a2.css
171 ms
411 ms
sprite.06bad3144429d24544aa8b00ffd77160.png
161 ms
hp-bkg-form.png
187 ms
icons-hp.png
345 ms
icons.dcb5405f8abc9a80e5628869f735eaf0.woff
185 ms
discovery.bundle.188b7afdc0cb75bb665bca3eb0ce9ba7.js
135 ms
noavatar92.4549c5353ccf103d32a8b81a856576ed.png
99 ms
noavatar92.png
98 ms
event.gif
363 ms
twoo-icons-v3.woff
325 ms
cb=gapi.loaded_0
135 ms
listRelated.json
160 ms
analytics.js
132 ms
homepage.languageselect.js
87 ms
register.js
86 ms
modals.tplmodule.js
95 ms
config.js
94 ms
components.js
131 ms
alert.js
114 ms
events
255 ms
__utm.gif
27 ms
collect
50 ms
api.js
420 ms
radar.js
420 ms
beacon.js
63 ms
like.php
182 ms
atom.png
25 ms
__utm.gif
26 ms
widgets.js
25 ms
plusone.js
54 ms
sdk.js
232 ms
avatar92.jpg
52 ms
collect
100 ms
button.71000885400e222c3c0eec823f8f93f0.js
24 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
68 ms
fastbutton
111 ms
follow_button.fd774b599f565016d763dd860cb31c79.en.html
38 ms
info.json
196 ms
Sh_BYjerrZ8.js
210 ms
LVx-xkvaJ0b.png
226 ms
postmessageRelay
29 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
16 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
17 ms
100 ms
xd_arbiter.php
151 ms
xd_arbiter.php
98 ms
handshake.js
155 ms
api.js
157 ms
xd_arbiter.php
56 ms
jot
26 ms
zuo.la accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
zuo.la best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
zuo.la SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zuo.la can be misinterpreted by Google and other search engines. Our service has detected that English 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 Zuo.la 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.
zuo.la
Open Graph description is not detected on the main page of Zuo. 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: