2.8 sec in total
107 ms
1.3 sec
1.3 sec
Welcome to criticalgameplay.com homepage info - get ready to check Critical Gameplay best content right away, or after learning these important things about criticalgameplay.com
15 year project in critical game design by Lindsay Grace. Implementing games that highlight social ludic bias.
Visit criticalgameplay.comWe analyzed Criticalgameplay.com page load time and found that the first response time was 107 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
criticalgameplay.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value12.3 s
0/100
25%
Value10.7 s
7/100
10%
Value2,030 ms
7/100
30%
Value0.007
100/100
15%
Value18.6 s
3/100
10%
107 ms
90 ms
120 ms
530 ms
430 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 57% of them (26 requests) were addressed to the original Criticalgameplay.com, 13% (6 requests) were made to Youtube.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (785 ms) belongs to the original domain Criticalgameplay.com.
Page size can be reduced by 314.7 kB (10%)
3.1 MB
2.8 MB
In fact, the total size of Criticalgameplay.com main page is 3.1 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. 65% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 27.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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 11% 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 27.5 kB or 78% of the original size.
Potential reduce by 160.2 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. Critical Gameplay images are well optimized though.
Potential reduce by 86.5 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 86.5 kB or 30% of the original size.
Potential reduce by 40.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. Criticalgameplay.com needs all CSS files to be minified and compressed as it can save up to 40.5 kB or 38% of the original size.
Number of requests can be reduced by 13 (33%)
39
26
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Critical Gameplay. 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 as a result speed up the page load time.
criticalgameplay.com
107 ms
main.css
90 ms
FapYAQ-fTIw
120 ms
n-F3_EUxln4
530 ms
4883135
430 ms
black_white_game.jpg
593 ms
Art_science_musuem_wide.jpg
584 ms
jquery.min.js
171 ms
jquery.poptrox.min.js
68 ms
jquery.scrolly.min.js
73 ms
jquery.scrollex.min.js
88 ms
browser.min.js
87 ms
breakpoints.min.js
101 ms
util.js
111 ms
main.js
120 ms
wait2.jpg
528 ms
Big_Huggin_large.jpg
528 ms
healer_arcade_2019.JPG
536 ms
simultaneity_screenshot_2.jpg
556 ms
Stolen_Kisses.jpg
528 ms
screen.png
558 ms
levity2a.jpg
581 ms
real_war_game.jpg
783 ms
charit_screeen.jpg
557 ms
bang_gp_1.jpg
782 ms
poo_game.jpg
785 ms
css
33 ms
fontawesome-all.min.css
529 ms
www-player.css
11 ms
www-embed-player.js
32 ms
base.js
55 ms
ad_status.js
263 ms
XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js
209 ms
embed.js
130 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
94 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
107 ms
Create
215 ms
Create
217 ms
api.js
195 ms
id
189 ms
overlay.png
172 ms
intro.jpg
172 ms
dark-arrow.svg
170 ms
two.png
171 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr3cOWxw.ttf
209 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr3cOWxw.ttf
209 ms
criticalgameplay.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
criticalgameplay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
criticalgameplay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Criticalgameplay.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Criticalgameplay.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.
criticalgameplay.com
Open Graph description is not detected on the main page of Critical Gameplay. 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: