Tools & Wizards About Us
38.en.cx screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

38.en.cx

Encounter - international network of active urban games

Page Load Speed

4.2 sec in total

First Response

417 ms

Resources Loaded

3.7 sec

Page Rendered

162 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 417 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 65% of websites can load faster.

Performance Metrics

38.en.cx performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.213

58/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

38.en.cx

417 ms

38.en.cx

807 ms

mainstyles.css

615 ms

jquery-1.6.2.js

888 ms

consCommon.js

653 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original 38.en.cx, 73% (33 requests) were made to Cdn.endata.cx and 13% (6 requests) were made to World.en.cx. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.endata.cx.

Page Optimization Overview & Recommendations

Page size can be reduced by 91.5 kB (36%)

Content Size

254.2 kB

After Optimization

162.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 38.en.cx main page is 254.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. 15% of websites need less resources to load. Images take 100.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 45.5 kB

  • Original 55.5 kB
  • After minification 50.4 kB
  • After compression 10.0 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 45.5 kB or 82% of the original size.

Image Optimization

-15%

Potential reduce by 14.7 kB

  • Original 100.4 kB
  • After minification 85.6 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, 38 En needs image optimization as it can save up to 14.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-32%

Potential reduce by 31.2 kB

  • Original 98.3 kB
  • After minification 98.3 kB
  • After compression 67.1 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 31.2 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (67%)

Requests Now

36

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 38 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.

Network Requests Diagram

38.en.cx

38.en.cx

417 ms

38.en.cx

38.en.cx

807 ms

mainstyles.css

mainstyles.css

615 ms

jquery-1.6.2.js

jquery-1.6.2.js

888 ms

consCommon.js

consCommon.js

653 ms

consUi.js

consUi.js

654 ms

swfobject.js

swfobject.js

21 ms

tooltip.js

tooltip.js

673 ms

EnPhotoUploader.js

EnPhotoUploader.js

677 ms

embed.js

embed.js

208 ms

js

js

60 ms

ok.gif

ok.gif

786 ms

cancel_en.gif

cancel_en.gif

889 ms

yes_en.gif

yes_en.gif

913 ms

no_en.gif

no_en.gif

921 ms

en_logo0s.png

en_logo0s.png

923 ms

moonf.jpg

moonf.jpg

549 ms

menu.png

menu.png

930 ms

left1.gif

left1.gif

964 ms

in2.gif

in2.gif

966 ms

empty.gif

empty.gif

1001 ms

1134.jpg

1134.jpg

1135 ms

en.gif

en.gif

1011 ms

ru.gif

ru.gif

1021 ms

green_lines.gif

green_lines.gif

1074 ms

en.faq.gif

en.faq.gif

1077 ms

hr.gif

hr.gif

1121 ms

rr11.gif

rr11.gif

1147 ms

rr10.gif

rr10.gif

1147 ms

org.gif

org.gif

1185 ms

own.gif

own.gif

1195 ms

rr9.gif

rr9.gif

1241 ms

XcspfFxN.jpg

XcspfFxN.jpg

1341 ms

L90xsYCR.JPG

L90xsYCR.JPG

1352 ms

UYGyllwH.jpg

UYGyllwH.jpg

1337 ms

own.gif

own.gif

626 ms

2rightarrow.png

2rightarrow.png

733 ms

calendar.aspx

calendar.aspx

262 ms

login_ru.gif

login_ru.gif

737 ms

en016.gif

en016.gif

1293 ms

line_counters.gif

line_counters.gif

1279 ms

moonf.jpg

moonf.jpg

871 ms

own.gif

own.gif

781 ms

2rightarrow.png

2rightarrow.png

683 ms

login_ru.gif

login_ru.gif

742 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

50

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

38.en.cx SEO score

46

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

High

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

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: