11.1 sec in total
531 ms
9.2 sec
1.4 sec
Click here to check amazing Alefarah content. Otherwise, check out these important facts you probably never knew about alefarah.com
2020年最新最全av优选推荐合家欢1一54全文在线阅读,和老板在办公室BD 中文,和老板在办公室BD 中文,在av优选可以找到,合家欢1一54全文在线阅读,和老板在办公室BD 中文,和老板在办公室BD 中文
Visit alefarah.comWe analyzed Alefarah.com page load time and found that the first response time was 531 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
alefarah.com performance score
531 ms
24 ms
20 ms
51 ms
22 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Alefarah.com, 16% (22 requests) were made to Treme.com.br and 11% (15 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Facebook.com.
Page size can be reduced by 1.2 MB (37%)
3.1 MB
1.9 MB
In fact, the total size of Alefarah.com main page is 3.1 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. 85% 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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 118.5 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 23.3 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 118.5 kB or 88% of the original size.
Potential reduce by 111.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. Alefarah images are well optimized though.
Potential reduce by 724.5 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 724.5 kB or 61% of the original size.
Potential reduce by 202.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. Alefarah.com needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.
Number of requests can be reduced by 41 (33%)
126
85
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alefarah. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and as a result speed up the page load time.
alefarah.com
531 ms
pre_tumblelog.js
24 ms
jquery-latest.min.js
20 ms
code
51 ms
tumblelog_post_message_queue.js
22 ms
plusone.js
86 ms
tweets.js
287 ms
index.js
40 ms
analytics.js
16 ms
tp_02.jpg
206 ms
0wmq0en.jpg
33 ms
english.jpg
308 ms
tumblr_o4awo6TMIv1qabbgwo1_500.jpg
167 ms
tumblr_o43dn0bddR1qabbgwo1_500.jpg
12 ms
Captura_de_Tela_2016_03_03_a_s_20_08_38.png
35 ms
tumblr_o499jndcHC1qabbgwo1_500.jpg
275 ms
tumblr_o44xsfCO5u1qabbgwo1_500.jpg
295 ms
tumblr_o41tureL9K1qabbgwo1_500.jpg
294 ms
tumblr_o3wpsfsEHg1qabbgwo1_500.jpg
302 ms
tumblr_o3wdtspTUw1qabbgwo1_500.jpg
279 ms
brwCIwN.png
32 ms
HBFAp57.png
38 ms
Ll5RmLQ.png
34 ms
tv.png
300 ms
print.png
304 ms
mais.png
296 ms
iconevideo.jpg
299 ms
iconefoto.jpg
300 ms
tp_03.jpg
200 ms
tp_04.jpg
201 ms
tp_05.jpg
190 ms
tp_06.jpg
191 ms
tp_07.jpg
191 ms
tp_08.jpg
227 ms
tp_09.jpg
233 ms
tp_10.jpg
236 ms
preto.jpg
235 ms
permalink.png
238 ms
relogio.png
242 ms
notas.png
273 ms
tags.png
268 ms
email.png
272 ms
twitter-lateral.png
273 ms
tumblr_o42wvsnBG41qabbgwo1_500.jpg
26 ms
tumblr_o3yfbumSjp1qabbgwo1_500.jpg
22 ms
tumblr_o3xzfywkfu1qabbgwo1_500.jpg
25 ms
tumblr_o3xgvqgp5q1qabbgwo1_500.jpg
24 ms
tumblr_o3wgvomTRb1qabbgwo1_400.jpg
21 ms
collect
10 ms
grupo_parceiro_inteira.js
412 ms
barra_uol.html
4 ms
modernizr-1.7.min.js
4 ms
site_logo_topo.png
20 ms
uoltm.js
392 ms
conteudo_menu_band2.png
1036 ms
gtm.js
27 ms
collect
4 ms
G6UizaGnQYg
100 ms
widgets.js
232 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
53 ms
fastbutton
114 ms
ga.js
41 ms
like.php
351 ms
www-embed-player-vflfNyN_r.css
164 ms
www-embed-player.js
277 ms
base.js
455 ms
postmessageRelay
327 ms
cb=gapi.loaded_0
82 ms
cb=gapi.loaded_1
60 ms
fastbutton
164 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
289 ms
like.php
470 ms
collect
258 ms
7jaUcXEpcYQ
209 ms
fastbutton
201 ms
like.php
320 ms
like.php
393 ms
parceiro-async.js
512 ms
band.js
616 ms
qeKvIRsJabD.js
350 ms
LVx-xkvaJ0b.png
321 ms
like.php
288 ms
like.php
335 ms
3193398744-postmessagerelay.js
336 ms
rpc:shindig_random.js
246 ms
like.php
323 ms
ga-audiences
364 ms
like.php
334 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
227 ms
ad_status.js
285 ms
like.php
7316 ms
fastbutton
143 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
78 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
127 ms
-YqvPsAt2mo
195 ms
like.php
190 ms
like.php
154 ms
like.php
145 ms
cb=gapi.loaded_0
133 ms
like.php
163 ms
fastbutton
136 ms
like.php
108 ms
logo-uol-52x52.png
736 ms
20anos.svg
1088 ms
like.php
103 ms
uol-text-regular.woff
921 ms
uol-text-light.woff
1581 ms
uol-icones-setas.woff
1583 ms
conteudo_menu_band2.png
33 ms
impixu
248 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
185 ms
fastbutton
177 ms
impixu
86 ms
analytics.html
147 ms
login_check.html
12 ms
avatar_ed490c7cad78_40.png
72 ms
iframe_logo.png
63 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
148 ms
rapid-3.36.js
44 ms
rapidworker-1.2.js
42 ms
ga.js
124 ms
analytics.js
118 ms
cs.js
123 ms
addthis.html
151 ms
yql
335 ms
__utm.gif
22 ms
addthis_widget.js
59 ms
api.html
32 ms
300lo.json
66 ms
sh.8e5f85691f9aaa082472a194.html
51 ms
jot.html
27 ms
uoldna.html
563 ms
dna-persist.min.js
1103 ms
sample
314 ms
cedexis.radar.js
5 ms
alefarah.com SEO score
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alefarah.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Alefarah.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.
alefarah.com
Open Graph description is not detected on the main page of Alefarah. 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: