3.9 sec in total
358 ms
3.4 sec
180 ms
Welcome to 66.en.cx homepage info - get ready to check 66 En best content for Russia right away, or after learning these important things about 66.en.cx
Encounter сеть городских игр — приключенческие, творческие, интеллектуальные игры, которые проводятся в реальном мире, на улицах городов более чем в 20 странах мира — квест, cхватка, фотоигра, мозгово...
Visit 66.en.cxWe analyzed 66.en.cx page load time and found that the first response time was 358 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
66.en.cx performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.5 s
38/100
25%
Value7.2 s
30/100
10%
Value2,490 ms
4/100
30%
Value0.018
100/100
15%
Value15.1 s
7/100
10%
358 ms
870 ms
480 ms
740 ms
508 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 66.en.cx, 37% (23 requests) were made to Cdn.endata.cx and 13% (8 requests) were made to D1.endata.cx. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.endata.cx.
Page size can be reduced by 144.2 kB (28%)
511.2 kB
366.9 kB
In fact, the total size of 66.en.cx main page is 511.2 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. 30% of websites need less resources to load. Javascripts take 279.8 kB which makes up the majority of the site volume.
Potential reduce by 81.4 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 12.1 kB, which is 12% 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 81.4 kB or 84% of the original size.
Potential reduce by 29.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. Obviously, 66 En needs image optimization as it can save up to 29.9 kB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.9 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 32.9 kB or 12% 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. 66.en.cx has all CSS files already compressed.
Number of requests can be reduced by 30 (57%)
53
23
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 66 En. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
66.en.cx
358 ms
66.en.cx
870 ms
mainstyles.css
480 ms
jquery-1.6.2.js
740 ms
consCommon.js
508 ms
consUi.js
512 ms
swfobject.js
18 ms
EnPhotoUploader.js
526 ms
js
62 ms
share.js
357 ms
ok.gif
819 ms
cancel_ru.gif
931 ms
yes_ru.gif
939 ms
no_ru.gif
932 ms
en_logo1s.png
933 ms
watch.js
1 ms
66.png
432 ms
left1.gif
931 ms
empty.gif
945 ms
movie.jpg
1040 ms
en.faq.gif
1045 ms
type.0.gif
1045 ms
rr12.gif
1046 ms
xkj5dDRA.jpg
1207 ms
VM8i9nKd.png
1204 ms
9lQ74wEO.JPG
1206 ms
login_ru.gif
432 ms
t.ico.png
814 ms
v.ico.png
945 ms
f.ico.png
1073 ms
ikon_4.gif
560 ms
rtrg
815 ms
menu.png
1158 ms
in2.gif
1147 ms
kG8YFgYktdA
137 ms
green_lines.gif
1135 ms
hr.gif
1251 ms
hit
379 ms
en016.gif
1222 ms
www-player.css
12 ms
www-embed-player.js
44 ms
base.js
92 ms
ga.js
68 ms
empty.gif
1055 ms
__utm.gif
189 ms
ad_status.js
182 ms
66.png
823 ms
hit
768 ms
login_ru.gif
897 ms
4FCBsbVWt5jZVKm36Bs_QtpgBkunTUSSklJnPgMburg.js
128 ms
embed.js
58 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
52 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
60 ms
ikon_4.gif
561 ms
Create
105 ms
id
96 ms
quest66.png
311 ms
66encx
588 ms
GenerateIT
14 ms
share.d5b30abe919b24183022bcd01d19328c.js
115 ms
line_counters.gif
235 ms
widgets_logo_letters.svg
115 ms
__utm.gif
4 ms
66.en.cx accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
66.en.cx 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
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
Issues were logged in the Issues panel in Chrome Devtools
66.en.cx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 66.en.cx can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 66.en.cx 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.
66.en.cx
Open Graph description is not detected on the main page of 66 En. 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: