Tools & Wizards About Us
watchjim.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

watchjim.com

Disney.com | The official home for all things Disney

Page Load Speed

1.2 sec in total

First Response

211 ms

Resources Loaded

978 ms

Page Rendered

0 ms

watchjim.com screenshot

About Website

Welcome to watchjim.com homepage info - get ready to check Watchjim best content right away, or after learning these important things about watchjim.com

The official website for all things Disney: theme parks, resorts, movies, tv programs, characters, games, videos, music, shopping, and more!

Visit watchjim.com

Key Findings

We analyzed Watchjim.com page load time and found that the first response time was 211 ms and then it took 978 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

watchjim.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value25.0 s

0/100

10%

TBT (Total Blocking Time)

Value36,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.102

89/100

15%

TTI (Time to Interactive)

Value52.0 s

0/100

10%

Network Requests Diagram

watchjim.com

211 ms

270 ms

global.js

185 ms

script.js

184 ms

omniture_dadt_account.js

187 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 14% of them (1 request) were addressed to the original Watchjim.com, 71% (5 requests) were made to Dadt.com and 14% (1 request) were made to Global.go.com. The less responsive or slowest element that took the longest time to load (454 ms) relates to the external source Dadt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.5 kB (62%)

Content Size

59.1 kB

After Optimization

22.7 kB

  • HTML
  • JavaScript

In fact, the total size of Watchjim.com main page is 59.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 57.8 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 615 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 701 B

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 615 B or 47% of the original size.

JavaScript Optimization

-62%

Potential reduce by 35.9 kB

  • Original 57.8 kB
  • After minification 50.8 kB
  • After compression 22.0 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 35.9 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (80%)

Requests Now

5

After Optimization

1

  • JavaScript

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watchjim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

watchjim.com

watchjim.com

211 ms

270 ms

global.js

global.js

185 ms

script.js

script.js

184 ms

omniture_dadt_account.js

omniture_dadt_account.js

187 ms

s_code.js

s_code.js

454 ms

master_flash_light.js

master_flash_light.js

309 ms

Accessibility Review

watchjim.com accessibility score

84

Accessibility Issues

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

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

Best Practices

watchjim.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

watchjim.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watchjim.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 Watchjim.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

watchjim.com

Open Graph description is not detected on the main page of Watchjim. 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: