13.3 sec in total
200 ms
12.8 sec
228 ms
Click here to check amazing Yshare content. Otherwise, check out these important facts you probably never knew about yshare.info
See related links to what you are looking for.
Visit yshare.infoWe analyzed Yshare.info page load time and found that the first response time was 200 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yshare.info performance score
200 ms
979 ms
110 ms
86 ms
124 ms
Our browser made a total of 175 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Yshare.info, 7% (12 requests) were made to Static.xx.fbcdn.net and 6% (11 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source Myfastbooking.com.
Page size can be reduced by 989.0 kB (57%)
1.7 MB
750.9 kB
In fact, the total size of Yshare.info main page is 1.7 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. 75% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 159.6 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 159.6 kB or 85% of the original size.
Potential reduce by 21.3 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. Yshare images are well optimized though.
Potential reduce by 587.7 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 587.7 kB or 56% of the original size.
Potential reduce by 220.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. Yshare.info needs all CSS files to be minified and compressed as it can save up to 220.5 kB or 85% of the original size.
Number of requests can be reduced by 95 (58%)
164
69
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yshare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.myfastbooking.com
200 ms
cache.manifest
979 ms
cloudflare.min.js
110 ms
jquery.min.js
86 ms
jquery-ui.min.js
124 ms
bootstrap.min.js
153 ms
switchery.min.js
1007 ms
widgets.js
83 ms
my1003201601.js
1031 ms
adsbygoogle.js
74 ms
bootstrap.min.css
1066 ms
jquery-ui.min.css
156 ms
switchery.css
1028 ms
element.js
117 ms
CACHE.html
957 ms
analytics.js
58 ms
dc.js
90 ms
eC72rYfxZkirTdPvj8fDng.js
372 ms
sdk.js
152 ms
css
85 ms
hover-min.css
13 ms
collect
17 ms
collect
56 ms
__utm.gif
35 ms
ga.js
82 ms
bg.jpg
997 ms
211.png
4244 ms
__utm.gif
78 ms
mfb.png
21 ms
gosocial.png
1018 ms
gopremium.png
1034 ms
donateus.png
1083 ms
fk.jpg
1033 ms
az.jpg
1705 ms
sd.jpg
1015 ms
ib.jpg
1982 ms
train.png
2021 ms
firefox.png
1081 ms
firefoxandroid.png
1115 ms
chrome.png
1081 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
70 ms
translateelement.css
63 ms
main.js
90 ms
74 ms
72 ms
xd_arbiter.php
357 ms
ca-pub-1505715935925092.js
16 ms
zrt_lookup.html
305 ms
show_ads_impl.js
224 ms
platform.js
378 ms
element_main.js
279 ms
glyphicons-halflings-regular.woff
907 ms
terms.html
1718 ms
faq.html
1711 ms
privacy.html
1853 ms
how.html
2385 ms
updateext.html
2667 ms
acbn.html
2686 ms
referearn.html
2735 ms
adblock.html
2719 ms
reviews.txt
2756 ms
StationList2.js
3315 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
144 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
121 ms
ads
249 ms
glyphicons-social-regular.woff
2505 ms
like.php
96 ms
page.php
149 ms
osd.js
86 ms
ads
177 ms
translate_24dp.png
109 ms
l
89 ms
cleardot.gif
208 ms
qeKvIRsJabD.js
275 ms
LVx-xkvaJ0b.png
319 ms
ads
238 ms
cb=gapi.loaded_0
79 ms
cb=gapi.loaded_1
95 ms
fastbutton
146 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
39 ms
Ezryo55Cca5.css
341 ms
q68gy-v_YMF.js
377 ms
YvxwM8R7ol8.js
348 ms
ihptErjAmMX.js
431 ms
ads
307 ms
te_ctrl3.gif
39 ms
css
54 ms
m_js_controller.js
88 ms
abg.js
117 ms
198 ms
adj
155 ms
beacon
140 ms
postmessageRelay
118 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
35 ms
favicon
74 ms
googlelogo_color_112x36dp.png
37 ms
nessie_icon_thin_arrow_big_white.png
37 ms
jot
240 ms
s
35 ms
x_button_blue2.png
25 ms
131 ms
adj
59 ms
beacon
42 ms
3193398744-postmessagerelay.js
124 ms
rpc:shindig_random.js
50 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
21 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
75 ms
75 ms
0
277 ms
surly.js
180 ms
16622353767559374398
95 ms
redir.html
611 ms
index.html
380 ms
verify_selector.js
337 ms
blank.gif
334 ms
109 ms
cb=gapi.loaded_0
83 ms
a.js;p=11022203414291;a=11022203414399;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=1458281860
249 ms
verify_selector.js
298 ms
blank.gif
279 ms
10891534_838299349559945_4976316585114226225_n.png
243 ms
1395184_1383681438537335_1445143173_n.jpg
335 ms
12733584_1102794263106887_3736932483497077450_n.jpg
360 ms
12190965_680858612016281_8507955864508939890_n.jpg
383 ms
12669570_1673218586249467_1019555923311974885_n.jpg
349 ms
12745725_1069107529779060_8152516499893470627_n.jpg
382 ms
10172674_624134691048026_2608584093854511288_n.jpg
351 ms
wL6VQj7Ab77.png
113 ms
s7jcwEQH7Sx.png
113 ms
ba.html
112 ms
pixel
109 ms
pixel
96 ms
4.gif
94 ms
lidar.js
37 ms
sbhK2lTE.js
47 ms
pixel
158 ms
pixel
160 ms
cTrvNaRi.html
51 ms
4311.js
39 ms
verifyr.js
68 ms
10476422_PricingPlan_728x90.gif
106 ms
setuid
103 ms
verifyr.js
61 ms
FaceBody_728x90_logo.gif
55 ms
FaceBody_728x90_bg.jpg
104 ms
beacon.js
82 ms
0
29 ms
bg.png
39 ms
adchoices.en.png
40 ms
sd
10 ms
R9a_DtVRZgv.js
20 ms
cUDgRFxaoIk.js
23 ms
0JBr1QHp8Gi.js
20 ms
kDOzhTr2W91.js
58 ms
box_19_top-right.png
11 ms
ci.png
11 ms
iframe.html
118 ms
__utm.gif
13 ms
__utm.gif
13 ms
collect
6 ms
__utm.gif
5 ms
activeview
12 ms
__utm.gif
36 ms
__utm.gif
14 ms
collect
4 ms
__utm.gif
6 ms
__utm.gif
34 ms
__utm.gif
30 ms
s1.png
8271 ms
st2.png
946 ms
__utm.gif
24 ms
__utm.gif
11 ms
track.js
168 ms
ui
14 ms
yshare.info SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yshare.info 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), while the claimed language is English. Our system also found out that Yshare.info 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.
yshare.info
Open Graph data is detected on the main page of Yshare. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: