23.6 sec in total
561 ms
22.8 sec
334 ms
Welcome to hoyoyo.com homepage info - get ready to check Hoyoyo best content for China right away, or after learning these important things about hoyoyo.com
Proxy shopping service for mercari Japan, yahoo auctions auto bid in Real-Time, rakuma, rakuten, surugaya, amazon.co.jp and other Japanese online stores. Buy from Japan and ship to USA, UK, Europe, Ca...
Visit hoyoyo.comWe analyzed Hoyoyo.com page load time and found that the first response time was 561 ms and then it took 23.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
hoyoyo.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value8.9 s
1/100
25%
Value20.8 s
0/100
10%
Value120 ms
97/100
30%
Value0.092
91/100
15%
Value21.9 s
1/100
10%
561 ms
1211 ms
497 ms
486 ms
488 ms
Our browser made a total of 255 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Hoyoyo.com, 87% (221 requests) were made to Us.hoyoyo.com and 3% (7 requests) were made to Image.hoyoyo.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Tajs.qq.com.
Page size can be reduced by 863.0 kB (46%)
1.9 MB
1.0 MB
In fact, the total size of Hoyoyo.com main page is 1.9 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. 70% of websites need less resources to load. Images take 815.4 kB which makes up the majority of the site volume.
Potential reduce by 236.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. This page needs HTML code to be minified as it can gain 41.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 236.0 kB or 82% of the original size.
Potential reduce by 110.0 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. Obviously, Hoyoyo needs image optimization as it can save up to 110.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 455.6 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 455.6 kB or 66% of the original size.
Potential reduce by 61.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. Hoyoyo.com needs all CSS files to be minified and compressed as it can save up to 61.5 kB or 82% of the original size.
Number of requests can be reduced by 59 (24%)
251
192
The browser has sent 251 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hoyoyo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
hoyoyo.com
561 ms
us.hoyoyo.com
1211 ms
index.css
497 ms
nav-v.css
486 ms
nav-h.css
488 ms
dd.css
488 ms
jquery-ui-1.8.1.css
498 ms
importUiJs.php
1303 ms
vtip.js
852 ms
vtip.css
850 ms
commonTools.js
1081 ms
jquery.translate.js
1162 ms
jquery.cookie.js
1102 ms
sdk.js
960 ms
sdk.js
959 ms
register.dev.js
1331 ms
facebook.dev.js
1151 ms
login.dev.js
1325 ms
search.js
1152 ms
jquery.ajaxmanager.js
1386 ms
menutop.js
1541 ms
FTraditiona.js
1555 ms
slideshow.css
1343 ms
slideshow.js
1792 ms
index_item.css
1568 ms
jquery.tools.min.js
2565 ms
jquery.lazyload.js
1663 ms
service.css
1561 ms
stat.php
1421 ms
stats
20255 ms
stat.php
1130 ms
connect.6.1
284 ms
ajax-loader-status.gif
773 ms
hoyoyologo_en.png
795 ms
banner4_en.jpg
1828 ms
simcard_en.jpg
1046 ms
wj_banner_en.jpg
1065 ms
sanrio-en.jpg
1921 ms
bnr_accept_120x30_y.gif
1215 ms
loading2.gif
893 ms
Yahoo-ico.gif
698 ms
Rakuten-ico.gif
882 ms
Taobao-ico.gif
905 ms
yahoo.png
1191 ms
rakuten.png
1230 ms
taobao.png
1345 ms
othershopping.png
1358 ms
mobile_logo.jpg
1386 ms
rakuten.logo.png
1825 ms
yahoo.logo.png
1829 ms
taobao.logo.png
1914 ms
surugaya.logo.png
1918 ms
others.logo.png
1920 ms
cm_en.png
1930 ms
getNaviImgImage.ajax.php
2135 ms
getNaviImgImage.ajax.php
2198 ms
getNaviImgImage.ajax.php
2313 ms
getNaviImgImage.ajax.php
2328 ms
getNaviImgImage.ajax.php
2355 ms
new.gif
2409 ms
bzf_en.gif
2609 ms
all.js
327 ms
rightbnt2.gif
2706 ms
rightbnt_en.jpg
2780 ms
taobaoCrown.png
2771 ms
letian.png
2654 ms
yahoo.png
2674 ms
taobao.png
2898 ms
getNaviImgImage.ajax.php
2876 ms
112 ms
xd_arbiter.php
301 ms
xd_arbiter.php
529 ms
getNaviImgImage.ajax.php
2865 ms
getNaviImgImage.ajax.php
2873 ms
getNaviImgImage.ajax.php
2897 ms
getNaviImgImage.ajax.php
2716 ms
getNaviImgImage.ajax.php
2938 ms
getNaviImgImage.ajax.php
2966 ms
getNaviImgImage.ajax.php
3469 ms
getNaviImgImage.ajax.php
3012 ms
getNaviImgImage.ajax.php
3464 ms
getNaviImgImage.ajax.php
3003 ms
getNaviImgImage.ajax.php
4127 ms
getNaviImgImage.ajax.php
2995 ms
getNaviImgImage.ajax.php
3046 ms
getNaviImgImage.ajax.php
3066 ms
getNaviImgImage.ajax.php
4048 ms
getNaviImgImage.ajax.php
3242 ms
b2222.png
523 ms
dc.js
312 ms
analytics.js
308 ms
b222hover.png
606 ms
google_ga.js
3783 ms
xd_arbiter.php
157 ms
stat.htm
683 ms
collect
53 ms
__utm.gif
26 ms
login_button.php
67 ms
collect
13 ms
__utm.gif
23 ms
getNaviImgImage.ajax.php
2976 ms
stat.htm
617 ms
getNaviImgImage.ajax.php
3015 ms
login_button.php
95 ms
getNaviImgImage.ajax.php
3249 ms
getNaviImgImage.ajax.php
3434 ms
ajax_category.php
3508 ms
IK_wUPJ6vpZ.js
669 ms
teE39sffXW8.png
738 ms
iqVGY7gYXlg.gif
809 ms
getNaviImgImage.ajax.php
3580 ms
getNaviImgImage.ajax.php
3672 ms
getNaviImgImage.ajax.php
3515 ms
getNaviImgImage.ajax.php
3580 ms
getNaviImgImage.ajax.php
3655 ms
getNaviImgImage.ajax.php
3715 ms
getNaviImgImage.ajax.php
3715 ms
getNaviImgImage.ajax.php
3666 ms
getNaviImgImage.ajax.php
3615 ms
getNaviImgImage.ajax.php
3613 ms
getNaviImgImage.ajax.php
3727 ms
getNaviImgImage.ajax.php
3810 ms
getNaviImgImage.ajax.php
3717 ms
getNaviImgImage.ajax.php
3812 ms
getNaviImgImage.ajax.php
4394 ms
getNaviImgImage.ajax.php
3655 ms
getNaviImgImage.ajax.php
3754 ms
getNaviImgImage.ajax.php
3834 ms
getNaviImgImage.ajax.php
3709 ms
getNaviImgImage.ajax.php
3757 ms
getNaviImgImage.ajax.php
3535 ms
getNaviImgImage.ajax.php
3701 ms
getNaviImgImage.ajax.php
3473 ms
getNaviImgImage.ajax.php
3592 ms
getNaviImgImage.ajax.php
3559 ms
getNaviImgImage.ajax.php
3529 ms
getNaviImgImage.ajax.php
3717 ms
getNaviImgImage.ajax.php
3532 ms
getNaviImgImage.ajax.php
3352 ms
getNaviImgImage.ajax.php
3407 ms
getNaviImgImage.ajax.php
3564 ms
getNaviImgImage.ajax.php
5431 ms
getNaviImgImage.ajax.php
3324 ms
getNaviImgImage.ajax.php
3318 ms
getNaviImgImage.ajax.php
3313 ms
getNaviImgImage.ajax.php
3313 ms
getNaviImgImage.ajax.php
3514 ms
getNaviImgImage.ajax.php
3424 ms
getNaviImgImage.ajax.php
3390 ms
getNaviImgImage.ajax.php
3367 ms
getNaviImgImage.ajax.php
3471 ms
getNaviImgImage.ajax.php
3639 ms
getNaviImgImage.ajax.php
3469 ms
getNaviImgImage.ajax.php
3412 ms
getNaviImgImage.ajax.php
3420 ms
getNaviImgImage.ajax.php
3595 ms
getNaviImgImage.ajax.php
3797 ms
getNaviImgImage.ajax.php
3688 ms
getNaviImgImage.ajax.php
3548 ms
getNaviImgImage.ajax.php
4903 ms
getNaviImgImage.ajax.php
4570 ms
getNaviImgImage.ajax.php
3779 ms
getNaviImgImage.ajax.php
3657 ms
getNaviImgImage.ajax.php
3554 ms
getNaviImgImage.ajax.php
4125 ms
getNaviImgImage.ajax.php
3953 ms
getNaviImgImage.ajax.php
3830 ms
getNaviImgImage.ajax.php
3719 ms
getNaviImgImage.ajax.php
4174 ms
getNaviImgImage.ajax.php
4080 ms
getNaviImgImage.ajax.php
4027 ms
getNaviImgImage.ajax.php
4362 ms
getNaviImgImage.ajax.php
3890 ms
getNaviImgImage.ajax.php
4335 ms
getNaviImgImage.ajax.php
4107 ms
getNaviImgImage.ajax.php
4065 ms
getNaviImgImage.ajax.php
3743 ms
getNaviImgImage.ajax.php
3776 ms
getNaviImgImage.ajax.php
4018 ms
getNaviImgImage.ajax.php
4051 ms
getNaviImgImage.ajax.php
3944 ms
getNaviImgImage.ajax.php
3694 ms
getNaviImgImage.ajax.php
3713 ms
getNaviImgImage.ajax.php
3768 ms
getNaviImgImage.ajax.php
3980 ms
getNaviImgImage.ajax.php
3799 ms
getNaviImgImage.ajax.php
3616 ms
getNaviImgImage.ajax.php
3667 ms
getNaviImgImage.ajax.php
3682 ms
getNaviImgImage.ajax.php
3691 ms
getNaviImgImage.ajax.php
3757 ms
getNaviImgImage.ajax.php
3412 ms
getNaviImgImage.ajax.php
3487 ms
getNaviImgImage.ajax.php
3578 ms
getNaviImgImage.ajax.php
3213 ms
getNaviImgImage.ajax.php
3176 ms
getNaviImgImage.ajax.php
3425 ms
greySpacer.png
3417 ms
getNaviImgImage.ajax.php
2994 ms
SurferServer
2866 ms
twtwdlogin.png
3070 ms
twusdlogin.png
3013 ms
30percent.png
3225 ms
bg_trans.png
2909 ms
ajax-loader.gif
2906 ms
dd_arrow.png
2961 ms
leftmenutop2.png
2801 ms
pagetitle.gif
2750 ms
Rlinebg.jpg
2973 ms
popupimg.jpg
2907 ms
ui-bg_flat_75_ffffff_40x100.png
2905 ms
ui-bg_highlight-hard_100_fee119_1x100.png
2893 ms
ui-bg_diagonals-medium_50_b81900_40x40.png
2819 ms
ui-icons_cd0a0a_256x240.png
2782 ms
ui-bg_diagonals-medium_100_ffe45c_40x40.png
2756 ms
ui-icons_2e83ff_256x240.png
2990 ms
dd_arrow.gif
2961 ms
us.png
2664 ms
au.png
2635 ms
ca.gif
2597 ms
cn.png
3255 ms
gb.png
2552 ms
hk.png
2460 ms
jp.png
2694 ms
my.png
2557 ms
sg.png
2800 ms
tw.png
2584 ms
eu.jpg
2296 ms
earth.png
2650 ms
ui-icons_222222_256x240.png
2580 ms
23336.png
2688 ms
23632.png
2756 ms
22152.png
2611 ms
21600.png
2774 ms
21964.png
2756 ms
25464.png
2693 ms
24242.png
3128 ms
20000.png
2793 ms
24698.png
2649 ms
26318.png
2829 ms
23000.png
2836 ms
23140.png
2836 ms
42177.png
3051 ms
23976.png
3032 ms
24198.png
2806 ms
2084055844.png
2829 ms
22896.png
2777 ms
26086.png
2784 ms
2084043920.png
3124 ms
24202.png
3108 ms
2084032594.png
3553 ms
20060.png
3137 ms
2084060731.png
3525 ms
2084217893.png
3681 ms
26084.png
3450 ms
hoyoyo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hoyoyo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hoyoyo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Hoyoyo.com 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 Hoyoyo.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.
hoyoyo.com
Open Graph description is not detected on the main page of Hoyoyo. 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: