go.com Go.com | The Walt Disney Company 

Mobile Usability

99/100

Good

Mobile Speed

47/100

Bad

Last tested: 2017-08-27

Rescan
go.com Mobile Usability: 99/100
go.com Mobile Usability Test Quick Overview

Size 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 <html class="js canvas touc…ers no-cssgrid">Go.com | The W…ghts Reserved,</html> is close to 2 other tap targets.
The tap target <section id="ref-1-2" class="module watch_p…ry-theme light">AdvertisementS…isney Princess</section> is close to 1 other tap targets.
The tap target <a href="https://help.disney.com/">Disney Help</a> and 6 others are close to other tap targets.
go.com Mobile Speed: 47/100
go.com Mobile Speed Test Quick Overview

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

Your page has 3 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.
http://a.dilcdn.com/a/head-effd208fb162.js
http://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js
http://a.dilcdn.com/a/application-f0358c5122dc.js
Optimize CSS Delivery of the following:
http://a.dilcdn.com/a/application-fef9a59558c2.css
http://a.dilcdn.com/a/modules-867d0a85a66a.css
http://a.dilcdn.com/a/unique-modules-8628289ca3db.css
http://a.dilcdn.com/a/international-modules-adbbf7fa0991.css
http://a.dilcdn.com/a/goc/wide-857de41a9da0.css
http://a.dilcdn.com/a/goc/responsive-mobile-d25be7c66fd1.css
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 369.9KiB (54% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/videothum…ion=0%2C0%2C1024%2C576 could save 96.8KiB (50% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/rich_mobi…peg?region=0,0,640,444 could save 78.5KiB (69% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/image_2d4…0&width=320&height=180 could save 70.4KiB (78% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/image_50c…0&width=320&height=180 could save 23KiB (57% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/image_6a9…0&width=320&height=180 could save 22.1KiB (56% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/videothum…6&width=320&height=180 could save 21.2KiB (52% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/vt_omd_di…0&width=320&height=180 could save 19.3KiB (52% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/image_ef7…0&width=320&height=180 could save 18KiB (51% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/image_410…0&width=320&height=180 could save 10.7KiB (40% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/open-uri2…gion=0%2C0%2C640%2C320 could save 7.9KiB (16% reduction).
Compressing https://lumiere-a.akamaihd.net/v1/images/image_e09…0&width=320&height=180 could save 1.1KiB (11% reduction).
Compressing http://a.dilcdn.com/a/goc/nav-logo-dark@2x-2b3eb08c507c.png could save 1,014B (21% reduction).
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 4% of the final above-the-fold content could be rendered with the full HTML response.
Leverage 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://aglobal.go.com/stat/dolWebAnalytics.js (expiration not specified)
http://secure-us.imrworldwide.com/novms/js/2/ggcmb390.js (expiration not specified)
http://cdnapi.kaltura.com/api_v3/index.php?service…8e507ea7fe6307ead5386e (60 seconds)
http://cdnapi.kaltura.com/html5/html5lib/v2.55.2/m…aylist12playerElement0 (4.4 minutes)
http://cdnapisec.kaltura.com/p/1068292/sp/10682920…132/partner_id/1068292 (6.3 minutes)
http://imasdk.googleapis.com/js/sdkloader/ima3.js (15 minutes)
http://www.googletagservices.com/tag/js/gpt_mobile.js (15 minutes)
https://cdn.registerdisney.go.com/v2/outer/DisneyID.js (15 minutes)
http://cfvod.kaltura.com/p/1068292/sp/106829200/th…dth/100/vid_slices/100 (60 minutes)

go.com Mobile Resources


Total Resources112
Number of Hosts28
Static Resources60
JavaScript Resources21
CSS Resources9

go.com Mobile Resource Breakdown