4.5 sec in total
709 ms
3 sec
756 ms
Click here to check amazing Green En content for Russia. Otherwise, check out these important facts you probably never knew about green.en.cx
Encounter сеть городских игр — приключенческие, творческие, интеллектуальные игры, которые проводятся в реальном мире, на улицах городов более чем в 20 странах мира — квест, cхватка, фотоигра, мозгово...
Visit green.en.cxWe analyzed Green.en.cx page load time and found that the first response time was 709 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
green.en.cx performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value5.7 s
17/100
25%
Value7.6 s
25/100
10%
Value510 ms
57/100
30%
Value0.011
100/100
15%
Value7.2 s
50/100
10%
709 ms
727 ms
727 ms
726 ms
727 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Green.en.cx, 49% (37 requests) were made to D1.endata.cx and 37% (28 requests) were made to Cdn.endata.cx. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source D1.endata.cx.
Page size can be reduced by 43.0 kB (55%)
78.9 kB
35.8 kB
In fact, the total size of Green.en.cx main page is 78.9 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. 15% of websites need less resources to load. HTML takes 53.8 kB which makes up the majority of the site volume.
Potential reduce by 42.8 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 42.8 kB or 80% of the original size.
Potential reduce by 278 B
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.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Green En. According to our analytics all requests are already optimized.
green.en.cx
709 ms
mainstyles.css
727 ms
jquery-1.6.2.js
727 ms
consCommon.js
726 ms
consUi.js
727 ms
swfobject.js
76 ms
swfobject.js
68 ms
EnPhotoUploader.js
728 ms
uc_base.js
1172 ms
games_data.js
1430 ms
holidays_data.js
1422 ms
uc_script.js
229 ms
ok.gif
116 ms
cancel_ru.gif
114 ms
yes_ru.gif
114 ms
no_ru.gif
124 ms
en_logo0s.png
124 ms
left1.gif
124 ms
empty.gif
125 ms
movie.jpg
124 ms
en.faq.gif
124 ms
own.gif
124 ms
rr9.gif
124 ms
auth.gif
123 ms
rr8.gif
124 ms
Nsp2lLpO.jpg
124 ms
G7nSQ9St.JPG
123 ms
Pg4P9OKW.jpg
111 ms
t.ico.png
687 ms
v.ico.png
692 ms
f.ico.png
694 ms
sc_vk.png
708 ms
sc_t.png
801 ms
sc_jj.png
814 ms
vid_01.png
812 ms
msl_01.png
825 ms
tr_01.png
830 ms
b_en_01.png
849 ms
rg_01.png
926 ms
mn_01.png
937 ms
st_01.png
949 ms
new.gif
971 ms
fullstyles.css
895 ms
uc_base.js
373 ms
_tucker_func.js
241 ms
holidays_data.js
121 ms
games_data.js
115 ms
t.ico.png
113 ms
v.ico.png
106 ms
f.ico.png
104 ms
sc_vk.png
91 ms
sc_t.png
166 ms
vid_01.png
155 ms
sc_jj.png
154 ms
msl_01.png
143 ms
tr_01.png
139 ms
b_en_01.png
121 ms
rg_01.png
44 ms
mn_01.png
31 ms
st_01.png
19 ms
new.gif
108 ms
fullstyles.css
106 ms
ok.gif
126 ms
cancel_ru.gif
155 ms
yes_ru.gif
154 ms
no_ru.gif
154 ms
green_lines.gif
51 ms
en016.gif
75 ms
ga.js
78 ms
ok.gif
209 ms
cancel_ru.gif
209 ms
yes_ru.gif
215 ms
no_ru.gif
214 ms
green_lines.gif
214 ms
__utm.gif
55 ms
green.en.cx accessibility score
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
Links do not have a discernible name
green.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
green.en.cx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Green.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 Green.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.
green.en.cx
Open Graph description is not detected on the main page of Green 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: