8.3 sec in total
1.9 sec
6.2 sec
220 ms
Click here to check amazing Eyeplay content for United States. Otherwise, check out these important facts you probably never knew about eyeplay.info
Award-winning interactive projector games, floor projection games, floor games, and wall games. Contact us to turn any space into a virtual playground!
Visit eyeplay.infoWe analyzed Eyeplay.info page load time and found that the first response time was 1.9 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eyeplay.info performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value9.3 s
1/100
25%
Value8.6 s
17/100
10%
Value1,460 ms
15/100
30%
Value0.144
78/100
15%
Value14.4 s
9/100
10%
1888 ms
7 ms
221 ms
210 ms
170 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 42% of them (37 requests) were addressed to the original Eyeplay.info, 11% (10 requests) were made to D.adroll.com and 9% (8 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Eyeplay.info.
Page size can be reduced by 496.6 kB (60%)
827.6 kB
331.1 kB
In fact, the total size of Eyeplay.info main page is 827.6 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. 50% of websites need less resources to load. Javascripts take 512.6 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.6 kB or 76% of the original size.
Potential reduce by 2 B
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. Eyeplay images are well optimized though.
Potential reduce by 377.3 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 377.3 kB or 74% of the original size.
Potential reduce by 97.6 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. Eyeplay.info needs all CSS files to be minified and compressed as it can save up to 97.6 kB or 85% of the original size.
Number of requests can be reduced by 62 (83%)
75
13
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyeplay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
redirect-newsite
1888 ms
jquery.min.js
7 ms
styles.css
221 ms
widgets.css
210 ms
style.css
170 ms
testimonial.css
203 ms
prototype.js
388 ms
ccard.js
237 ms
validation.js
268 ms
builder.js
298 ms
effects.js
351 ms
dragdrop.js
330 ms
controls.js
419 ms
slider.js
357 ms
js.js
513 ms
form.js
989 ms
menu.js
1122 ms
translate.js
1034 ms
cookies.js
888 ms
eyeplay.js
791 ms
preloadCssImages.jQuery_v5.js
624 ms
widgets.js
82 ms
gtm.js
46 ms
bg-snap-to-left.png
428 ms
bg-snap-to-right.png
549 ms
logo-ep.png
671 ms
icon-fb.png
320 ms
icon-twtr.png
365 ms
icon-in.png
319 ms
icon-ytube.png
405 ms
eyeplay-logo-footer.png
899 ms
icon-in-hover.png
451 ms
icon-ytube-hover.png
474 ms
icon-fb-hover.png
503 ms
icon-twtr-hover.png
518 ms
btn-readmore-over.png
542 ms
GothamRnd-Light.woff
558 ms
GothamRnd-Medium.woff
642 ms
all.js
275 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
138 ms
GothamRnd-Bold.woff
632 ms
analytics.js
6 ms
roundtrip.js
19 ms
fbds.js
304 ms
oct.js
37 ms
468424.js
64 ms
collect
23 ms
collect
87 ms
adsct
118 ms
adsct
60 ms
UO5HMSB2WRFDFAX5FH2M66.js
346 ms
tweet_button.64a917b4a230f163048902c783e1530f.en.html
41 ms
163 ms
xd_arbiter.php
211 ms
xd_arbiter.php
418 ms
jot
75 ms
84 ms
85 ms
fbevents.hashing.js
68 ms
out
9 ms
24 ms
out
6 ms
out
8 ms
out
9 ms
out
11 ms
out
14 ms
out
13 ms
out
15 ms
out
15 ms
u.php
116 ms
adsct
33 ms
pixel
32 ms
25 ms
sync
7 ms
tap.php
6 ms
377928.gif
6 ms
pixel
13 ms
in
3 ms
sd
23 ms
20 ms
print.css
116 ms
pd.js
22 ms
__ptq.gif
18 ms
20 ms
20 ms
like.php
127 ms
-t4cwofxmC9.js
483 ms
FEppCFCt76d.png
548 ms
eyeplay.info 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
eyeplay.info 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
eyeplay.info SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyeplay.info 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 Eyeplay.info 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.
eyeplay.info
Open Graph description is not detected on the main page of Eyeplay. 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: