3.4 sec in total
322 ms
2.5 sec
540 ms
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.eeWe 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.
rr.ee performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value8.6 s
1/100
25%
Value8.4 s
18/100
10%
Value210 ms
88/100
30%
Value0.001
100/100
15%
Value9.9 s
27/100
10%
322 ms
801 ms
6 ms
164 ms
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 size can be reduced by 153.6 kB (9%)
1.6 MB
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.
Potential reduce by 29.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. 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.
Potential reduce by 30.2 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. Rr images are well optimized though.
Potential reduce by 62.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.
Potential reduce by 31.5 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.
Number of requests can be reduced by 21 (30%)
71
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.
rr.ee
322 ms
rioreisid.ee
801 ms
jquery-ui.css
6 ms
styles.css
164 ms
slideshow.min.css
168 ms
wppie.css
169 ms
normalize.css
172 ms
style.css
250 ms
jquery.min.js
7 ms
conditionizr.min.js
7 ms
modernizr.min.js
9 ms
scripts.js
172 ms
slideshow.min.js
243 ms
jquery.ui.core.min.js
172 ms
jquery.ui.datepicker.min.js
338 ms
jquery.form.min.js
253 ms
scripts.js
254 ms
bg.jpg
667 ms
bg2.png
334 ms
bg2-footer.png
86 ms
bg-footer.png
89 ms
rioreisid-logo.png
167 ms
lang-et.png
168 ms
lang-ru.png
170 ms
bg-buttons-header.png
190 ms
banner-04.jpg
417 ms
banner-05.jpg
501 ms
banner-02.jpg
417 ms
banner-03.jpg
355 ms
banner-01_ee.jpg
497 ms
loading.gif
439 ms
slideshow_icon_inactive.png
499 ms
mask-image-main.png
585 ms
box-header.png
520 ms
bg-box-hot.png
580 ms
partner-novatours.jpg
581 ms
Reisiraha_sinisel%20taustal%20RGB.jpg
582 ms
Aurinko%20logo.jpg
604 ms
Mouzenidis.png
668 ms
GoAdventure%20uus%20logo.jpg
664 ms
Tez%20rahvusvaheline%20logo_ee%20small.jpg
668 ms
logo%20bta.gif
671 ms
partner-salva-kindlustus.png
686 ms
webdesign.png
745 ms
bg-sidebar.png
746 ms
bg-input.png
748 ms
button-1.et_.png
748 ms
button-3.et_.png
750 ms
button-2.et_.png
768 ms
buttons-social.png
812 ms
bg-button-ok.png
811 ms
Salva_logo_trans.png
813 ms
Maria%20Rosi_JPG.jpg
751 ms
about_vivasan_logo.png
752 ms
ui-bg_flat_75_ffffff_40x100.png
4 ms
hots
766 ms
countries
793 ms
hoteltypes
799 ms
viru-varietee.jpg
747 ms
zig-zag.jpg
727 ms
flowers-250x162.jpg
586 ms
bg-button.png
627 ms
rannee-bronirovanie-1-250x194.jpg
582 ms
300x145-250x120.jpg
584 ms
pic-250x156.jpg
563 ms
red-sea-250x200.jpg
543 ms
tenerife.jpg
542 ms
halkidiki-1.jpg
558 ms
Santorini.jpg
643 ms
delfin.jpg
502 ms
Lanzarote.jpg
501 ms
bg-footer2.png
541 ms
slideshow_icon_active.png
541 ms
rr.ee accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
rr.ee best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
rr.ee SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ET
ET
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.
rr.ee
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: