FATE-GO.US Fate/Grand Order Official USA Website

fate-go.us Website Information

Daily Unique Visits: 4,588

Daily Page Views: 18,352

Income Per Day: $51

Estimated Value: $27,540

fate-go.us is registered under .US top-level domain. Please check other sites in .US zone.

No name server records were found.

and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

The highest website fate-go.us position in Alexa rank database was 14585 and the lowest rank position was 987108. Current position of fate-go.us in Alexa rank database is 273501.

Desktop speed score of fate-go.us (41/100) is better than the results of 15.65% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of fate-go.us (65/100) is better than the results of 13.11% of other sites and means that the page is not mobile-friendly.

Mobile speed score of fate-go.us (37/100) is better than the results of 15.74% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

fate-go.us Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


fate-go.us whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: fate-go.us
Registry Domain ID: D58262493-US
Registrar WHOIS Server: whois.ionos.com
Registrar URL: https://ionos.com
Updated Date: 2023-03-19T00:00:01Z
Creation Date: 2017-02-02T19:06:52Z
Registry Expiry Date: 2024-02-01T23:59:59Z
Registrar: IONOS SE
Registrar IANA ID: 83
Registrar Abuse Contact Email: abuse@ionos.com
Registrar Abuse Contact Phone: +1.8772064253
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: C58262479-US
Registrant Name: Hiroe Tsukamoto
Registrant Organization: Aniplex of America Inc.
Registrant Street: 2120 Colorado Ave
Registrant Street:
Registrant Street:
Registrant City: Santa Monica
Registrant State/Province: CA
Registrant Postal Code: 90404
Registrant Country: US
Registrant Phone: +1.3104538594
Registrant Phone Ext:
Registrant Fax: +1.3108293743
Registrant Fax Ext:
Registrant Email: shu.nishimoto@aniplex.jp
Registrant Application Purpose: P1
Registrant Nexus Category: C11
Registry Admin ID: C58262480-US
Admin Name: Hiroe Tsukamoto
Admin Organization: Aniplex of America Inc.
Admin Street: 2120 Colorado Ave
Admin Street:
Admin Street:
Admin City: Santa Monica
Admin State/Province: CA
Admin Postal Code: 90404
Admin Country: US
Admin Phone: +1.3104538594
Admin Phone Ext:
Admin Fax: +1.3108293743
Admin Fax Ext:
Admin Email: shu.nishimoto@aniplex.jp
Admin Application Purpose: P1
Admin Nexus Category: C11
Registry Tech ID: C4543631-US
Tech Name: Hostmaster ONEANDONE
Tech Organization: 1&1 Internet Inc.
Tech Street: 701 Lee Rd.
Tech Street: Suite 300
Tech Street:
Tech City: Chesterbrook
Tech State/Province: PA
Tech Postal Code: 19087
Tech Country: US
Tech Phone: +1.8774612631
Tech Phone Ext:
Tech Fax: +1.6105601501
Tech Fax Ext:
Tech Email: hostmaster@1and1.com
Name Server: ns-1775.awsdns-29.co.uk
Name Server: ns-1529.awsdns-63.org
Name Server: ns-705.awsdns-24.net
Name Server: ns-128.awsdns-16.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-10-12T20:19:19Z

fate-go.us server information

Servers Location

fate-go.us desktop page speed rank

Last tested: 2018-07-09


Desktop Speed Bad
41/100

fate-go.us Desktop Speed Test Quick Summary


priority - 100Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 975.6KiB (71% reduction).

Compressing and resizing http://fate-go.us/images/event_100658765.png could save 436.8KiB (86% reduction).
Compressing and resizing http://fate-go.us/images/new_event_08242017.png could save 147.2KiB (73% reduction).
Compressing and resizing http://fate-go.us/images/banner_manwaka.png could save 86.6KiB (80% reduction).
Compressing and resizing http://fate-go.us/images/usetip-biginers.jpg could save 61.1KiB (90% reduction).
Compressing and resizing http://fate-go.us/images/banner/banner_fgo_ost.jpg could save 58.4KiB (90% reduction).
Compressing and resizing http://fate-go.us/images/banner/banner_gudao.png could save 42.1KiB (73% reduction).
Compressing and resizing http://fate-go.us/images/banner/banner_fgoa_02.jpg could save 41.7KiB (88% reduction).
Compressing http://fate-go.us/images/pc_header_nav.png could save 20.1KiB (40% reduction).
Compressing http://fate-go.us/images/pc_footer_bg.gif could save 15.6KiB (45% reduction).
Compressing and resizing http://fate-go.us/images/banner/faq2.png could save 14.4KiB (67% reduction).
Compressing http://fate-go.us/images/pc_servant_title.png could save 11.1KiB (30% reduction).
Compressing http://fate-go.us/images/pc_download_bg.png could save 9.6KiB (14% reduction).
Compressing http://fate-go.us/images/pc_cv_title.png could save 7.2KiB (32% reduction).
Compressing http://fate-go.us/images/pc_tvcm_txt1r.png?v=2 could save 6.3KiB (35% reduction).
Compressing http://fate-go.us/images/banner/pc_banner_fategoanime.jpg could save 4.5KiB (42% reduction).
Compressing http://fate-go.us/images/banner/pc_banner_fatezero.jpg could save 4.1KiB (44% reduction).
Compressing http://fate-go.us/images/pc_spec_txts.png could save 3.5KiB (33% reduction).
Compressing http://fate-go.us/images/pc_tvcm_txt2r.png could save 1.3KiB (11% reduction).
Compressing http://fate-go.us/images/pc_tvcm_more3.png could save 946B (38% reduction).
Compressing http://fate-go.us/images/banner/pc_banner_sn_anime.jpg could save 809B (17% reduction).
Compressing http://fate-go.us/images/pc_servant_button.png could save 761B (38% reduction).
Compressing http://fate-go.us/images/pc_download_badge_android.png could save 708B (21% reduction).
Compressing http://fate-go.us/images/pc_download_badge_ios.png could save 535B (20% reduction).
Compressing http://fate-go.us/images/pc_tvcm_obi_pv02.png?v=20161205 could save 308B (15% reduction).

priority - 35Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://fate-go.us/css/index_pc.css (60 seconds)
http://fate-go.us/css/index_pc_eor.css (60 seconds)
http://fate-go.us/css/jquery.bxslider.css (60 seconds)
http://fate-go.us/css/jquery.fancybox.css (60 seconds)
http://fate-go.us/css/pop_layer.css (60 seconds)
http://fate-go.us/event_camelot/assets/img/pop_camelot.png (60 seconds)
http://fate-go.us/functions/js/eor-animation.js (60 seconds)
http://fate-go.us/functions/js/jquery.bxslider.min.js (60 seconds)
http://fate-go.us/functions/js/jquery.cookie.js (60 seconds)
http://fate-go.us/functions/js/jquery.fancybox-media.js (60 seconds)
http://fate-go.us/functions/js/jquery.fancybox.pack.js (60 seconds)
http://fate-go.us/functions/js/layerBoard.js (60 seconds)
http://fate-go.us/images/available_now.png (60 seconds)
http://fate-go.us/images/banner/banner_fgo_ost.jpg (60 seconds)
http://fate-go.us/images/banner/banner_fgoa_02.jpg (60 seconds)
http://fate-go.us/images/banner/banner_gudao.png (60 seconds)
http://fate-go.us/images/banner/faq2.png (60 seconds)
http://fate-go.us/images/banner/pc_banner_fategoanime.jpg (60 seconds)
http://fate-go.us/images/banner/pc_banner_fatezero.jpg (60 seconds)
http://fate-go.us/images/banner/pc_banner_sn_anime.jpg (60 seconds)
http://fate-go.us/images/banner_manwaka.png (60 seconds)
http://fate-go.us/images/bg.gif (60 seconds)
http://fate-go.us/images/event_100658765.png (60 seconds)
http://fate-go.us/images/mainvisual2.png (60 seconds)
http://fate-go.us/images/new_event_08242017.png (60 seconds)
http://fate-go.us/images/pc_bg_illust01.png (60 seconds)
http://fate-go.us/images/pc_bg_illust02.png (60 seconds)
http://fate-go.us/images/pc_bg_illust03.png (60 seconds)
http://fate-go.us/images/pc_bg_illust04.png (60 seconds)
http://fate-go.us/images/pc_copy.png (60 seconds)
http://fate-go.us/images/pc_cv_actors.png?v=2 (60 seconds)
http://fate-go.us/images/pc_cv_base_line.png (60 seconds)
http://fate-go.us/images/pc_cv_pic.png (60 seconds)
http://fate-go.us/images/pc_cv_title.png (60 seconds)
http://fate-go.us/images/pc_download_badge_android.png (60 seconds)
http://fate-go.us/images/pc_download_badge_ios.png (60 seconds)
http://fate-go.us/images/pc_download_bg.png (60 seconds)
http://fate-go.us/images/pc_footer_bg.gif (60 seconds)
http://fate-go.us/images/pc_footer_nav_01.png (60 seconds)
http://fate-go.us/images/pc_footer_nav_02.png (60 seconds)
http://fate-go.us/images/pc_footer_nav_03.png (60 seconds)
http://fate-go.us/images/pc_footer_nav_05.png (60 seconds)
http://fate-go.us/images/pc_footer_nav_06.png (60 seconds)
http://fate-go.us/images/pc_header_nav.png (60 seconds)
http://fate-go.us/images/pc_logo.png (60 seconds)
http://fate-go.us/images/pc_screen_pv_08.png (60 seconds)
http://fate-go.us/images/pc_servant_base_line.png (60 seconds)
http://fate-go.us/images/pc_servant_button.png (60 seconds)
http://fate-go.us/images/pc_servant_pic.png (60 seconds)
http://fate-go.us/images/pc_servant_title.png (60 seconds)
http://fate-go.us/images/pc_sns_facebook.png (60 seconds)
http://fate-go.us/images/pc_sns_sharebox.png (60 seconds)
http://fate-go.us/images/pc_sns_twitter.png (60 seconds)
http://fate-go.us/images/pc_spec_line02.png (60 seconds)
http://fate-go.us/images/pc_spec_logo.png (60 seconds)
http://fate-go.us/images/pc_spec_txts.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_01.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_02.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_03.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_04.png (60 seconds)
http://fate-go.us/images/pc_staff_title.png (60 seconds)
http://fate-go.us/images/pc_tvcm_base_line2.png?v=2 (60 seconds)
http://fate-go.us/images/pc_tvcm_more3.png (60 seconds)
http://fate-go.us/images/pc_tvcm_obi_pv02.png?v=20161205 (60 seconds)
http://fate-go.us/images/pc_tvcm_txt1r.png?v=2 (60 seconds)
http://fate-go.us/images/pc_tvcm_txt2r.png (60 seconds)
http://fate-go.us/images/pc_tvcm_waku2.png?v=2 (60 seconds)
http://fate-go.us/images/totop.png (60 seconds)
http://fate-go.us/images/usetip-biginers.jpg (60 seconds)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://code.jquery.com/jquery-1.11.2.min.js
http://code.jquery.com/ui/1.11.4/jquery-ui.min.js
https://cdnjs.cloudflare.com/ajax/libs/buzz/1.1.9/buzz.min.js
http://fate-go.us/functions/js/jquery.bxslider.min.js
http://fate-go.us/functions/js/jquery.fancybox.pack.js
http://fate-go.us/functions/js/jquery.fancybox-media.js
http://fate-go.us/functions/js/fgo.js
http://fate-go.us/functions/js/layerBoard.js

Optimize CSS Delivery of the following:

http://code.jquery.com/ui/1.11.4/themes/cupertino/jquery-ui.css
http://fate-go.us/css/animate.css
http://fate-go.us/css/jquery.fancybox.css
http://fate-go.us/css/jquery.bxslider.css
http://fate-go.us/css/index_pc.css
http://fate-go.us/css/index_pc_eor.css
http://fate-go.us/css/pop_layer.css

priority - 10Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 96.9KiB (74% reduction).

Compressing http://fate-go.us/css/index_pc.css could save 39.9KiB (86% reduction).
Compressing http://fate-go.us/functions/js/jquery.fancybox.pack.js could save 14.2KiB (62% reduction).
Compressing http://fate-go.us/functions/js/jquery.bxslider.min.js could save 13.9KiB (73% reduction).
Compressing http://fate-go.us/ could save 13.7KiB (73% reduction).
Compressing http://fate-go.us/css/jquery.fancybox.css could save 3.5KiB (71% reduction).
Compressing http://fate-go.us/functions/js/jquery.fancybox-media.js could save 3.3KiB (62% reduction).
Compressing http://fate-go.us/css/jquery.bxslider.css could save 2.7KiB (68% reduction).
Compressing http://fate-go.us/functions/js/layerBoard.js could save 2.6KiB (69% reduction).
Compressing http://fate-go.us/functions/js/jquery.cookie.js could save 1.7KiB (55% reduction).
Compressing http://fate-go.us/functions/js/eor-animation.js could save 721B (53% reduction).
Compressing http://fate-go.us/css/index_pc_eor.css could save 631B (62% reduction).
Compressing http://fate-go.us/css/pop_layer.css could save 229B (49% reduction).

priority - 2Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 18.2KiB (29% reduction).

Minifying http://fate-go.us/css/index_pc.css could save 14.6KiB (32% reduction).
Minifying http://code.jquery.com/ui/1.11.4/themes/cupertino/jquery-ui.css could save 1.4KiB (17% reduction) after compression.
Minifying http://fate-go.us/css/jquery.fancybox.css could save 1,009B (20% reduction).
Minifying http://fate-go.us/css/jquery.bxslider.css could save 1,007B (26% reduction).
Minifying http://fate-go.us/css/index_pc_eor.css could save 156B (16% reduction).
Minifying http://fate-go.us/css/pop_layer.css could save 110B (24% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 7.2KiB (54% reduction).

Minifying http://fate-go.us/functions/js/jquery.fancybox-media.js could save 3KiB (57% reduction).
Minifying http://fate-go.us/functions/js/layerBoard.js could save 2.3KiB (61% reduction).
Minifying http://fate-go.us/functions/js/jquery.cookie.js could save 1.3KiB (44% reduction).
Minifying http://fate-go.us/functions/js/eor-animation.js could save 674B (50% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 4.9KiB (26% reduction).

Minifying http://fate-go.us/ could save 4.9KiB (26% reduction).

fate-go.us Desktop Resource Breakdown

Total Resources78
Number of Hosts5
Static Resources74
JavaScript Resources10
CSS Resources6

fate-go.us mobile page speed rank

Last tested: 2017-06-07


Mobile Speed Bad
37/100

fate-go.us Mobile Speed Test Quick Summary


priority - 76Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 739.1KiB (70% reduction).

Compressing http://fate-go.us/images/promotion_banner2.png could save 608.8KiB (86% reduction).
Compressing http://fate-go.us/images/banner/banner_fgo_ost.jpg could save 31.8KiB (50% reduction).
Compressing http://fate-go.us/images/banner/banner_fgoa_02.jpg could save 21.8KiB (47% reduction).
Compressing http://fate-go.us/images/pc_header_nav.png could save 20.1KiB (40% reduction).
Compressing http://fate-go.us/images/pc_footer_bg.gif could save 15.6KiB (45% reduction).
Compressing http://fate-go.us/images/pc_servant_title.png could save 11.1KiB (30% reduction).
Compressing http://fate-go.us/images/pc_cv_title.png could save 7.2KiB (32% reduction).
Compressing http://fate-go.us/images/pc_tvcm_txt1r.png?v=2 could save 6.3KiB (35% reduction).
Compressing http://fate-go.us/images/banner/pc_banner_fategoanime.jpg could save 4.5KiB (42% reduction).
Compressing http://fate-go.us/images/news_thumb.jpg could save 4.1KiB (20% reduction).
Compressing http://fate-go.us/images/banner/pc_banner_fatezero.jpg could save 4.1KiB (44% reduction).
Compressing http://fate-go.us/images/pc_tvcm_txt2r.png could save 1.3KiB (11% reduction).
Compressing http://fate-go.us/images/pc_tvcm_more3.png could save 946B (38% reduction).
Compressing http://fate-go.us/images/banner/pc_banner_sn_anime.jpg could save 809B (17% reduction).
Compressing http://fate-go.us/images/pc_servant_button.png could save 761B (38% reduction).

priority - 46Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://fate-go.us/SYS/CONTENTS/2017060208495349529956/w349 (60 seconds)
http://fate-go.us/SYS/CONTENTS/2017060709192341274576/w534 (60 seconds)
http://fate-go.us/css/animate.css (60 seconds)
http://fate-go.us/css/index_pc.css (60 seconds)
http://fate-go.us/css/jquery.bxslider.css (60 seconds)
http://fate-go.us/css/jquery.fancybox.css (60 seconds)
http://fate-go.us/functions/js/fgo.js (60 seconds)
http://fate-go.us/functions/js/jquery.bxslider.min.js (60 seconds)
http://fate-go.us/functions/js/jquery.cookie.js (60 seconds)
http://fate-go.us/functions/js/jquery.fancybox-media.js (60 seconds)
http://fate-go.us/functions/js/jquery.fancybox.pack.js (60 seconds)
http://fate-go.us/images/banner/banner_fgo_ost.jpg (60 seconds)
http://fate-go.us/images/banner/banner_fgoa_02.jpg (60 seconds)
http://fate-go.us/images/banner/pc_banner_fategoanime.jpg (60 seconds)
http://fate-go.us/images/banner/pc_banner_fatezero.jpg (60 seconds)
http://fate-go.us/images/banner/pc_banner_sn_anime.jpg (60 seconds)
http://fate-go.us/images/bg.gif (60 seconds)
http://fate-go.us/images/coming_in_summer2017.png (60 seconds)
http://fate-go.us/images/mainvisual.png?v=2 (60 seconds)
http://fate-go.us/images/news_thumb.jpg (60 seconds)
http://fate-go.us/images/pc_bg_illust01.png (60 seconds)
http://fate-go.us/images/pc_bg_illust02.png (60 seconds)
http://fate-go.us/images/pc_bg_illust03.png (60 seconds)
http://fate-go.us/images/pc_bg_illust04.png (60 seconds)
http://fate-go.us/images/pc_copy.png (60 seconds)
http://fate-go.us/images/pc_cv_actors.png?v=2 (60 seconds)
http://fate-go.us/images/pc_cv_base_line.png (60 seconds)
http://fate-go.us/images/pc_cv_pic.png (60 seconds)
http://fate-go.us/images/pc_cv_title.png (60 seconds)
http://fate-go.us/images/pc_footer_bg.gif (60 seconds)
http://fate-go.us/images/pc_footer_nav_02.png (60 seconds)
http://fate-go.us/images/pc_footer_nav_03.png (60 seconds)
http://fate-go.us/images/pc_footer_nav_05.png (60 seconds)
http://fate-go.us/images/pc_header_bg.png (60 seconds)
http://fate-go.us/images/pc_header_nav.png (60 seconds)
http://fate-go.us/images/pc_logo.png (60 seconds)
http://fate-go.us/images/pc_screen_pv_06.png (60 seconds)
http://fate-go.us/images/pc_servant_base_line.png (60 seconds)
http://fate-go.us/images/pc_servant_button.png (60 seconds)
http://fate-go.us/images/pc_servant_pic.png (60 seconds)
http://fate-go.us/images/pc_servant_title.png (60 seconds)
http://fate-go.us/images/pc_sns_facebook.png (60 seconds)
http://fate-go.us/images/pc_sns_sharebox.png (60 seconds)
http://fate-go.us/images/pc_sns_sharebox_bottom.png (60 seconds)
http://fate-go.us/images/pc_sns_twitter.png (60 seconds)
http://fate-go.us/images/pc_spec_line02.png (60 seconds)
http://fate-go.us/images/pc_spec_logo.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_01.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_02.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_03.png (60 seconds)
http://fate-go.us/images/pc_staff_h3_04.png (60 seconds)
http://fate-go.us/images/pc_staff_title.png (60 seconds)
http://fate-go.us/images/pc_tvcm_base_line2.png?v=2 (60 seconds)
http://fate-go.us/images/pc_tvcm_more3.png (60 seconds)
http://fate-go.us/images/pc_tvcm_obi_pv02.png?v=20161205 (60 seconds)
http://fate-go.us/images/pc_tvcm_txt1r.png?v=2 (60 seconds)
http://fate-go.us/images/pc_tvcm_txt2r.png (60 seconds)
http://fate-go.us/images/pc_tvcm_waku2.png?v=2 (60 seconds)
http://fate-go.us/images/promotion_banner2.png (60 seconds)
http://fate-go.us/images/totop.png (60 seconds)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://code.jquery.com/jquery-1.11.2.min.js
http://code.jquery.com/ui/1.11.4/jquery-ui.min.js
https://cdnjs.cloudflare.com/ajax/libs/buzz/1.1.9/buzz.min.js
https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
http://fate-go.us/functions/js/jquery.bxslider.min.js
http://fate-go.us/functions/js/jquery.fancybox.pack.js
http://fate-go.us/functions/js/jquery.fancybox-media.js
http://fate-go.us/functions/js/fgo.js

