30.3 sec in total
10 sec
17.9 sec
2.3 sec
Click here to check amazing Yy content. Otherwise, check out these important facts you probably never knew about yy.my
Visit yy.myWe analyzed Yy.my page load time and found that the first response time was 10 sec and then it took 20.3 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.
yy.my performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value1.3 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.2 s
100/100
10%
10047 ms
12 ms
507 ms
546 ms
539 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 32% of them (35 requests) were addressed to the original Yy.my, 29% (32 requests) were made to Apis.google.com and 22% (24 requests) were made to Playedonline.com. The less responsive or slowest element that took the longest time to load (10 sec) belongs to the original domain Yy.my.
Page size can be reduced by 536.3 kB (72%)
745.9 kB
209.6 kB
In fact, the total size of Yy.my main page is 745.9 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. 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 279.6 kB which makes up the majority of the site volume.
Potential reduce by 189.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 189.6 kB or 90% of the original size.
Potential reduce by 7.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. Yy images are well optimized though.
Potential reduce by 184.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 184.5 kB or 66% of the original size.
Potential reduce by 154.9 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. Yy.my needs all CSS files to be minified and compressed as it can save up to 154.9 kB or 86% of the original size.
Number of requests can be reduced by 46 (48%)
96
50
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
yy.my
10047 ms
ga.js
12 ms
buddybar.css
507 ms
nggallery.css
546 ms
shutter-reloaded.css
539 ms
swa.css
576 ms
events_manager.css
620 ms
default.css
1049 ms
responsive.css
1079 ms
l10n.js
1116 ms
jquery.js
1625 ms
shutter-reloaded.js
1149 ms
jquery.cycle.all.min.js
1173 ms
ngg.slideshow.min.js
1598 ms
global.js
1603 ms
jquery.lazyload.mini.js
1691 ms
theme.js
1702 ms
add2home.js
1744 ms
swa.js
2147 ms
bp-share-it.js
2171 ms
jquery.innerfade.js
2178 ms
style.css
2199 ms
general.css
2273 ms
shadowbox.css
61 ms
shadowbox.js
61 ms
__utm.gif
12 ms
shadowbox.css
52 ms
shadowbox.js
1069 ms
plusone.js
63 ms
adsbygoogle.js
6 ms
jq_fade.css
303 ms
Kill_Birds_With_Rockets_2.jpg
29 ms
background.gif
602 ms
34b6e8d3a7195d2c93989293de7b6f4e-bpthumb.jpg
601 ms
tweet.png
600 ms
share.png
599 ms
linkedin.png
597 ms
digg.png
630 ms
email.png
1110 ms
rss.png
1194 ms
Pixelotl.jpg
29 ms
IQ_Ball.jpg
28 ms
gunexpress.jpg
30 ms
DuckLife2_World_Champion.jpg
31 ms
Best_Friends_Forever_3.jpg
31 ms
Sagoo2.jpg
48 ms
fitted.jpg
71 ms
Ultimate_War.jpg
71 ms
Carnival_Showdown.jpg
71 ms
60pc_black.png
1195 ms
Kill_Birds_With_Rockets_2.jpg
47 ms
Pixelotl.jpg
1081 ms
IQ_Ball.jpg
2080 ms
gunexpress.jpg
3022 ms
DuckLife2_World_Champion.jpg
4014 ms
Best_Friends_Forever_3.jpg
5031 ms
Sagoo2.jpg
5942 ms
cb=gapi.loaded_0
15 ms
cb=gapi.loaded_1
14 ms
fastbutton
192 ms
fitted.jpg
4946 ms
Carnival_Showdown.jpg
3915 ms
Ultimate_War.jpg
3012 ms
fastbutton
80 ms
postmessageRelay
75 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
46 ms
fastbutton
98 ms
fastbutton
129 ms
3193398744-postmessagerelay.js
123 ms
rpc:shindig_random.js
121 ms
fastbutton
122 ms
fastbutton
142 ms
fastbutton
111 ms
cb=gapi.loaded_0
55 ms
fastbutton
72 ms
fastbutton
58 ms
fastbutton
92 ms
fastbutton
103 ms
fastbutton
83 ms
fastbutton
82 ms
fastbutton
97 ms
fastbutton
88 ms
fastbutton
84 ms
fastbutton
81 ms
fastbutton
82 ms
fastbutton
215 ms
fastbutton
77 ms
fastbutton
104 ms
fastbutton
148 ms
fastbutton
100 ms
fastbutton
115 ms
fastbutton
511 ms
60pc_black.png
517 ms
admin-menu-arrow.gif
504 ms
external.min.php
494 ms
ca-pub-3928849302384355.js
699 ms
zrt_lookup.html
695 ms
show_ads_impl.js
470 ms
grey.gif
311 ms
ads
161 ms
style.min.css
137 ms
loader-14x14.gif
139 ms
get.php
228 ms
tooltip-loader.gif
23 ms
osd.js
17 ms
resources.js
178 ms
theme.css
160 ms
yellow.s.png
84 ms
is.png
29 ms
yy.my accessibility score
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
Document doesn't have a <title> element
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
yy.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
yy.my SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yy.my 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 Yy.my 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.
yy.my
Open Graph description is not detected on the main page of Yy. 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: