REDWEEK.COM The World's Largest Timeshare Marketplace | RedWeek

redweek.com Website Information

Daily Unique Visits: 15,797

Daily Page Views: 94,782

Income Per Day: $190

Estimated Value: $136,800

This website is located in United States and is using following IP address 216.211.130.141. See the complete list of popular websites hosted in United States.

redweek.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website redweek.com is using the following name servers:

  • ns-1468.awsdns-55.org
  • ns-1711.awsdns-21.co.uk
  • ns-259.awsdns-32.com
  • ns-574.awsdns-07.net

and is probably hosted by AS17378 - TIERPOINT PENNSYLVANIA TWO LLC, US. See the full list of other websites hosted by AS17378 - TIERPOINT PENNSYLVANIA TWO LLC, US.

The highest website redweek.com position in Alexa rank database was 83370 and the lowest rank position was 248979. Current position of redweek.com in Alexa rank database is 90793.

Desktop speed score of redweek.com (77/100) is better than the results of 63.93% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of redweek.com (91/100) is better than the results of 32.41% of other sites and means that the page is mobile-friendly.

Mobile speed score of redweek.com (71/100) is better than the results of 78.26% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

redweek.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


redweek.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: REDWEEK.COM
Registry Domain ID: 16338621_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2022-09-20T07:04:38Z
Creation Date: 1999-12-31T19:43:17Z
Registry Expiry Date: 2026-12-31T19:43:17Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS-1468.AWSDNS-55.ORG
Name Server: NS-1711.AWSDNS-21.CO.UK
Name Server: NS-259.AWSDNS-32.COM
Name Server: NS-574.AWSDNS-07.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-16T20:56:59Z

redweek.com server information

Servers Location

redweek.com desktop page speed rank

Last tested: 2019-12-15


Desktop Speed Medium
77/100

redweek.com Desktop Speed Test Quick Summary


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

Your page has 4 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Josefin+Sa…0,500,700&display=swap
https://stackpath.bootstrapcdn.com/font-awesome/4.…s/font-awesome.min.css
https://cdn1.redweek.com/css/redweek-styles.css?a_EZU-GYz6FkzjP8hBh7qA
https://cdn1.redweek.com/css/rw-page-home.css?bOSJ4J6bQ8BIqDX6pwYW7g

priority - 9Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://redweek.com/
https://redweek.com/
https://www.redweek.com/

priority - 6Leverage 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://tracker.affirm.com/collect (expiration not specified)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/633873…7066?v=2.9.15&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://cdn1.affirm.com/js/v2/affirm.js (30 minutes)
https://widget.trustpilot.com/trustbox-data/53aa89…PerPage=15&theme=light (30 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://s.yimg.com/wi/config/412866.json (60 minutes)
https://s.yimg.com/wi/ytc.js (60 minutes)
https://www.affirm.com/api/v2/cookie_sent (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2Reduce server response time

In our test, your server responded in 0.41 seconds.

priority - 0Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 1.5KiB (57% reduction).

Compressing https://polyfills.trustpilot.com/v2/polyfill.min.j…ncludes%2CNumber.isNaN could save 1.5KiB (57% reduction).

priority - 0Optimize images

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

Optimize the following images to reduce their size by 274B (25% reduction).

Compressing https://cdn1.redweek.com/img/structure/footer.soci…fX_TeVZ-vJfWcXQrdzetjQ could save 274B (25% reduction).

redweek.com Desktop Resource Breakdown

Total Resources91
Number of Hosts35
Static Resources40
JavaScript Resources37
CSS Resources5

redweek.com mobile page speed rank

Last tested: 2016-10-12


Mobile Speed Medium
71/100

redweek.com Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js

Optimize CSS Delivery of the following:

http://fonts.googleapis.com/css?family=Roboto:400,400italic,300,500,700
http://cdn.redweek.com/css/redweek-styles.css?vRW7svevw6sqPwtz0ur2CA
http://cdn.redweek.com/css/rw-page-home.css?vNQhWmC5NsL59ieiEHfhbg

priority - 8Leverage 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:

http://bat.bing.com/bat.js (expiration not specified)
https://s.yimg.com/wi/ytc.js (expiration not specified)
http://static.hotjar.com/c/hotjar-53859.js?sv=5 (60 seconds)
http://a.adroll.com/j/roundtrip.js (5 minutes)
https://s.adroll.com/pixel/KRK7VGJPOVDNNEJGLS43YD/…AXHVVJ5CNFBSFTUPXHJ.js (5 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 0Minify 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 3.6KiB (28% reduction).

Minifying http://cdn.redweek.com/ext-lib/js/js-webshim/polyf…ZS3zG7lBC6_XE4LOrCHPWw could save 2.1KiB (21% reduction) after compression.
Minifying http://cdn.redweek.com/ext-lib/js/ie8/rem.js?Yltn8K0Xpk-ffmxMmzaJ4Q could save 1.5KiB (50% reduction) after compression.

redweek.com Mobile Resource Breakdown

Total Resources121
Number of Hosts36
Static Resources67
JavaScript Resources31
CSS Resources5

redweek.com mobile page usability

Last tested: 2016-10-12


Mobile Usability Good
91/100

redweek.com Mobile Usability Test Quick Summary


priority - 5Size 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="/browse/timeshares/">location</a> and 1 others are close to other tap targets.
The tap target <a href="http://www.red…ruba-surf-club">Aruba Surf Club</a> and 27 others are close to other tap targets.

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 415 CSS pixels wide, but the viewport is only 411 CSS pixels wide. The following elements fall outside the viewport:

The element <div class="search-container">Search Search…Browse all »</div> falls outside the viewport.

