2.6 sec in total
382 ms
1.7 sec
523 ms
Click here to check amazing 11 Wickets content for India. Otherwise, check out these important facts you probably never knew about 11wickets.com
Fantasy cricket & fantasy football leagues only on 11wickets online fantasy cricket app. Make your dream team, play and win huge cash prizes.
Visit 11wickets.comWe analyzed 11wickets.com page load time and found that the first response time was 382 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
11wickets.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.8 s
15/100
25%
Value5.9 s
48/100
10%
Value800 ms
36/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
382 ms
413 ms
39 ms
161 ms
26 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 41% of them (14 requests) were addressed to the original 11wickets.com, 32% (11 requests) were made to Cdn.ampproject.org and 12% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (764 ms) belongs to the original domain 11wickets.com.
Page size can be reduced by 182.9 kB (12%)
1.6 MB
1.4 MB
In fact, the total size of 11wickets.com main page is 1.6 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 93.8 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.
Potential reduce by 53.7 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. 11 Wickets images are well optimized though.
Potential reduce by 35.4 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.4 kB or 14% of the original size.
Potential reduce by 0 B
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. 11wickets.com has all CSS files already compressed.
Number of requests can be reduced by 10 (40%)
25
15
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 11 Wickets. 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.
11wickets.com
382 ms
www.11wickets.com
413 ms
css2
39 ms
all.css
161 ms
v0.js
26 ms
amp-analytics-0.1.js
40 ms
amp-sidebar-0.1.js
49 ms
amp-carousel-0.2.js
50 ms
amp-youtube-0.1.js
50 ms
amp-accordion-0.1.js
61 ms
amp-bind-0.1.js
55 ms
amp-form-0.1.js
55 ms
amp-mustache-0.2.js
53 ms
amp-font-0.1.js
56 ms
amp-selector-0.1.js
56 ms
main-loyalty-banner.jpg
385 ms
main-slider-sports.jpg
439 ms
khel-banner.jpg
406 ms
playing-experience-bg.jpg
35 ms
our-fans-bg.jpg
396 ms
pratik-ghosh.jpg
27 ms
avinash-tiwari.jpg
34 ms
puja-nair.jpg
424 ms
how-to-play-bg.jpg
34 ms
most-trusted-bg.jpg
39 ms
exclusive-feature.jpg
439 ms
chat-icon.svg
764 ms
S6uyw4BMUTPHvxk.ttf
20 ms
S6u9w4BMUTPHh7USew8.ttf
24 ms
S6u9w4BMUTPHh6UVew8.ttf
46 ms
S6u9w4BMUTPHh50Xew8.ttf
47 ms
fa-solid-900.woff
85 ms
fa-regular-400.woff
113 ms
fa-brands-400.woff
156 ms
11wickets.com accessibility score
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
button, link, and menuitem elements do not have accessible names.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
11wickets.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
11wickets.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 11wickets.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 11wickets.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.
11wickets.com
Open Graph data is detected on the main page of 11 Wickets. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: