Tools & Wizards About Us
riga.en.cx screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

riga.en.cx

ENCOUNTER — Starptautiskais nakts ekstremālo spēļu tīkls

Page Load Speed

7.5 sec in total

First Response

974 ms

Resources Loaded

6.3 sec

Page Rendered

279 ms

riga.en.cx screenshot

About Website

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

Encounter - aktīvo pilsētas spēļu starptautiskais tīkls (nakts ekstremālās spēles, auto orientēšanās, kvesti, fotomedības, slapjie kari, fotoekstrīms, kešings, brainstrom, kvests, auto-kvests, geokeši...

Visit riga.en.cx

Key Findings

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

Performance Metrics

riga.en.cx performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

riga.en.cx

974 ms

mainstyles.css

309 ms

jquery.min.js

51 ms

consCommon.js

247 ms

consUi.js

248 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Riga.en.cx, 67% (29 requests) were made to Cdn.endata.cx and 9% (4 requests) were made to World.en.cx. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source En.nn.lv.

Page Optimization Overview & Recommendations

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

Content Size

472.4 kB

After Optimization

188.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Riga.en.cx main page is 472.4 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 277.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 53.1 kB

  • Original 65.6 kB
  • After minification 57.1 kB
  • After compression 12.5 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. This page needs HTML code to be minified as it can gain 8.5 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 53.1 kB or 81% of the original size.

Image Optimization

-21%

Potential reduce by 27.3 kB

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

JavaScript Optimization

-73%

Potential reduce by 203.3 kB

  • Original 277.4 kB
  • After minification 256.9 kB
  • After compression 74.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 203.3 kB or 73% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

riga.en.cx

riga.en.cx

974 ms

mainstyles.css

mainstyles.css

309 ms

jquery.min.js

jquery.min.js

51 ms

consCommon.js

consCommon.js

247 ms

consUi.js

consUi.js

248 ms

swfobject.js

swfobject.js

61 ms

EnPhotoUploader.js

EnPhotoUploader.js

168 ms

_tucker_func.js

_tucker_func.js

290 ms

awards_data.js

awards_data.js

375 ms

holidays_data.js

holidays_data.js

120 ms

description_data.js

description_data.js

60 ms

forum.js

forum.js

5220 ms

ok.gif

ok.gif

7 ms

cancel_lv.gif

cancel_lv.gif

118 ms

yes_lv.gif

yes_lv.gif

109 ms

no_lv.gif

no_lv.gif

116 ms

en_logo0s.png

en_logo0s.png

44 ms

awards.css

awards.css

198 ms

calendar.css

calendar.css

229 ms

left1.gif

left1.gif

5 ms

empty.gif

empty.gif

6 ms

955.jpg

955.jpg

278 ms

lv.gif

lv.gif

127 ms

ru.gif

ru.gif

41 ms

en.faq.gif

en.faq.gif

43 ms

type.0.gif

type.0.gif

46 ms

rr8.gif

rr8.gif

47 ms

own.gif

own.gif

50 ms

org.gif

org.gif

51 ms

0xNiY1bl.JPG

0xNiY1bl.JPG

251 ms

4KymSJE8.jpg

4KymSJE8.jpg

281 ms

login_ru.gif

login_ru.gif

211 ms

bottom_logo.jpg

bottom_logo.jpg

526 ms

menu.png

menu.png

8 ms

in2.gif

in2.gif

24 ms

green_lines.gif

green_lines.gif

25 ms

hr.gif

hr.gif

24 ms

en016.gif

en016.gif

4 ms

ga.js

ga.js

32 ms

__utm.gif

__utm.gif

23 ms

__utm.gif

__utm.gif

31 ms

line_counters.gif

line_counters.gif

13 ms

__utm.gif

__utm.gif

30 ms

Accessibility Review

riga.en.cx accessibility score

65

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

riga.en.cx best practices score

75

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

SEO Factors

riga.en.cx SEO score

90

Search Engine Optimization Advices

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

    LV

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Riga.en.cx can be misinterpreted by Google and other search engines. Our service has detected that Latvian/Lettish 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 Riga.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

riga.en.cx

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