Optimize CSS Delivery of the following:

http://code.jquery.com/ui/1.11.4/themes/cupertino/jquery-ui.css
http://fate-go.us/css/animate.css
http://fate-go.us/css/jquery.fancybox.css
http://fate-go.us/css/jquery.bxslider.css
http://fate-go.us/css/index_pc.css

priority - 16Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 160.4KiB (81% reduction).

Compressing http://fate-go.us/css/animate.css could save 63.3KiB (94% reduction).
Compressing http://fate-go.us/css/index_pc.css could save 39.1KiB (85% reduction).
Compressing http://fate-go.us/functions/js/jquery.fancybox.pack.js could save 14.2KiB (62% reduction).
Compressing http://fate-go.us/functions/js/jquery.bxslider.min.js could save 13.9KiB (73% reduction).
Compressing http://fate-go.us/ could save 11.6KiB (73% reduction).
Compressing http://fate-go.us/functions/js/fgo.js could save 7.2KiB (71% reduction).
Compressing http://fate-go.us/css/jquery.fancybox.css could save 3.5KiB (71% reduction).
Compressing http://fate-go.us/functions/js/jquery.fancybox-media.js could save 3.3KiB (62% reduction).
Compressing http://fate-go.us/css/jquery.bxslider.css could save 2.7KiB (68% reduction).
Compressing http://fate-go.us/functions/js/jquery.cookie.js could save 1.7KiB (55% reduction).

priority - 3Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 29.3KiB (23% reduction).

Minifying http://fate-go.us/css/index_pc.css could save 14.3KiB (32% reduction).
Minifying http://fate-go.us/css/animate.css could save 11.6KiB (18% reduction).
Minifying http://code.jquery.com/ui/1.11.4/themes/cupertino/jquery-ui.css could save 1.4KiB (17% reduction) after compression.
Minifying http://fate-go.us/css/jquery.fancybox.css could save 1,009B (20% reduction).
Minifying http://fate-go.us/css/jquery.bxslider.css could save 1,007B (26% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 8.8KiB (48% reduction).

Minifying http://fate-go.us/functions/js/fgo.js could save 4.5KiB (45% reduction).
Minifying http://fate-go.us/functions/js/jquery.fancybox-media.js could save 3KiB (57% reduction).
Minifying http://fate-go.us/functions/js/jquery.cookie.js could save 1.3KiB (44% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 4.3KiB (28% reduction).

Minifying http://fate-go.us/ could save 4.3KiB (28% reduction).

fate-go.us Mobile Resource Breakdown

Total Resources71
Number of Hosts6
Static Resources66
JavaScript Resources11
CSS Resources5

fate-go.us mobile page usability

Last tested: 2017-06-07


Mobile Usability Medium
65/100

fate-go.us Mobile Usability Test Quick Summary


priority - 30Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,015 CSS pixels wide, but the viewport is only 640 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="mainVisual"> falls outside the viewport.
The element <p class="ill01"></p> falls outside the viewport.
The element <span class="illust"> falls outside the viewport.
The element <span class="line"> falls outside the viewport.
The element <span class="line"> falls outside the viewport.
The element <p class="ill04"></p> falls outside the viewport.
The element <h1>Fate/Grand Order</h1> falls outside the viewport.
The element <h3>News</h3> falls outside the viewport.
The element <img src="/images/news_thumb.jpg"> falls outside the viewport.
The element <p class="date">06.06.2017</p> falls outside the viewport.
The element <p class="title">New Servant Cl…NCER&quot; updated!</p> falls outside the viewport.
The element <img src="/images/news_thumb.jpg"> falls outside the viewport.
The element <p class="date">06.01.2017</p> falls outside the viewport.
The element <p class="title">New Promotion:…avenger Hunt!!</p> falls outside the viewport.
The element <a href="/news/" class="morelink">&gt;&gt;More</a> falls outside the viewport.
The element <a href="http://twitter…tags=FateGOUSA">twitter</a> falls outside the viewport.
The element <a href="http://www.fac…ww.fate-go.us/">facebook</a> falls outside the viewport.
The element <img src="/images/banner…er_fgo_ost.jpg"> falls outside the viewport.
The element <a href="" class="bx-pager-link">1</a> falls outside the viewport.
The element <a href="" class="bx-pager-link active">2</a> falls outside the viewport.
The element <a href="" class="bx-prev">Prev</a> falls outside the viewport.
The element <a href="" class="bx-next">Next</a> falls outside the viewport.
The element <h2>Type-Moon pres…new Fate RPG!</h2> falls outside the viewport.
The element <img src="/images/pc_screen_pv_06.png"> falls outside the viewport.
The element <a href="https://www.yo…?v=byjDskIyDhI" class="play playVideoLink">Trailer</a> falls outside the viewport.
The element <a href="/gallery/" class="newslink">Click for more details &gt;</a> falls outside the viewport.
The element <span class="ribbon">Trailer</span> falls outside the viewport.
The element <h2>In addition to…in the battle!</h2> falls outside the viewport.
The element <a href="/servant/" class="detaillink">Click for more details &gt;</a> falls outside the viewport.
The element <h2>Featuring Orig…Japanese Voice</h2> falls outside the viewport.
The element <img src="/images/pc_cv_pic.png" class="pic"> falls outside the viewport.
The element <h3 class="h304">Developed by:…r: Mieko Hosoi</h3> falls outside the viewport.
The element <div class="wrapper">fate/Grand Order</div> falls outside the viewport.
The element <h4>[System Requirements]</h4> falls outside the viewport.
The element <p class="sub">*Please confir…sions of OSes.</p> falls outside the viewport.
The element <p class="sub">*It is possibl…sions of OSes.</p> falls outside the viewport.
The element <a href="/servant/">Servant</a> falls outside the viewport.
The element <a href="/gallery/">Gallery</a> falls outside the viewport.
The element <img src="/images/banner…r_sn_anime.jpg"> falls outside the viewport.
The element <img src="/images/banner…r_fatezero.jpg"> falls outside the viewport.
The element <a href="http://www.fate-go.jp/">&gt; Japanese Site</a> falls outside the viewport.
The element <a href="http://aniplexusa.com/">&gt; Aniplex of America</a> falls outside the viewport.

priority - 14Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

News renders only 7 pixels tall (12 CSS pixels).
06.06.2017 and 1 others render only 6 pixels tall (10 CSS pixels).
New Promotion:…avenger Hunt!! and 1 others render only 7 pixels tall (12 CSS pixels).
&gt;&gt;More renders only 7 pixels tall (12 CSS pixels).
*It is possibl…ion or higher. and 5 others render only 7 pixels tall (11 CSS pixels).
&gt;&gt;Fate/Grand O…al USA Website and 2 others render only 7 pixels tall (11 CSS pixels).
©TYPE-MOON / FGO PROJECT renders only 7 pixels tall (11 CSS pixels).
&gt; Aniplex of America and 1 others render only 7 pixels tall (12 CSS pixels).

priority - 10Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

priority - 2Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/news/" class="morelink">&gt;&gt;More</a> is close to 1 other tap targets.
The tap target <a href="http://twitter…tags=FateGOUSA">twitter</a> is close to 1 other tap targets.
The tap target <a href="http://www.fac…ww.fate-go.us/">facebook</a> is close to 1 other tap targets.
The tap target <a href="http://fategra…/products.html"></a> is close to 1 other tap targets.
The tap target <div class="bx-pager bx-default-pager">12</div> is close to 1 other tap targets.
The tap target <a href="" class="bx-pager-link">1</a> is close to 1 other tap targets.
The tap target <a href="" class="bx-pager-link active">2</a> is close to 1 other tap targets.
The tap target <a href="" class="bx-prev">Prev</a> is close to 1 other tap targets.
The tap target <a href="" class="bx-next">Next</a> is close to 1 other tap targets.

fate-go.us HTML validation

Errors

A document must not include both a “meta” element with an “http-equiv” attribute whose value is “content-type”, and a “meta” element with a “charset” attribute.

Line: 5 Column: 9 - 75
"...> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> ..."

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Line: 6 Column: 9 - 73
"...> <meta http-equiv="Content-Script-Type" content="text/javascript"> ..."

Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.

Line: 7 Column: 9 - 65
"...> <meta http-equiv="Content-Style-Type" content="text/css"> ..."

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 8 Column: 9 - 71
"...> <meta http-equiv="X-UA-Compatible" content="IE=edge, chrome=1"> ..."

Duplicate attribute “class”.

Line: 111 Column: - 41
"...ontainer" class="pc"> ..."

Attribute “target” not allowed on element “img” at this point.

Line: 148 Column: 69 - 160
"...te-go.us"><img src="/images/banner/faq2.png" width="226" height="50" target="_blank" alt="Contact us"></a> ..."

Duplicate ID “banner”.

Line: 164 Column: 21 - 37
"... <div id="banner"> ..."

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 9 Column: 9 - 67
"...> <meta name="viewport" content="width=640,user-scalable=no"> ..."

The first occurrence of ID “banner” was here.

Line: 145 Column: 21 - 37
"... <div id="banner"> ..."

fate-go.us similar domains

Similar domains:
www.fate-go.com
www.fate-go.net
www.fate-go.org
www.fate-go.info
www.fate-go.biz
www.fate-go.us
www.fate-go.mobi
www.ate-go.us
www.fate-go.us
www.cate-go.us
www.fcate-go.us
www.cfate-go.us
www.date-go.us
www.fdate-go.us
www.dfate-go.us
www.rate-go.us
www.frate-go.us
www.rfate-go.us
www.tate-go.us
www.ftate-go.us
www.tfate-go.us
www.gate-go.us
www.fgate-go.us
www.gfate-go.us
www.vate-go.us
www.fvate-go.us
www.vfate-go.us
www.fte-go.us
www.fqte-go.us
www.faqte-go.us
www.fqate-go.us
www.fwte-go.us
www.fawte-go.us
www.fwate-go.us
www.fste-go.us
www.faste-go.us
www.fsate-go.us
www.fzte-go.us
www.fazte-go.us
www.fzate-go.us
www.fae-go.us
www.fare-go.us
www.fatre-go.us
www.farte-go.us
www.fafe-go.us
www.fatfe-go.us
www.fafte-go.us
www.fage-go.us
www.fatge-go.us
www.fagte-go.us
www.faye-go.us
www.fatye-go.us
www.fayte-go.us
www.fat-go.us
www.fatw-go.us
www.fatew-go.us
www.fatwe-go.us
www.fats-go.us
www.fates-go.us
www.fatse-go.us
www.fatd-go.us
www.fated-go.us
www.fatde-go.us
www.fatr-go.us
www.fater-go.us
www.fatego.us
www.fate-o.us
www.fate-fo.us
www.fate-gfo.us
www.fate-fgo.us
www.fate-vo.us
www.fate-gvo.us
www.fate-vgo.us
www.fate-to.us
www.fate-gto.us
www.fate-tgo.us
www.fate-bo.us
www.fate-gbo.us
www.fate-bgo.us
www.fate-yo.us
www.fate-gyo.us
www.fate-ygo.us
www.fate-ho.us
www.fate-gho.us
www.fate-hgo.us
www.fate-g.us
www.fate-gi.us
www.fate-goi.us
www.fate-gio.us
www.fate-gk.us
www.fate-gok.us
www.fate-gko.us
www.fate-gl.us
www.fate-gol.us
www.fate-glo.us
www.fate-gp.us
www.fate-gop.us
www.fate-gpo.us

fate-go.us Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


fate-go.us TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.