redweek.com HTML validation

Errors

Duplicate ID “menu-sign-in”.

Line: 150 Column: 1 - 70
"...r_login"> <a href="https://www.redweek.com/signin?target=%2F" id="menu-sign-in">Sign I..."

Duplicate ID “find-a-timeshare”.

Line: 194 Column: 1 - 81
"...ropdown"> <a href="/browse/timeshares" class="toggle-timeshare-menu" id="find-a-timeshare">Find a..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 225 Column: 1 - 94
"...o--left"> <img src="https://cdn2.redweek.com/img/heroes/home/testimonial-05.jpg?xgdC2MyG0GN8EdNyfhiRdg"> ..." Line: 342 Column: 5 - 174
"...</dt> <dd><img data-original="https://cdn2.redweek.com/img/media/redbook.png?56P_uLy8_lxSzLrRq2gqQA" src="https://cdn2.redweek.com/img/1x1.gif?PqzQEyMQ6kTK11azeKO8Bw" class="lazy"></dd> ..." Line: 343 Column: 5 - 174
"...</dd> <dd><img data-original="https://cdn2.redweek.com/img/media/latimes.png?4EVWxsLjZTQX490nZMF-0w" src="https://cdn2.redweek.com/img/1x1.gif?PqzQEyMQ6kTK11azeKO8Bw" class="lazy"></dd> ..." Line: 344 Column: 5 - 171
"...</dd> <dd><img data-original="https://cdn2.redweek.com/img/media/aarp.png?Edp63yVeMgRNbYldfcKRWw" src="https://cdn2.redweek.com/img/1x1.gif?PqzQEyMQ6kTK11azeKO8Bw" class="lazy"></dd> ..." Line: 345 Column: 5 - 176
"...</dd> <dd><img data-original="https://cdn1.redweek.com/img/media/kiplinger.png?u-WI8KZ6UbP1YahbTe90MQ" src="https://cdn2.redweek.com/img/1x1.gif?PqzQEyMQ6kTK11azeKO8Bw" class="lazy"></dd> ..." Line: 346 Column: 5 - 171
"...</dd> <dd><img data-original="https://cdn2.redweek.com/img/media/self.png?VE_SgTFtBRusSm3TSyZwVw" src="https://cdn2.redweek.com/img/1x1.gif?PqzQEyMQ6kTK11azeKO8Bw" class="lazy"></dd> ..."

The text content of element “time” was not in the required format: The literal did not satisfy the time-datetime format.

Line: 231 Column: 55 - 61
"...since 2014</time> </div..."

Element “figcaption” not allowed as child of element “a” in this context. (Suppressing further errors from this subtree.)

Line: 389 Column: 244 - 277
"... <figcaption class="image-caption">Harbor..." Line: 410 Column: 218 - 251
"... <figcaption class="image-caption">Hawaii..."

Warnings

The first occurrence of ID “menu-sign-in” was here.

Line: 137 Column: 1 - 70
"...r_login"> <a href="https://www.redweek.com/signin?target=%2F" id="menu-sign-in">Sign I..."

The first occurrence of ID “find-a-timeshare” was here.

Line: 169 Column: 1 - 81
"...ropdown"> <a href="/browse/timeshares" class="toggle-timeshare-menu" id="find-a-timeshare">Find a..."

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

Line: 263 Column: 57 - 69
"...ll-large"><h1 id="top">The Wo..."

redweek.com similar domains

Similar domains:
www.redweek.com
www.redweek.net
www.redweek.org
www.redweek.info
www.redweek.biz
www.redweek.us
www.redweek.mobi
www.edweek.com
www.redweek.com
www.eedweek.com
www.reedweek.com
www.eredweek.com
www.dedweek.com
www.rdedweek.com
www.dredweek.com
www.fedweek.com
www.rfedweek.com
www.fredweek.com
www.tedweek.com
www.rtedweek.com
www.tredweek.com
www.rdweek.com
www.rwdweek.com
www.rewdweek.com
www.rwedweek.com
www.rsdweek.com
www.resdweek.com
www.rsedweek.com
www.rddweek.com
www.reddweek.com
www.rrdweek.com
www.rerdweek.com
www.rredweek.com
www.reweek.com
www.rexweek.com
www.redxweek.com
www.rexdweek.com
www.resweek.com
www.redsweek.com
www.reeweek.com
www.redeweek.com
www.rerweek.com
www.redrweek.com
www.refweek.com
www.redfweek.com
www.refdweek.com
www.recweek.com
www.redcweek.com
www.recdweek.com
www.redeek.com
www.redqeek.com
www.redwqeek.com
www.redqweek.com
www.redaeek.com
www.redwaeek.com
www.redaweek.com
www.redseek.com
www.redwseek.com
www.redeeek.com
www.redweeek.com
www.redwek.com
www.redwwek.com
www.redwewek.com
www.redwweek.com
www.redwsek.com
www.redwesek.com
www.redwdek.com
www.redwedek.com
www.redwdeek.com
www.redwrek.com
www.redwerek.com
www.redwreek.com
www.redwewk.com
www.redweewk.com
www.redwesk.com
www.redweesk.com
www.redwedk.com
www.redweedk.com
www.redwerk.com
www.redweerk.com
www.redwee.com
www.redweej.com
www.redweekj.com
www.redweejk.com
www.redweei.com
www.redweeki.com
www.redweeik.com
www.redweem.com
www.redweekm.com
www.redweemk.com
www.redweel.com
www.redweekl.com
www.redweelk.com
www.redweeo.com
www.redweeko.com
www.redweeok.com
www.redweek.con

redweek.com Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


redweek.com TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.