Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

rr.ee

Reisibüroo Tallinnas - Reisibüroo Rio Reisid

Page Load Speed

3.4 sec in total

First Response

322 ms

Resources Loaded

2.5 sec

Page Rendered

540 ms

rr.ee screenshot

About Website

Welcome to rr.ee homepage info - get ready to check Rr best content right away, or after learning these important things about rr.ee

Reisibüroo Tallinnas, Reisibüroo Rio Reisid

Visit rr.ee

Key Findings

We analyzed Rr.ee page load time and found that the first response time was 322 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

rr.ee performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

rr.ee

322 ms

rioreisid.ee

801 ms

jquery-ui.css

6 ms

styles.css

164 ms

slideshow.min.css

168 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rr.ee, 92% (67 requests) were made to Rioreisid.ee and 4% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (813 ms) relates to the external source Rioreisid.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.6 kB (9%)

Content Size

1.6 MB

After Optimization

1.5 MB

In fact, the total size of Rr.ee main page is 1.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 29.5 kB

  • Original 37.6 kB
  • After minification 34.5 kB
  • After compression 8.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 29.5 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 30.2 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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. Rr images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 62.4 kB

  • Original 92.8 kB
  • After minification 89.3 kB
  • After compression 30.4 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 62.4 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 31.5 kB

  • Original 38.0 kB
  • After minification 24.4 kB
  • After compression 6.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Rr.ee needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (30%)

Requests Now

71

After Optimization

50

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

rr.ee accessibility score

83

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

rr.ee 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

rr.ee SEO score

76

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

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rr.ee can be misinterpreted by Google and other search engines. Our service has detected that Estonian is used on the page, and it matches the claimed language. Our system also found out that Rr.ee 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

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