Tools & Wizards About Us
11wicket.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

11wicket.com

Play Fantasy Cricket, Fantasy football & Win Prizes | 11wickets

Page Load Speed

1.2 sec in total

First Response

14 ms

Resources Loaded

685 ms

Page Rendered

543 ms

11wicket.com screenshot

About Website

Visit 11wicket.com now to see the best up-to-date 11 Wicket content and also check out these interesting facts you probably never knew about 11wicket.com

Fantasy cricket & fantasy football leagues only on 11wickets online fantasy cricket app. Make your dream team, play and win huge cash prizes.

Visit 11wicket.com

Key Findings

We analyzed 11wicket.com page load time and found that the first response time was 14 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

11wicket.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value390 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

11wicket.com

14 ms

www.11wickets.com

57 ms

css2

46 ms

all.css

176 ms

v0.js

31 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original 11wicket.com, 38% (13 requests) were made to 11wickets.com and 32% (11 requests) were made to Cdn.ampproject.org. The less responsive or slowest element that took the longest time to load (437 ms) relates to the external source 11wickets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.9 kB (10%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 11wicket.com main page is 1.5 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 93.8 kB

  • Original 115.5 kB
  • After minification 96.3 kB
  • After compression 21.7 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 19.2 kB, which is 17% 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 93.8 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 53.7 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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. 11 Wicket images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 400 B

  • Original 222.2 kB
  • After minification 222.2 kB
  • After compression 221.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 11.0 kB
  • After minification 11.0 kB
  • After compression 11.0 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. 11wicket.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (40%)

Requests Now

25

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

11wicket.com

11wicket.com

14 ms

www.11wickets.com

www.11wickets.com

57 ms

css2

css2

46 ms

all.css

all.css

176 ms

v0.js

v0.js

31 ms

amp-analytics-0.1.js

amp-analytics-0.1.js

52 ms

amp-sidebar-0.1.js

amp-sidebar-0.1.js

62 ms

amp-carousel-0.2.js

amp-carousel-0.2.js

62 ms

amp-youtube-0.1.js

amp-youtube-0.1.js

62 ms

amp-accordion-0.1.js

amp-accordion-0.1.js

60 ms

amp-bind-0.1.js

amp-bind-0.1.js

61 ms

amp-form-0.1.js

amp-form-0.1.js

58 ms

amp-mustache-0.2.js

amp-mustache-0.2.js

69 ms

amp-font-0.1.js

amp-font-0.1.js

69 ms

amp-selector-0.1.js

amp-selector-0.1.js

68 ms

main-loyalty-banner.jpg

main-loyalty-banner.jpg

435 ms

main-slider-sports.jpg

main-slider-sports.jpg

418 ms

khel-banner.jpg

khel-banner.jpg

437 ms

playing-experience-bg.jpg

playing-experience-bg.jpg

411 ms

our-fans-bg.jpg

our-fans-bg.jpg

22 ms

pratik-ghosh.jpg

pratik-ghosh.jpg

29 ms

avinash-tiwari.jpg

avinash-tiwari.jpg

30 ms

puja-nair.jpg

puja-nair.jpg

47 ms

how-to-play-bg.jpg

how-to-play-bg.jpg

48 ms

most-trusted-bg.jpg

most-trusted-bg.jpg

57 ms

exclusive-feature.jpg

exclusive-feature.jpg

56 ms

chat-icon.svg

chat-icon.svg

58 ms

S6uyw4BMUTPHvxk6WQev.ttf

S6uyw4BMUTPHvxk6WQev.ttf

36 ms

S6u9w4BMUTPHh7USew-FHi_o.ttf

S6u9w4BMUTPHh7USew-FHi_o.ttf

37 ms

S6u9w4BMUTPHh6UVew-FHi_o.ttf

S6u9w4BMUTPHh6UVew-FHi_o.ttf

63 ms

S6u9w4BMUTPHh50Xew-FHi_o.ttf

S6u9w4BMUTPHh50Xew-FHi_o.ttf

63 ms

fa-solid-900.woff

fa-solid-900.woff

89 ms

fa-regular-400.woff

fa-regular-400.woff

120 ms

fa-brands-400.woff

fa-brands-400.woff

156 ms

Accessibility Review

11wicket.com accessibility score

94

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

button, link, and menuitem elements do not have accessible names.

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

Links do not have a discernible name

Best Practices

11wicket.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

11wicket.com SEO score

93

Search Engine Optimization Advices

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

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 11wicket.com 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 11wicket.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.

Social Sharing Optimization

11wicket.com

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