Tools & Wizards About Us
play.11plays.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

play.11plays.com

New Fantasy Cricket App Download, Play Online Fantasy Sports App | 11Plays

Page Load Speed

1.2 sec in total

First Response

109 ms

Resources Loaded

902 ms

Page Rendered

198 ms

play.11plays.com screenshot

About Website

Click here to check amazing Play 11Plays content for India. Otherwise, check out these important facts you probably never knew about play.11plays.com

Download India's most exciting Fantasy Cricket Platform app similar to Dream a11 on Android and iOS. Get C ricket app to earn money. Login with 11Plays to create Fantasy Cricket teams.

Visit play.11plays.com

Key Findings

We analyzed Play.11plays.com page load time and found that the first response time was 109 ms and then it took 1.1 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

play.11plays.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

play.11plays.com

109 ms

js

44 ms

style.css

58 ms

scustom.css

79 ms

65.bffaadc2.chunk.css

152 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 50% of them (17 requests) were addressed to the original Play.11plays.com, 9% (3 requests) were made to Google-analytics.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (244 ms) belongs to the original domain Play.11plays.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.0 kB (11%)

Content Size

280.0 kB

After Optimization

250.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Play.11plays.com main page is 280.0 kB. 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 218.4 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 23.3 kB

  • Original 34.9 kB
  • After minification 34.9 kB
  • After compression 11.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. 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 23.3 kB or 67% of the original size.

Image Optimization

-3%

Potential reduce by 6.5 kB

  • Original 218.4 kB
  • After minification 211.9 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. Play 11Plays images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 197 B

  • Original 26.8 kB
  • After minification 26.8 kB
  • After compression 26.6 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.

Requests Breakdown

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

Requests Now

28

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

play.11plays.com

play.11plays.com

109 ms

js

js

44 ms

style.css

style.css

58 ms

scustom.css

scustom.css

79 ms

65.bffaadc2.chunk.css

65.bffaadc2.chunk.css

152 ms

main.64d0ead3.chunk.css

main.64d0ead3.chunk.css

160 ms

logo.png

logo.png

111 ms

65.286d9762.chunk.js

65.286d9762.chunk.js

158 ms

main.c1db1278.chunk.js

main.c1db1278.chunk.js

149 ms

analytics.js

analytics.js

43 ms

js

js

18 ms

collect

collect

113 ms

collect

collect

125 ms

0.60f7234e.chunk.js

0.60f7234e.chunk.js

124 ms

1.461d58d5.chunk.js

1.461d58d5.chunk.js

88 ms

2.3d9f32ba.chunk.js

2.3d9f32ba.chunk.js

92 ms

3.e63121f5.chunk.js

3.e63121f5.chunk.js

104 ms

9.69aaed95.chunk.css

9.69aaed95.chunk.css

79 ms

9.bd8c2a48.chunk.js

9.bd8c2a48.chunk.js

145 ms

side_bg.cf92ef6d.jpg

side_bg.cf92ef6d.jpg

244 ms

collect

collect

29 ms

collect

collect

22 ms

ga-audiences

ga-audiences

44 ms

ga-audiences

ga-audiences

38 ms

font-awesome.min.css

font-awesome.min.css

66 ms

sdk.js

sdk.js

26 ms

api.js

api.js

75 ms

logo.322f3333.png

logo.322f3333.png

98 ms

sdk.js

sdk.js

10 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

29 ms

fontawesome-webfont.fee66e71.woff

fontawesome-webfont.fee66e71.woff

114 ms

iframe

iframe

55 ms

cspreport

cspreport

47 ms

Accessibility Review

play.11plays.com accessibility score

81

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

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.

Best Practices

play.11plays.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

play.11plays.com SEO score

92

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 Play.11plays.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 Play.11plays.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

play.11plays.com

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