INDYGO.NET Home - IndyGo - Boldly Moving Our City Forward

indygo.net Website Information

Daily Unique Visits: 5,928

Daily Page Views: 23,712

Income Per Day: $66

Estimated Value: $35,640

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

indygo.net is registered under .NET top-level domain. Please check other sites in .NET zone.

Website indygo.net is using the following name servers:

  • dns2.easydns.net
  • dns1.easydns.com
  • dns3.easydns.org

and is probably hosted by 20i Limited. See the full list of other websites hosted by 20i Limited.

The highest website indygo.net position in Alexa rank database was 57559 and the lowest rank position was 999892. Current position of indygo.net in Alexa rank database is 211710.

Desktop speed score of indygo.net (47/100) is better than the results of 20.85% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of indygo.net (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of indygo.net (38/100) is better than the results of 16.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

indygo.net 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.


indygo.net 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: INDYGO.NET
Registry Domain ID: 9845729_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.easydns.com
Registrar URL: http://www.easydns.com
Updated Date: 2021-07-21T16:54:27Z
Creation Date: 1999-09-06T02:33:27Z
Registry Expiry Date: 2026-09-06T02:33:27Z
Registrar: easyDNS Technologies Inc.
Registrar IANA ID: 469
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: DNS1.EASYDNS.COM
Name Server: DNS2.EASYDNS.NET
Name Server: DNS3.EASYDNS.ORG
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-11-27T07:10:59Z

indygo.net server information

Servers Location

indygo.net desktop page speed rank

Last tested: 2018-01-31


Desktop Speed Bad
47/100

indygo.net Desktop Speed Test Quick Summary


priority - 105Optimize images

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

Optimize the following images to reduce their size by 1,023.3KiB (43% reduction).

Compressing https://www.indygo.net/wp-content/themes/indygo/li…es/IndyGo_Kate-137.jpg could save 590KiB (33% reduction).
Compressing https://www.indygo.net/wp-content/uploads/2014/12/homepage.jpg could save 430.7KiB (78% reduction).
Compressing https://www.indygo.net/wp-content/uploads/2014/12/MCTP-icon.png could save 2.1KiB (29% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 591B (42% reduction).

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

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

Remove render-blocking JavaScript:

https://www.indygo.net/wp-content/themes/indygo/li…odernizr.custom.min.js
https://www.indygo.net/wp-includes/js/jquery/jquery.js
https://www.indygo.net/wp-includes/js/jquery/jquery-migrate.min.js
https://www.indygo.net/wp-content/themes/indygo/li…uery.magnific-popup.js
https://www.indygo.net/wp-content/themes/indygo/li…libs/jquery.fitvids.js
https://www.indygo.net/wp-content/themes/indygo/li…/libs/jquery.ui.min.js
https://www.indygo.net/wp-content/themes/indygo/li…js/libs/svgeezy.min.js
https://www.indygo.net/wp-content/themes/indygo/library/js/geolocation.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700,400italic
https://maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css
https://www.indygo.net/wp-content/plugins/testimon…st/jquery.bxslider.css
https://www.indygo.net/wp-content/plugins/testimon…estimonials-widget.css
https://fonts.googleapis.com/css?family=Lato%3A400…C400italic%2C700italic
https://www.indygo.net/wp-content/themes/indygo/library/css/style.css
https://www.indygo.net/wp-content/themes/indygo/li…ibs/magnific-popup.css

priority - 7Avoid 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://indygo.net/
http://www.indygo.net/
https://www.indygo.net/

priority - 2Leverage 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://www.googletagmanager.com/gtm.js?id=GTM-TVZ6X5 (15 minutes)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 11.2KiB (38% reduction).

Minifying https://www.indygo.net/wp-content/themes/indygo/library/css/style.css could save 10.4KiB (41% reduction) after compression.
Minifying https://www.indygo.net/wp-content/plugins/testimon…st/jquery.bxslider.css could save 372B (31% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/li…ibs/magnific-popup.css could save 278B (15% reduction) after compression.
Minifying https://www.indygo.net/wp-content/plugins/testimon…estimonials-widget.css could save 115B (19% reduction) after compression.

priority - 1Minify 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 8KiB (39% reduction).

Minifying https://www.indygo.net/wp-content/themes/indygo/li…uery.magnific-popup.js could save 4.9KiB (37% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/library/js/scripts.js could save 2.2KiB (50% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/li…libs/jquery.fitvids.js could save 417B (33% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/library/js/geolocation.js could save 281B (33% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/li…js/libs/svgeezy.min.js could save 215B (33% reduction) after compression.

indygo.net Desktop Resource Breakdown

Total Resources53
Number of Hosts12
Static Resources42
JavaScript Resources22
CSS Resources10

indygo.net mobile page speed rank

Last tested: 2018-02-06


Mobile Speed Bad
38/100

indygo.net Mobile Speed Test Quick Summary


priority - 105Optimize images

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

Optimize the following images to reduce their size by 1,023.3KiB (43% reduction).

Compressing https://www.indygo.net/wp-content/themes/indygo/li…es/IndyGo_Kate-137.jpg could save 590KiB (33% reduction).
Compressing https://www.indygo.net/wp-content/uploads/2014/12/homepage.jpg could save 430.7KiB (78% reduction).
Compressing https://www.indygo.net/wp-content/uploads/2014/12/MCTP-icon.png could save 2.1KiB (29% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 591B (42% reduction).

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

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

Remove render-blocking JavaScript:

https://www.indygo.net/wp-content/themes/indygo/li…odernizr.custom.min.js
https://www.indygo.net/wp-includes/js/jquery/jquery.js
https://www.indygo.net/wp-includes/js/jquery/jquery-migrate.min.js
https://www.indygo.net/wp-content/themes/indygo/li…uery.magnific-popup.js
https://www.indygo.net/wp-content/themes/indygo/li…libs/jquery.fitvids.js
https://www.indygo.net/wp-content/themes/indygo/li…/libs/jquery.ui.min.js
https://www.indygo.net/wp-content/themes/indygo/li…js/libs/svgeezy.min.js
https://www.indygo.net/wp-content/themes/indygo/library/js/geolocation.js

Optimize CSS Delivery of the following:

https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700,400italic
https://maxcdn.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.min.css
https://www.indygo.net/wp-content/plugins/testimon…st/jquery.bxslider.css
https://www.indygo.net/wp-content/plugins/testimon…estimonials-widget.css
https://fonts.googleapis.com/css?family=Lato%3A400…C400italic%2C700italic
https://www.indygo.net/wp-content/themes/indygo/library/css/style.css
https://www.indygo.net/wp-content/themes/indygo/li…ibs/magnific-popup.css

priority - 26Avoid 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://indygo.net/
http://www.indygo.net/
https://www.indygo.net/

priority - 3Leverage 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://www.googletagmanager.com/gtm.js?id=GTM-TVZ6X5 (15 minutes)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 11.2KiB (38% reduction).

Minifying https://www.indygo.net/wp-content/themes/indygo/library/css/style.css could save 10.4KiB (41% reduction) after compression.
Minifying https://www.indygo.net/wp-content/plugins/testimon…st/jquery.bxslider.css could save 372B (31% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/li…ibs/magnific-popup.css could save 278B (15% reduction) after compression.
Minifying https://www.indygo.net/wp-content/plugins/testimon…estimonials-widget.css could save 115B (19% reduction) after compression.

priority - 1Minify 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 8KiB (39% reduction).

Minifying https://www.indygo.net/wp-content/themes/indygo/li…uery.magnific-popup.js could save 4.9KiB (37% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/library/js/scripts.js could save 2.2KiB (50% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/li…libs/jquery.fitvids.js could save 417B (33% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/library/js/geolocation.js could save 281B (33% reduction) after compression.
Minifying https://www.indygo.net/wp-content/themes/indygo/li…js/libs/svgeezy.min.js could save 215B (33% reduction) after compression.

indygo.net Mobile Resource Breakdown

Total Resources53
Number of Hosts12
Static Resources42
JavaScript Resources22
CSS Resources10

indygo.net mobile page usability

Last tested: 2018-02-06


Mobile Usability Good
99/100

indygo.net Mobile Usability Test Quick Summary


priority - 0Size 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 id="expandTimes" href="#" class="closed">Choose Date &amp; Time</a> is close to 1 other tap targets.
The tap target <a id="expandTimes" href="#" class="closed">Choose Date &amp; Time</a> is close to 1 other tap targets.
The tap target <label for="nf-field-23" class="">Email Address *</label> is close to 1 other tap targets.

indygo.net HTML validation

Errors

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 89 Column: 1 - 72
"...</script> <link rel='https://api.w.org/' href='https://www.indygo.net/wp-json/' /> <link..."

Bad value “alert('broken');this.onerror=null;this.src=https://www.indygo.net/wp-content/uploads/2014/12/logo.png” for attribute “onerror” on element “img”: missing ; before statement

Line: 113 Column: 8 - 204
"..."> <img alt="IndyGo" src="https://www.indygo.net/wp-content/uploads/2014/12/logo.svg" onerror="alert('broken');this.onerror=null;this.src=https://www.indygo.net/wp-content/uploads/2014/12/logo.png" /> ..."

End tag “div” seen, but there were open elements.

Line: 254 Column: 9 - 14
"...> </div> ..."

Unclosed element “section”.

Line: 222 Column: 9 - 47
"... <section class="cta-buttons-container"> ..."

Unclosed element “article”.

Line: 158 Column: 7 - 152
"... <article id="post-133" class="cf post-133 page type-page status-publish hentry" role="article" itemscope itemtype="http://schema.org/BlogPosting"> ..."

Stray end tag “article”.

Line: 274 Column: 7 - 16
"...n> </article> ..."

Stray end tag “div”.

Line: 377 Column: 3 - 8
"...</div> </div> ..."

The “for” attribute of the “label” element must refer to a non-hidden form control.

Line: 180 Column: 14 - 38
"... <label for="oldTripForm">From:<..." Line: 183 Column: 14 - 61
"... <label for="oldTripFromCoord" class="hideLabel">Coordi..."

Warnings

The “banner” role is unnecessary for element “header”.

Line: 107 Column: 4 - 88
"...ner"> <header class="header" role="banner" itemscope itemtype="http://schema.org/WPHeader"> ..."

The “navigation” role is unnecessary for element “nav”.

Line: 118 Column: 6 - 89
"... <nav role="navigation" itemscope itemtype="http://schema.org/SiteNavigationElement"> ..."

The “article” role is unnecessary for element “article”.

Line: 158 Column: 7 - 152
"... <article id="post-133" class="cf post-133 page type-page status-publish hentry" role="article" itemscope itemtype="http://schema.org/BlogPosting"> ..."

Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.

Line: 158 Column: 7 - 152
"... <article id="post-133" class="cf post-133 page type-page status-publish hentry" role="article" itemscope itemtype="http://schema.org/BlogPosting"> ..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 283 Column: 4 - 93
".../div> <footer class="footer" role="contentinfo" itemscope itemtype="http://schema.org/WPFooter"> ..."

indygo.net similar domains

Similar domains:
www.indygo.com
www.indygo.net
www.indygo.org
www.indygo.info
www.indygo.biz
www.indygo.us
www.indygo.mobi
www.ndygo.net
www.indygo.net
www.undygo.net
www.iundygo.net
www.uindygo.net
www.jndygo.net
www.ijndygo.net
www.jindygo.net
www.kndygo.net
www.ikndygo.net
www.kindygo.net
www.ondygo.net
www.iondygo.net
www.oindygo.net
www.idygo.net
www.ibdygo.net
www.inbdygo.net
www.ibndygo.net
www.ihdygo.net
www.inhdygo.net
www.ihndygo.net
www.ijdygo.net
www.injdygo.net
www.imdygo.net
www.inmdygo.net
www.imndygo.net
www.inygo.net
www.inxygo.net
www.indxygo.net
www.inxdygo.net
www.insygo.net
www.indsygo.net
www.insdygo.net
www.ineygo.net
www.indeygo.net
www.inedygo.net
www.inrygo.net
www.indrygo.net
www.inrdygo.net
www.infygo.net
www.indfygo.net
www.infdygo.net
www.incygo.net
www.indcygo.net
www.incdygo.net
www.indgo.net
www.indtgo.net
www.indytgo.net
www.indtygo.net
www.indggo.net
www.indyggo.net
www.indgygo.net
www.indhgo.net
www.indyhgo.net
www.indhygo.net
www.indugo.net
www.indyugo.net
www.induygo.net
www.indyo.net
www.indyfo.net
www.indygfo.net
www.indyfgo.net
www.indyvo.net
www.indygvo.net
www.indyvgo.net
www.indyto.net
www.indygto.net
www.indybo.net
www.indygbo.net
www.indybgo.net
www.indyyo.net
www.indygyo.net
www.indyygo.net
www.indyho.net
www.indygho.net
www.indyg.net
www.indygi.net
www.indygoi.net
www.indygio.net
www.indygk.net
www.indygok.net
www.indygko.net
www.indygl.net
www.indygol.net
www.indyglo.net
www.indygp.net
www.indygop.net
www.indygpo.net

indygo.net 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.


indygo.net 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.