3.7 sec in total
1.3 sec
2.1 sec
267 ms
Visit fun.en.cx now to see the best up-to-date Fun En content for Russia and also check out these interesting facts you probably never knew about fun.en.cx
Encounter сеть городских игр — приключенческие, творческие, интеллектуальные игры, которые проводятся в реальном мире, на улицах городов более чем в 20 странах мира — квест, cхватка, фотоигра, мозгово...
Visit fun.en.cxWe analyzed Fun.en.cx page load time and found that the first response time was 1.3 sec and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fun.en.cx performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.6 s
34/100
25%
Value5.6 s
53/100
10%
Value310 ms
78/100
30%
Value0
100/100
15%
Value6.6 s
58/100
10%
1334 ms
247 ms
33 ms
277 ms
280 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Fun.en.cx, 42% (23 requests) were made to Cdn.endata.cx and 33% (18 requests) were made to D1.endata.cx. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fun.en.cx.
Page size can be reduced by 216.8 kB (57%)
383.0 kB
166.2 kB
In fact, the total size of Fun.en.cx main page is 383.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. 30% of websites need less resources to load. Images take 172.4 kB which makes up the majority of the site volume.
Potential reduce by 64.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 64.8 kB or 83% of the original size.
Potential reduce by 62.0 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, Fun En needs image optimization as it can save up to 62.0 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 90.0 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 90.0 kB or 68% of the original size.
Number of requests can be reduced by 23 (43%)
54
31
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fun 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 7 to 1 for JavaScripts and as a result speed up the page load time.
fun.en.cx
1334 ms
mainstyles.css
247 ms
jquery.min.js
33 ms
consCommon.js
277 ms
consUi.js
280 ms
swfobject.js
42 ms
EnPhotoUploader.js
211 ms
ok.gif
15 ms
top-01.png
271 ms
cancel_ru.gif
93 ms
yes_ru.gif
191 ms
no_ru.gif
91 ms
en_logo0s.png
15 ms
left1.gif
191 ms
empty.gif
13 ms
movie.jpg
24 ms
en.faq.gif
194 ms
org.gif
193 ms
own.gif
248 ms
rr8.gif
94 ms
auth.gif
191 ms
rr6.gif
189 ms
GZ5AJSsA.JPG
366 ms
7JTQlmpR.jpg
281 ms
S3CC832N.JPG
285 ms
arrow_up.gif
345 ms
arrow_down.gif
341 ms
soc-tw.png
204 ms
soc-fb.png
193 ms
soc-vk.png
192 ms
t.ico.png
187 ms
v.ico.png
190 ms
f.ico.png
258 ms
%D0%97%D0%B0%D0%BA%D1%80%D1%8B%D1%82%D0%BE.png
290 ms
botton-2.png
296 ms
botton-1.png
306 ms
botton-3.png
312 ms
botton-4.png
447 ms
12-4.png
373 ms
arrow_stil.gif
400 ms
org-01.png
407 ms
org-02.png
414 ms
menu11.png
395 ms
in2.gif
234 ms
ProviderSupport.html
164 ms
green_lines.gif
174 ms
en016.gif
178 ms
fun.en.cx
245 ms
ga.js
70 ms
line_counters.gif
325 ms
left1.gif
353 ms
__utm.gif
12 ms
safe-standard.js
31 ms
offline-339564588.gif
8 ms
encounter
34 ms
fun.en.cx 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
Form elements do not have associated labels
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.
fun.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
fun.en.cx SEO score
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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fun.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 Fun.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.
fun.en.cx
Open Graph description is not detected on the main page of Fun 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: