Tools & Wizards About Us
38.en.cx screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    50% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

38.en.cx

Encounter - international network of active urban games

Page Load Speed

3.1 sec in total

First Response

883 ms

Resources Loaded

2 sec

Page Rendered

164 ms

38.en.cx screenshot

About Website

Welcome to 38.en.cx homepage info - get ready to check 38 En best content for Russia right away, or after learning these important things about 38.en.cx

Encounter is an international network of active urban games. Night games, brainstorm, quest, photo, street wars, caching and more.

Visit 38.en.cx

Key Findings

We analyzed 38.en.cx page load time and found that the first response time was 883 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

38.en.cx performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value7.2 s

29/100

10%

TBT (Total Blocking Time)

Value1,440 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

38.en.cx

883 ms

mainstyles.css

600 ms

jquery-1.6.2.js

601 ms

consCommon.js

600 ms

consUi.js

600 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original 38.en.cx, 70% (28 requests) were made to Cdn.endata.cx and 15% (6 requests) were made to World.en.cx. The less responsive or slowest element that took the longest time to load (883 ms) belongs to the original domain 38.en.cx.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.2 kB (60%)

Content Size

75.6 kB

After Optimization

30.4 kB

  • HTML
  • JavaScript

In fact, the total size of 38.en.cx main page is 75.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. Only 10% of websites need less resources to load. HTML takes 48.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 38.8 kB

  • Original 48.2 kB
  • After minification 43.8 kB
  • After compression 9.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. 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 38.8 kB or 81% of the original size.

JavaScript Optimization

-23%

Potential reduce by 6.4 kB

  • Original 27.4 kB
  • After minification 27.4 kB
  • After compression 21.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 6.4 kB or 23% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

  • Images
  • JavaScript

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 38 En. According to our analytics all requests are already optimized.

Network Requests Diagram

38.en.cx

38.en.cx

883 ms

mainstyles.css

mainstyles.css

600 ms

jquery-1.6.2.js

jquery-1.6.2.js

601 ms

consCommon.js

consCommon.js

600 ms

consUi.js

consUi.js

600 ms

swfobject.js

swfobject.js

48 ms

tooltip.js

tooltip.js

601 ms

EnPhotoUploader.js

EnPhotoUploader.js

601 ms

embed.js

embed.js

157 ms

ok.gif

ok.gif

511 ms

cancel_en.gif

cancel_en.gif

511 ms

yes_en.gif

yes_en.gif

510 ms

no_en.gif

no_en.gif

510 ms

en_logo0s.png

en_logo0s.png

510 ms

left1.gif

left1.gif

509 ms

empty.gif

empty.gif

508 ms

277.jpg

277.jpg

509 ms

en.gif

en.gif

509 ms

ru.gif

ru.gif

508 ms

en.faq.gif

en.faq.gif

508 ms

rr11.gif

rr11.gif

508 ms

rr10.gif

rr10.gif

507 ms

org.gif

org.gif

508 ms

own.gif

own.gif

508 ms

rr9.gif

rr9.gif

507 ms

XcspfFxN.jpg

XcspfFxN.jpg

507 ms

myWTt8lw.JPG

myWTt8lw.JPG

507 ms

wsRHcSX6.jpg

wsRHcSX6.jpg

508 ms

2rightarrow.png

2rightarrow.png

503 ms

login_ru.gif

login_ru.gif

502 ms

green_lines.gif

green_lines.gif

439 ms

calendar.aspx

calendar.aspx

8 ms

en016.gif

en016.gif

406 ms

ga.js

ga.js

14 ms

line_counters.gif

line_counters.gif

400 ms

__utm.gif

__utm.gif

15 ms

moonf.jpg

moonf.jpg

30 ms

own.gif

own.gif

18 ms

login_ru.gif

login_ru.gif

12 ms

2rightarrow.png

2rightarrow.png

11 ms

Accessibility Review

38.en.cx accessibility score

61

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

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

High

<html> element does not have a [lang] attribute

Best Practices

38.en.cx best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

38.en.cx SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 38.en.cx 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 38.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.

Social Sharing Optimization

38.en.cx

Open Graph description is not detected on the main page of 38 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: