WUND.COM Weather Forecast & Reports - Long Range & Local | Wunderground | Weather Underground


wund.com website information.

wund.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for wund.com domain:

  • a10-65.akam.net
  • a13-67.akam.net
  • a14-64.akam.net
  • a11-66.akam.net

According to Alexa traffic rank the highest website wund.com position was 68341 (in the world). The lowest Alexa rank position was 999979. Current position of wund.com in Alexa rank database is below 1 million.

Website wund.com Desktop speed measurement score (64/100) is better than the results of 41.34% of other sites shows that the page desktop performance can be improved.

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

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

Weekly Rank Report

DateRankChange
Sep-26-2021 N/AN/A
Sep-25-2021 N/AN/A
Sep-24-2021 N/AN/A
Sep-23-2021 N/AN/A
Sep-22-2021 N/AN/A
Sep-21-2021 N/AN/A
Sep-20-2021 N/AN/A

Advertisement

wund.com 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.



wund.com 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.


Domain Name: WUND.COM
Registry Domain ID: 79921032_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: http://cscdbs.com
Updated Date: 2020-11-14T07:08:12Z
Creation Date: 2001-11-18T20:01:31Z
Registry Expiry Date: 2021-11-18T20:01:31Z
Registrar: CSC Corporate Domains, Inc.
Registrar IANA ID: 299
Registrar Abuse Contact Email: domainabuse@cscglobal.com
Registrar Abuse Contact Phone: 8887802723
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: A1-70.AKAM.NET
Name Server: A10-65.AKAM.NET
Name Server: A11-66.AKAM.NET
Name Server: A13-67.AKAM.NET
Name Server: A14-64.AKAM.NET
Name Server: A24-65.AKAM.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-05-14T11:18:31Z

wund.com server information

Servers Location

IP Address
23.60.74.115
Region
Washington
City
Seattle

wund.com desktop page speed rank

Last tested: 2017-05-02


Desktop Speed Bad
64/100

wund.com Desktop Speed Test Quick Summary


priority - 27 Optimize images

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

Optimize the following images to reduce their size by 259.1KiB (60% reduction).

Compressing https://icons.wxug.com/i/homepage/device-pws.jpg could save 104.5KiB (78% reduction).
Compressing https://icons.wxug.com/i/homepage/device-hero-dark.jpg could save 93KiB (57% reduction).
Compressing https://icons.wxug.com/i/homepage/device-guide.jpg could save 26.1KiB (50% reduction).
Compressing https://tpc.googlesyndication.com/simgad/13018889541763442089 could save 18.6KiB (50% reduction).
Compressing https://s3.amazonaws.com/creatives2/Pringles.jpg could save 14.4KiB (49% reduction).
Compressing https://icons.wxug.com/i/o/sprite-common-vert.png?v=1.21 could save 2.4KiB (21% reduction).

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

Your page has 3 blocking script resources and 3 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://icons.wxug.com/scripts/modernizr/2.8.2/modernizr.min.js
https://icons.wxug.com/scripts/wui-whyads/advert.js?0.0.3
https://tags.crwdcntrl.net/c/2216/cc.js?ns=_cc2216

Optimize CSS Delivery of the following:

https://icons.wxug.com/css/wu4/core.css?v=2017041301
https://icons.wxug.com/css/wu4/omnibus.css?v=2017041901
https://icons.wxug.com/css/wu4/homepage.css?v=2017041301

priority - 12 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://icons.wxug.com/i/homepage/device-guide.jpg (expiration not specified)
https://icons.wxug.com/i/homepage/device-hero-dark.jpg (expiration not specified)
https://icons.wxug.com/i/homepage/device-pws.jpg (expiration not specified)
https://s3.amazonaws.com/creatives2/Pringles.jpg (expiration not specified)
https://secure-us.imrworldwide.com/v60.js (expiration not specified)
https://atemda.com/UserMatch.ashx?bidderid=12&bidderuid=8165578255005985204 (1 second)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback94102199999 (41 seconds)
https://api-ak-aws.wunderground.com/api/eb7a37c339…esCallback000004003779 (2.2 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback60290199999 (2.5 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback77001199999 (2.8 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback02108199999 (3.2 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…esCallback100011199999 (3.9 minutes)
https://api-ak-aws.wunderground.com/api/8dee7a0127….0/q/KJRB.json?ttl=300 (4.9 minutes)
https://api-ak-aws.wunderground.com/api/8dee7a0127…73.949600.json?ttl=300 (5 minutes)
https://tags.tiqcdn.com/utag/weather/wunderground/prod/utag.js (5 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/sdk.js (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=we…42150&cb=1493716769243 (30 minutes)
https://js-sec.indexww.com/ht/ls-wunderground.js (32 minutes)
https://mathid.mathtag.com/device/id.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://z.moatads.com/weatherv36943544254/moatad.js (11.7 hours)

