Tools & Wizards About Us
48.en.cx screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

48.en.cx

Encounter - international network of active urban games

Page Load Speed

4.8 sec in total

First Response

419 ms

Resources Loaded

4.3 sec

Page Rendered

113 ms

48.en.cx screenshot

About Website

Click here to check amazing 48 En content for Russia. Otherwise, check out these important facts you probably never knew about 48.en.cx

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

Visit 48.en.cx

Key Findings

We analyzed 48.en.cx page load time and found that the first response time was 419 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

48.en.cx performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

34/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

48.en.cx

419 ms

48.en.cx

1026 ms

mainstyles.css

653 ms

jquery-1.6.2.js

924 ms

consCommon.js

680 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original 48.en.cx, 43% (20 requests) were made to Cdn.endata.cx and 17% (8 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 183.3 kB (34%)

Content Size

534.1 kB

After Optimization

350.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 48.en.cx main page is 534.1 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. 20% of websites need less resources to load. Javascripts take 186.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 135.6 kB

  • Original 167.5 kB
  • After minification 161.9 kB
  • After compression 31.9 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 135.6 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 15.2 kB

  • Original 179.8 kB
  • After minification 164.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. 48 En images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 32.6 kB

  • Original 186.8 kB
  • After minification 186.3 kB
  • After compression 154.2 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.6 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (59%)

Requests Now

39

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 48 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

48.en.cx

48.en.cx

419 ms

48.en.cx

48.en.cx

1026 ms

mainstyles.css

mainstyles.css

653 ms

jquery-1.6.2.js

jquery-1.6.2.js

924 ms

consCommon.js

consCommon.js

680 ms

consUi.js

consUi.js

680 ms

swfobject.js

swfobject.js

24 ms

tooltip.js

tooltip.js

705 ms

EnPhotoUploader.js

EnPhotoUploader.js

708 ms

es5-shims.min.js

es5-shims.min.js

184 ms

share.js

share.js

436 ms

jquery.cookie.js

jquery.cookie.js

425 ms

js

js

68 ms

telegram.js

telegram.js

673 ms

jquery.cookie.js

jquery.cookie.js

351 ms

telegram.js

telegram.js

557 ms

ok.gif

ok.gif

765 ms

cancel_en.gif

cancel_en.gif

891 ms

yes_en.gif

yes_en.gif

1018 ms

no_en.gif

no_en.gif

1128 ms

en_logo0s.png

en_logo0s.png

1109 ms

shapka4.jpg

shapka4.jpg

139 ms

shapka_mobile_2.jpg

shapka_mobile_2.jpg

279 ms

left1.gif

left1.gif

1077 ms

empty.gif

empty.gif

1106 ms

694.jpg

694.jpg

1295 ms

en.gif

en.gif

1192 ms

ru.gif

ru.gif

1193 ms

green_lines.gif

green_lines.gif

1198 ms

en.faq.gif

en.faq.gif

1232 ms

own.gif

own.gif

1264 ms

rr8.gif

rr8.gif

1307 ms

PC5HF6HN.JPG

PC5HF6HN.JPG

1394 ms

bGEZGv4H.JPG

bGEZGv4H.JPG

1417 ms

LzxZ0FUE.JPG

LzxZ0FUE.JPG

1424 ms

en016.gif

en016.gif

1403 ms

iconfinder_navigation-up-button_green_68972.png

iconfinder_navigation-up-button_green_68972.png

266 ms

3_0_868686FF_666666FF_1_uniques

3_0_868686FF_666666FF_1_uniques

640 ms

tag.js

tag.js

829 ms

shapka4.jpg

shapka4.jpg

542 ms

line_counters.gif

line_counters.gif

1210 ms

menu.png

menu.png

1160 ms

shapka_mobile_2.jpg

shapka_mobile_2.jpg

593 ms

iconfinder_navigation-up-button_green_68972.png

iconfinder_navigation-up-button_green_68972.png

686 ms

advert.gif

advert.gif

726 ms

sync_cookie_image_decide

sync_cookie_image_decide

149 ms

Accessibility Review

48.en.cx accessibility score

75

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

48.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

48.en.cx SEO score

64

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 48.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 48.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

48.en.cx

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