Tools & Wizards About Us
willow.tv screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

willow.tv

Watch Cricket Live streaming, Replay, Highlights much more| Willow

Page Load Speed

3.5 sec in total

First Response

920 ms

Resources Loaded

2.1 sec

Page Rendered

410 ms

willow.tv screenshot

About Website

Visit willow.tv now to see the best up-to-date Willow content for United States and also check out these interesting facts you probably never knew about willow.tv

Watch live cricket matches, get real-time scores, and enjoy highlights, replays, and schedules for all major cricket leagues and tournaments on Willow.tv

Visit willow.tv

Key Findings

We analyzed Willow.tv page load time and found that the first response time was 920 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

willow.tv performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value5,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.442

21/100

15%

TTI (Time to Interactive)

Value36.0 s

0/100

10%

Network Requests Diagram

willow.tv

920 ms

www.willow.tv

126 ms

gtm.js

95 ms

gpt.js

126 ms

js

234 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Willow.tv, 33% (38 requests) were made to Aimages.willow.tv and 15% (17 requests) were made to Astatic.willow.tv. The less responsive or slowest element that took the longest time to load (949 ms) relates to the external source Static.willow.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 378.5 kB (28%)

Content Size

1.3 MB

After Optimization

967.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Willow.tv main page is 1.3 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. 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 722.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 165.2 kB

  • Original 193.8 kB
  • After minification 168.8 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 25.0 kB, which is 13% 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 165.2 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 24.6 kB

  • Original 380.6 kB
  • After minification 356.1 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. Willow images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 184.6 kB

  • Original 722.5 kB
  • After minification 722.5 kB
  • After compression 537.9 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.6 kB or 26% of the original size.

CSS Optimization

-8%

Potential reduce by 4.1 kB

  • Original 48.6 kB
  • After minification 48.6 kB
  • After compression 44.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. Willow.tv has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 58 (57%)

Requests Now

101

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

willow.tv

willow.tv

920 ms

www.willow.tv

www.willow.tv

126 ms

gtm.js

gtm.js

95 ms

gpt.js

gpt.js

126 ms

js

js

234 ms

beacon.js

beacon.js

61 ms

clipboard.min.js

clipboard.min.js

85 ms

AccessEnabler.js

AccessEnabler.js

159 ms

adobe_primetime_authentication_helper_v1.min.js

adobe_primetime_authentication_helper_v1.min.js

124 ms

css

css

91 ms

bootstrap.min.css

bootstrap.min.css

91 ms

jquery-ui.min.css

jquery-ui.min.css

123 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

154 ms

jquery-ui.1.10.0.min.js

jquery-ui.1.10.0.min.js

155 ms

bootstrap.min.js

bootstrap.min.js

154 ms

common.min.js

common.min.js

153 ms

eventlog.js

eventlog.js

215 ms

common.min.css

common.min.css

153 ms

commonMediaQuery.min.css

commonMediaQuery.min.css

214 ms

headerfooter.min.css

headerfooter.min.css

215 ms

homeui_v1.min.css

homeui_v1.min.css

220 ms

ndhompp_1_v2.css

ndhompp_1_v2.css

223 ms

commonMediaQueryNew_v1.min.css

commonMediaQueryNew_v1.min.css

226 ms

tvproviders.min.css

tvproviders.min.css

227 ms

place1.css

place1.css

226 ms

place2.css

place2.css

225 ms

hmpagpmsubcon.css

hmpagpmsubcon.css

226 ms

cAIS9B0n.js

cAIS9B0n.js

114 ms

owl.carousel.min.css

owl.carousel.min.css

867 ms

owl.theme.default.min.css

owl.theme.default.min.css

871 ms

wlw_optz.css

wlw_optz.css

228 ms

62ea8786ea398af1e9d64da8

62ea8786ea398af1e9d64da8

335 ms

player_api

player_api

111 ms

owl.carousel.min.js

owl.carousel.min.js

949 ms

js

js

228 ms

pubads_impl.js

pubads_impl.js

86 ms

polyfill.js

polyfill.js

177 ms

analytics.js

analytics.js

178 ms

adServerESI.aspx

adServerESI.aspx

308 ms

wlw-nw-lgo.png

wlw-nw-lgo.png

373 ms

ic_mobile.png

ic_mobile.png

365 ms

wllw_logo_primary_v2.png

wllw_logo_primary_v2.png

385 ms

cricclub-ico-wlwhm1_nr1_wlw2.png

cricclub-ico-wlwhm1_nr1_wlw2.png

358 ms

ic_see_more_2xIcon.png

ic_see_more_2xIcon.png

371 ms

tve-dish-w.png

tve-dish-w.png

365 ms

tve-spectrum-w.png

tve-spectrum-w.png

378 ms

tve-optimum-w.png

tve-optimum-w.png

364 ms

tve-fios-w.png

tve-fios-w.png

379 ms

optimumtv_300-53_w.png

optimumtv_300-53_w.png

382 ms

tve-directv-w.png

tve-directv-w.png

382 ms

tve-directv-stream-w.png

tve-directv-stream-w.png

382 ms

tve-xfinity-w.png

tve-xfinity-w.png

384 ms

Dish_79_34.png

Dish_79_34.png

424 ms

spectrum_155_34.png

spectrum_155_34.png

419 ms

Fios_56_34.png

Fios_56_34.png

423 ms

xfinity_105_34.png

xfinity_105_34.png

423 ms

optimum_r_340_110.png

optimum_r_340_110.png

422 ms

optimumtv_300-53_b.png

optimumtv_300-53_b.png

428 ms

toi_logo_ico_wlw.jpg

toi_logo_ico_wlw.jpg

429 ms

hm-shdelin.png

hm-shdelin.png

438 ms

hm-shdelinbig.png

hm-shdelinbig.png

438 ms

spectrum_164_53.png

spectrum_164_53.png

437 ms

optimum_164_53.png

optimum_164_53.png

436 ms

fios_164_53.png

fios_164_53.png

437 ms

dish_164_53.png

dish_164_53.png

437 ms

xfinity_164_53.png

xfinity_164_53.png

443 ms

directtv_340_110.png

directtv_340_110.png

445 ms

directtvstream_340_110.png

directtvstream_340_110.png

444 ms

optimumtv_340_110.png

optimumtv_340_110.png

442 ms

sling_164_53.png

sling_164_53.png

442 ms

Karostream_340_110.png

Karostream_340_110.png

443 ms

NovCam_Devices.png

NovCam_Devices.png

450 ms

ic_Facebook_2xIcon.png

ic_Facebook_2xIcon.png

445 ms

ic_Twitter_2xIcon.png

ic_Twitter_2xIcon.png

444 ms

ic_Insta_Icon.png

ic_Insta_Icon.png

445 ms

ic_youtube_2xIcon.png

ic_youtube_2xIcon.png

446 ms

ic_pinterest_2xIcon.png

ic_pinterest_2xIcon.png

446 ms

uid2SecureSignal.js

uid2SecureSignal.js

155 ms

ob.js

ob.js

160 ms

esp.js

esp.js

160 ms

105 ms

js

js

81 ms

1

1

127 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

126 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

135 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

145 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

148 ms

img_ios_2xIcon.png

img_ios_2xIcon.png

95 ms

ios_google_play_store_2xIcon.png

ios_google_play_store_2xIcon.png

88 ms

9cdb65b1-e652-4904-b75c-3455c4dcda2c-async.js

9cdb65b1-e652-4904-b75c-3455c4dcda2c-async.js

84 ms

collect

collect

28 ms

collect

collect

17 ms

js

js

48 ms

ga-audiences

ga-audiences

105 ms

3490721242191156539

3490721242191156539

7 ms

generic

generic

28 ms

esp

esp

49 ms

generic

generic

3 ms

pd

pd

70 ms

8351fb40-4357-e83f-f61c-6d416cb2c1c8

8351fb40-4357-e83f-f61c-6d416cb2c1c8

51 ms

openx

openx

18 ms

pixel

pixel

101 ms

pixel

pixel

103 ms

sd

sd

90 ms

www-widgetapi.js

www-widgetapi.js

75 ms

index.html

index.html

67 ms

dcm

dcm

56 ms

container.html

container.html

43 ms

pixel

pixel

37 ms

pixel

pixel

36 ms

sd

sd

30 ms

AccessEnablerProxy.html

AccessEnablerProxy.html

19 ms

AccessEnablerProxy.js

AccessEnablerProxy.js

6 ms

polyfill.js

polyfill.js

6 ms

collect

collect

7 ms

collect

collect

33 ms

Accessibility Review

willow.tv accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

willow.tv best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

willow.tv SEO score

69

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Willow.tv can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Willow.tv 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.

Social Sharing Optimization

willow.tv

Open Graph data is detected on the main page of Willow. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: