RE.IS Reykjavik Excursions, a leading organiser of coach and bus tours in Iceland


re.is website information.

re.is domain name is registered by .IS top-level domain registry. See the other sites registred in .IS domain zone.

No name server records were found.

and probably website re.is is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.

According to Alexa traffic rank the highest website re.is position was 37863 (in the world). The lowest Alexa rank position was 998455. Now website re.is ranked in Alexa database as number 157620 (in the world).

Website re.is Desktop speed measurement score (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.

re.is Mobile usability score (97/100) is better than the results of 49.9% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of re.is (69/100) is better than the results of 74.36% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-19-2024 157,620-1,469
May-18-2024 156,151-2,266
May-17-2024 153,885-1,544
May-16-2024 152,341-41
May-15-2024 152,300-2,436
May-14-2024 149,8644,924
May-13-2024 154,788-1,548

Advertisement

re.is Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



re.is whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


% This is the ISNIC Whois server.
%
% Rights restricted by copyright.
% See https://www.isnic.is/en/about/copyright

domain: re.is
registrant: REE25-IS
admin-c: REE4-IS
tech-c: SKY3-IS
zone-c: CN25-IS
billing-c: REE4-IS
nserver: may.ns.cloudflare.com
nserver: clay.ns.cloudflare.com
dnssec: unsigned delegation
created: November 20 1997
expires: November 20 2021
source: ISNIC

role: Ferdaskrifstofa Kynnisferda ehf.
nic-hdl: REE25-IS
address: Klettagordum 12
address: IS-104 Reykjavik
phone: +354 5805400
e-mail: webmaster@re.is
created: November 20 1997
source: ISNIC

role: Advania Island ehf.
nic-hdl: SKY3-IS
address: Gudrunartuni 10
address: IS-105 Reykjavik
phone: +354 4409000
e-mail: hostmaster@advania.is
created: September 17 1999
source: ISNIC

role: Ferdaskrifstofa Kynnisferda ehf.
nic-hdl: REE4-IS
address: Klettagordum 12
address: IS-104 Reykjavik
phone: +354 5805400
e-mail: webmaster@re.is
created: July 8 2010
source: ISNIC

role: CloudFlare NOC
nic-hdl: CN25-IS
address: 665 3rd Street, Suite 207
address: San Francisco, CA 94107
address: US
phone: +1 6503198930
e-mail: noc@cloudflare.com
created: January 19 2012
source: ISNIC

re.is server information

Servers Location

IP Address
Country
Region
City

re.is desktop page speed rank

Last tested: 2017-05-19


Desktop Speed Medium
80/100

re.is Desktop Speed Test Quick Summary


priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://use.typekit.net/jnx1rcv.js
https://www.re.is/skin/kynnisferdir/codecentre/jqreq.js
https://www.re.is/skin/kynnisferdir/main.js?v47

Optimize CSS Delivery of the following:

https://www.re.is/skin/kynnisferdir/main.css?v47

priority - 7 Reduce server response time

In our test, your server responded in 0.55 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 5 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://jokull.s3.amazonaws.com/photo13preview (expiration not specified)
https://jokull.s3.amazonaws.com/photo432large (expiration not specified)
https://jokull.s3.amazonaws.com/photo694preview (expiration not specified)
https://jokull.s3.amazonaws.com/photo7preview (expiration not specified)
https://secure.eplica.is/codecentre/jq/q-ajaxform.js (expiration not specified)
https://use.typekit.net/jnx1rcv.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-3DLP (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/605761196239049?v=2.7.9 (20 minutes)
https://www.google-analytics.com/plugins/ua/ecommerce.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 69% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 6.5KiB (15% reduction).

Compressing https://www.re.is/media/headers-video/NorthernLights-full.jpg could save 6.5KiB (15% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.2KiB (16% reduction).

Minifying https://www.re.is/ could save 1.2KiB (16% reduction) after compression.

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 631B (79% reduction).

Minifying https://connect.facebook.net/signals/config/605761196239049?v=2.7.9 could save 631B (79% reduction) after compression.

re.is Desktop Resources

Total Resources59
Number of Hosts15
Static Resources34
JavaScript Resources13
CSS Resources1

re.is Desktop Resource Breakdown

re.is mobile page speed rank

Last tested: 2017-05-19


Mobile Speed Medium
69/100

re.is Mobile Speed Test Quick Summary


priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://use.typekit.net/jnx1rcv.js
https://www.re.is/skin/kynnisferdir/codecentre/jqreq.js

Optimize CSS Delivery of the following:

https://www.re.is/skin/kynnisferdir/main.css?v47

priority - 7 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://jokull.s3.amazonaws.com/photo13preview (expiration not specified)
https://jokull.s3.amazonaws.com/photo432large (expiration not specified)
https://jokull.s3.amazonaws.com/photo7preview (expiration not specified)
https://secure.eplica.is/codecentre/jq/q-ajaxform.js (expiration not specified)
https://use.typekit.net/jnx1rcv.js (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-3DLP (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/605761196239049?v=2.7.9 (20 minutes)
https://www.google-analytics.com/plugins/ua/ecommerce.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 5 Reduce server response time

In our test, your server responded in 0.52 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.5KiB (20% reduction).

Compressing https://www.re.is/media/headers/demo-new-small.jpg could save 5.5KiB (20% reduction).

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 1.2KiB (16% reduction).

Minifying https://www.re.is/ could save 1.2KiB (16% reduction) after compression.

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 631B (79% reduction).

Minifying https://connect.facebook.net/signals/config/605761196239049?v=2.7.9 could save 631B (79% reduction) after compression.

re.is Mobile Resources

Total Resources59
Number of Hosts15
Static Resources34
JavaScript Resources13
CSS Resources1

re.is Mobile Resource Breakdown

re.is mobile page usability

Last tested: 2017-05-19


Mobile Usability Good
97/100

re.is Mobile Usability Test Quick Summary


priority - 2 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/search?q=gull…TextSearchForm">gullfoss</a> and 1 others are close to other tap targets.
The tap target <a href="/day-tours/">Day tours</a> and 20 others are close to other tap targets.

re.is similar domains

Similar domains:
www.re.com
www.re.net
www.re.org
www.re.info
www.re.biz
www.re.us
www.re.mobi
www.e.is
www.re.is
www.ee.is
www.ree.is
www.ere.is
www.de.is
www.rde.is
www.dre.is
www.fe.is
www.rfe.is
www.fre.is
www.te.is
www.rte.is
www.tre.is
www.r.is
www.rw.is
www.rew.is
www.rwe.is
www.rs.is
www.res.is
www.rse.is
www.rd.is
www.red.is
www.rr.is
www.rer.is
www.rre.is

re.is Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


re.is TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.