priority - 2 Enable 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 22.1KiB (54% reduction).

Compressing https://cdn.issigpen.com/cmpp/cst.min.js could save 10.8KiB (64% reduction).
Compressing https://fastlane.rubiconproject.com/a/api/fastlane…nd=0.34399502584710717 could save 1.7KiB (45% reduction).
Compressing https://flapi1.rubiconproject.com/a/api/fastlane.j…nd=0.24626537505537271 could save 1.7KiB (44% reduction).
Compressing https://fastlane.rubiconproject.com/a/api/fastlane…and=0.9372386175673455 could save 1.6KiB (45% reduction).
Compressing https://fastlane.rubiconproject.com/a/api/fastlane…and=0.6506572149228305 could save 1.6KiB (44% reduction).
Compressing https://flapi2.rubiconproject.com/a/api/fastlane.j…nd=0.09570529498159885 could save 1.5KiB (44% reduction).
Compressing https://triggers1.wfxtriggers.com/json/?resp_type=…70880294_1493716768566 could save 1.4KiB (64% reduction).
Compressing https://bcp.crwdcntrl.net/5/ct=y/c=2216/rand=35405…roTendency_stdy/rt=ifr could save 1KiB (56% reduction).
Compressing https://pixel.mathtag.com/sync/js?sync=auto&mt_lim=5&mm_bnc&mm_bct could save 897B (57% reduction).

priority - 2 Reduce server response time

In our test, your server responded in 0.42 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 - 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 32% of the final above-the-fold content could be rendered with the full HTML response.

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 2KiB (18% reduction).

Minifying https://secure-us.imrworldwide.com/storageframe.html could save 1.2KiB (35% reduction) after compression.
Minifying https://tap-secure.rubiconproject.com/partner/scri…738/42868&geo=na&co=us could save 859B (11% reduction) after compression.

wund.com Desktop Resources

Total Resources212
Number of Hosts77
Static Resources85
JavaScript Resources94
CSS Resources4

wund.com Desktop Resource Breakdown

wund.com mobile page speed rank

Last tested: 2017-04-27


Mobile Speed Bad
53/100

wund.com Mobile Speed Test Quick Summary


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

Your page has 3 blocking script resources and 3 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://icons.wxug.com/scripts/modernizr/2.8.2/modernizr.min.js
https://icons.wxug.com/scripts/wui-whyads/advert.js?0.0.3
https://tags.crwdcntrl.net/c/2216/cc.js?ns=_cc2216

Optimize CSS Delivery of the following:

https://icons.wxug.com/css/wu4/core.css?v=2017041301
https://icons.wxug.com/css/wu4/omnibus.css?v=2017041901
https://icons.wxug.com/css/wu4/homepage.css?v=2017041301

priority - 23 Optimize images

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

Optimize the following images to reduce their size by 226.1KiB (62% reduction).

Compressing https://icons.wxug.com/i/homepage/device-pws.jpg could save 104.5KiB (78% reduction).
Compressing https://icons.wxug.com/i/homepage/device-hero-dark.jpg could save 93KiB (57% reduction).
Compressing https://icons.wxug.com/i/homepage/device-guide.jpg could save 26.1KiB (50% reduction).
Compressing https://icons.wxug.com/i/o/sprite-common-vert.png?v=1.21 could save 2.4KiB (21% reduction).

priority - 16 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://icons.wxug.com/i/homepage/device-guide.jpg (expiration not specified)
https://icons.wxug.com/i/homepage/device-hero-dark.jpg (expiration not specified)
https://icons.wxug.com/i/homepage/device-pws.jpg (expiration not specified)
https://secure-us.imrworldwide.com/v60.js (expiration not specified)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback02108199999 (31 seconds)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback00000103772 (2.8 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback60290199999 (2.9 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback94102199999 (2.9 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…tesCallback77001199999 (4.1 minutes)
https://api-ak-aws.wunderground.com/api/eb7a37c339…esCallback100011199999 (4.2 minutes)
https://api-ak-aws.wunderground.com/api/8dee7a0127…74.005997.json?ttl=300 (4.5 minutes)
https://api-ak-aws.wunderground.com/api/8dee7a0127….0/q/KJRB.json?ttl=300 (4.8 minutes)
https://tags.tiqcdn.com/utag/weather/wunderground/prod/utag.js (5 minutes)
https://js-sec.indexww.com/ht/ls-wunderground.js (7.6 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/sdk.js (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=we…42150&cb=1493278126646 (30 minutes)
https://pagead2.googlesyndication.com/pagead/js/lidar.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://z.moatads.com/weatherv36943544254/moatad.js (10.7 hours)

priority - 8 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 41% of the final above-the-fold content could be rendered with the full HTML response.

priority - 2 Reduce server response time

In our test, your server responded in 0.34 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 Enable 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 7.6KiB (54% reduction).

Compressing https://flapi1.rubiconproject.com/a/api/fastlane.j…and=0.2755968610290438 could save 3.2KiB (57% reduction).
Compressing https://fastlane.rubiconproject.com/a/api/fastlane…nd=0.24626537505537271 could save 1.7KiB (45% reduction).
Compressing https://triggers1.wfxtriggers.com/json/?resp_type=…75673455_1493278125946 could save 1.6KiB (64% reduction).
Compressing https://flapi1.rubiconproject.com/a/api/fastlane.j…nd=0.09570529498159885 could save 1.2KiB (50% 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.8KiB (32% reduction).

Minifying https://secure-us.imrworldwide.com/storageframe.html could save 1.2KiB (35% reduction) after compression.
Minifying https://s0.2mdn.net/4376713/1490386844711/17-PUB-0…-320x50-OP2/index.html could save 612B (27% reduction) after compression.

wund.com Mobile Resources

Total Resources160
Number of Hosts50
Static Resources81
JavaScript Resources80
CSS Resources4

wund.com Mobile Resource Breakdown

wund.com mobile page usability

Last tested: 2017-04-27


Mobile Usability Medium
80/100

wund.com Mobile Usability Test Quick Summary


priority - 23 Size 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 732 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="/login.asp">Log in</a> falls outside the viewport.
The element <a href="/member/registration">Join</a> falls outside the viewport.
The element <i class="fi-widget sidebar-icon"> falls outside the viewport.
The element <a href="javascript:void(0);" class="maps">Maps &amp; Radar</a> falls outside the viewport.
The element <a href="javascript:void(0);" class="severe">Severe Weather</a> falls outside the viewport.
The element <a href="javascript:void(0);" class="news">News &amp; BlogsLIVE!</a> falls outside the viewport.
The element <a href="javascript:void(0);" class="photos">Photos &amp; Video</a> falls outside the viewport.
The element <a href="/history/" class="history">Historical Weather</a> falls outside the viewport.
The element <a href="javascript:void(0);" class="activities">Activities</a> falls outside the viewport.
The element <a href="/sitemap/" class="browse">Site Map</a> falls outside the viewport.
The element <a href="/weatherstatio…uyingguide.asp">Buy a Weather Station</a> falls outside the viewport.
The element <a href="/personal-weat…station/signup">Add Weather Station</a> falls outside the viewport.
The element <a href="/weatherstation/overview.asp">Weather Station Network</a> falls outside the viewport.
The element <a href="/download">Mobile Apps</a> falls outside the viewport.
The element <a href="/weather/api/">Weather API for Developers</a> falls outside the viewport.

priority - 0 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 <div id="global-header" class="new-wu">Log in | Join…More Settings</div> is close to 3 other tap targets.

The tap target <a href="/zmw:"></a> is close to 1 other tap targets.

The tap target <a href="/us/ma/boston/…:02108.1.99999">50 °F Boston, MA</a> is close to 3 other tap targets.

The tap target <input type="button" class="favorites-list-toggle"> is close to 1 other tap targets.

wund.com similar domains

Similar domains:
www.wund.com
www.wund.net
www.wund.org
www.wund.info
www.wund.biz
www.wund.us
www.wund.mobi
www.und.com
www.wund.com
www.qund.com
www.wqund.com
www.qwund.com
www.aund.com
www.waund.com
www.awund.com
www.sund.com
www.wsund.com
www.swund.com
www.eund.com
www.weund.com
www.ewund.com
www.wnd.com
www.wynd.com
www.wuynd.com
www.wyund.com
www.whnd.com
www.wuhnd.com
www.whund.com
www.wjnd.com
www.wujnd.com
www.wjund.com
www.wind.com
www.wuind.com
www.wiund.com
www.wud.com
www.wubd.com
www.wunbd.com
www.wubnd.com
www.wuhd.com
www.wunhd.com
www.wujd.com
www.wunjd.com
www.wumd.com
www.wunmd.com
www.wumnd.com
www.wun.com
www.wunx.com
www.wundx.com
www.wunxd.com
www.wuns.com
www.wunds.com
www.wunsd.com
www.wune.com
www.wunde.com
www.wuned.com
www.wunr.com
www.wundr.com
www.wunrd.com
www.wunf.com
www.wundf.com
www.wunfd.com
www.wunc.com
www.wundc.com
www.wuncd.com
www.wund.con

wund.com 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.


wund.com 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.