Tools & Wizards About Us
whatoplay.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

whatoplay.com

whatoplay • Discover your next favorite games

Page Load Speed

1.4 sec in total

First Response

154 ms

Resources Loaded

1.2 sec

Page Rendered

81 ms

whatoplay.com screenshot

About Website

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

Don’t know what to play? We track all new and upcoming video game releases, aggregate critic and player reviews, and highlight the best PC, console, and mobile games to play.

Visit whatoplay.com

Key Findings

We analyzed Whatoplay.com page load time and found that the first response time was 154 ms and then it took 1.3 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

whatoplay.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value3,210 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.706

7/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

whatoplay.com

154 ms

whatoplay.com

438 ms

ad-manager.min.js

82 ms

d09ffb68d2e3efb3.css

73 ms

e1b7f3a42db9eacf.css

142 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 96% of them (22 requests) were addressed to the original Whatoplay.com, 4% (1 request) were made to Hb.vntsm.com. The less responsive or slowest element that took the longest time to load (599 ms) belongs to the original domain Whatoplay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.8 kB (59%)

Content Size

176.0 kB

After Optimization

72.2 kB

  • HTML
  • JavaScript

In fact, the total size of Whatoplay.com main page is 176.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. 35% of websites need less resources to load. HTML takes 135.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 103.8 kB

  • Original 135.3 kB
  • After minification 135.3 kB
  • After compression 31.5 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 103.8 kB or 77% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 40.7 kB
  • After minification 40.7 kB
  • After compression 40.7 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 18 (86%)

Requests Now

21

After Optimization

3

  • JavaScript
  • CSS

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

Network Requests Diagram

whatoplay.com

whatoplay.com

154 ms

whatoplay.com

whatoplay.com

438 ms

ad-manager.min.js

ad-manager.min.js

82 ms

d09ffb68d2e3efb3.css

d09ffb68d2e3efb3.css

73 ms

e1b7f3a42db9eacf.css

e1b7f3a42db9eacf.css

142 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

269 ms

ae51ba48-260ef84082f2eee4.js

ae51ba48-260ef84082f2eee4.js

200 ms

5423ad26-39739ca4d3674952.js

5423ad26-39739ca4d3674952.js

285 ms

9027-b7b66f709e48a9f4.js

9027-b7b66f709e48a9f4.js

202 ms

2616-c5451916e2317307.js

2616-c5451916e2317307.js

285 ms

7434-521cc16315709f45.js

7434-521cc16315709f45.js

213 ms

1677-0827ce6d6a8f4936.js

1677-0827ce6d6a8f4936.js

283 ms

656-b368261f0b2b0104.js

656-b368261f0b2b0104.js

285 ms

3664-3b6d2bc34a794ec8.js

3664-3b6d2bc34a794ec8.js

286 ms

4798.6f112b2f45498699.js

4798.6f112b2f45498699.js

327 ms

webpack-73ddd9372a9f2d64.js

webpack-73ddd9372a9f2d64.js

330 ms

framework-fee8a7e75612eda8.js

framework-fee8a7e75612eda8.js

407 ms

main-4a5b78858d8844af.js

main-4a5b78858d8844af.js

407 ms

_app-a6af1b459d6c86dc.js

_app-a6af1b459d6c86dc.js

599 ms

9999-46243b29fce9febc.js

9999-46243b29fce9febc.js

353 ms

index-1e1f1b74646aeafd.js

index-1e1f1b74646aeafd.js

394 ms

_buildManifest.js

_buildManifest.js

396 ms

_ssgManifest.js

_ssgManifest.js

416 ms

Accessibility Review

whatoplay.com accessibility score

79

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

<frame> or <iframe> elements do not have a title

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

[id] attributes on active, focusable elements are not unique

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

whatoplay.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

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

whatoplay.com SEO score

99

Search Engine Optimization Advices

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 Whatoplay.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 Whatoplay.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

whatoplay.com

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