tempe.gov Website Information
Daily Unique Visits: 56,968
Daily Page Views: 341,808
Income Per Day: $684
Estimated Value: $492,480
This website is located in United States and is using following IP address 135.84.124.41. See the complete list of popular websites hosted in United States.
tempe.gov is registered under .GOV top-level domain. Please check other sites in .GOV zone.
Website tempe.gov is using the following name servers:
- ns1-01.azure-dns.com
- ns2-01.azure-dns.net
- ns3-01.azure-dns.org
- ns4-01.azure-dns.info
and is probably hosted by AMAZON-02 - Amazon.com, Inc., US. See the full list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.
The highest website tempe.gov position in Alexa rank database was 24124 and the lowest rank position was 26701. Current position of tempe.gov in Alexa rank database is 25176.
Desktop speed score of tempe.gov (51/100) is better than the results of 24.87% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of tempe.gov (86/100) is better than the results of 27.73% of other sites and means that the page is mobile-friendly.
Mobile speed score of tempe.gov (48/100) is better than the results of 30.32% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
tempe.gov 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.
tempe.gov 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.
Registrar WHOIS Server: whois.nic.gov
Registrar URL: https://get.gov
Updated Date: 2024-01-08T03:26:58Z
Creation Date: 1997-10-02T01:29:30Z
Registry Expiry Date: 2025-09-30T04:00:00Z
Registrar: Cybersecurity and Infrastructure Security Agency
Registrar IANA ID: 8888888
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: REDACTED FOR PRIVACY
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: REDACTED FOR PRIVACY
Registrant Phone: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: REDACTED FOR PRIVACY
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Registry Security ID: REDACTED FOR PRIVACY
Security Name: REDACTED FOR PRIVACY
Security Organization: REDACTED FOR PRIVACY
Security Street: REDACTED FOR PRIVACY
Security City: REDACTED FOR PRIVACY
Security State/Province: REDACTED FOR PRIVACY
Security Postal Code: REDACTED FOR PRIVACY
Security Country: REDACTED FOR PRIVACY
Security Phone: REDACTED FOR PRIVACY
Security Email: scott_campbell@tempe.gov
Name Server: dylan.ns.cloudflare.com
Name Server: karina.ns.cloudflare.com
DNSSEC: unsigned
>>> Last update of WHOIS database: 2024-09-22T09:51:34Z
tempe.gov server information
Servers Location
tempe.gov desktop page speed rank
Last tested: 2017-07-27
tempe.gov Desktop Speed Test Quick Summary
priority - 64Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 626KiB (58% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=31461&t=636358890155270000 could save 134.4KiB (76% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=19196&t=635791968211070000 could save 124.6KiB (68% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/main_bg.jpg could save 91.7KiB (49% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=28254&t=636173911698170000 could save 48.8KiB (65% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/home_content_top.png could save 18.4KiB (20% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=12704&t=635424068097770000 could save 14.6KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/footer_bg_home.jpg could save 9.4KiB (19% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10455&t=635324738797430000 could save 1.8KiB (12% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/events_link.png could save 1.6KiB (47% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10475&t=635324740072170000 could save 1.6KiB (11% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/news_link.png could save 1.6KiB (45% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10437&t=635324731134200000 could save 1.4KiB (41% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/topics_link.png could save 1.3KiB (45% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/go_buttons.png could save 1.3KiB (73% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/next.png could save 1.2KiB (34% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10433&t=635324731126570000 could save 1.2KiB (41% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10431&t=635324731122630000 could save 1.2KiB (37% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/nav/home_buttons.png could save 1.1KiB (59% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/sitemap.gif could save 1.1KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/contact.gif could save 1.1KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/prev.png could save 1.1KiB (33% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/news_title_bg.jpg could save 1.1KiB (66% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10435&t=635324731130470000 could save 1KiB (32% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/go_button.png could save 935B (77% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/content_strip.png could save 849B (82% reduction).
priority - 27Reduce server response time
priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://www.tempe.gov/Scripts/ScriptBundleAngularLi…PHoz0NZ7g4VVdWaIn7RNo1
Optimize CSS Delivery of the following:
http://www.tempe.gov/Project/Contents/Main/StyleBu…QGO70AcWyT6xcWppw9c0w1
http://www.tempe.gov/Areas/Admin/Content/StyleBund…nOUnqKuoiK61z7_e6NMxo1
http://www.tempe.gov/DefaultContent/Default/kendo/…LGTLBh6mO_aQWPARk7ONM1
http://www.tempe.gov/Project/Contents/Main/x-small.css
http://www.tempe.gov/DefaultContent/Default/StyleB…7IGXKm4NOJhdA51oOtG5A1
http://www.tempe.gov/DefaultContent/Default/StyleB…-z8_WTsoZ7bqx2pLTZtXU1
http://www.tempe.gov/Project/Contents/Main/StyleBu…k0o1lYanFxbGVq1zKJAUo1
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:
http://www.googletagmanager.com/gtm.js?id=GTM-T7JG59&l=userDataLayer (15 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 0Minify 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 4KiB (29% reduction).
priority - 0Minify 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 2.7KiB (18% reduction).
tempe.gov Desktop Resource Breakdown
Total Resources | 81 |
Number of Hosts | 9 |
Static Resources | 47 |
JavaScript Resources | 12 |
CSS Resources | 10 |
tempe.gov mobile page speed rank
Last tested: 2017-06-02
tempe.gov Mobile Speed Test Quick Summary
priority - 74Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 726.4KiB (69% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=17270&t=636298290933370000 could save 207.8KiB (73% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=30451&t=636305475589270000 could save 134.4KiB (76% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=30345&t=636301753934430000 could save 85.6KiB (70% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=28258&t=636173911707570000 could save 46.9KiB (65% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=30517&t=636307983505800000 could save 12.4KiB (21% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=30703&t=636320082102353862 could save 4.4KiB (74% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10455&t=635324738797430000 could save 1.8KiB (12% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10475&t=635324740072170000 could save 1.6KiB (11% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10437&t=635324731134200000 could save 1.4KiB (41% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/mob_arrow.gif could save 1.2KiB (80% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/next.png could save 1.2KiB (34% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10433&t=635324731126570000 could save 1.2KiB (41% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10431&t=635324731122630000 could save 1.2KiB (37% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cm…obile_header_strip.gif could save 1.1KiB (91% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/home.gif could save 1.1KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/sitemap.gif could save 1.1KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/mob_header.gif could save 1.1KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cm…ile/mob_header_nav.gif could save 1.1KiB (90% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/mobile/contact.gif could save 1.1KiB (87% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/home/prev.png could save 1.1KiB (33% reduction).
Compressing http://www.tempe.gov/Home/ShowImage?id=10435&t=635324731130470000 could save 1KiB (32% reduction).
Compressing http://www.tempe.gov/Project/Contents/Main/_gfx/cmn/go_button.png could save 935B (77% reduction).
priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://www.tempe.gov/Scripts/ScriptBundleAngularLi…kaJCM5cTW7G67aAFgvE-01
Optimize CSS Delivery of the following:
http://www.tempe.gov/Project/Contents/Main/StyleBu…QGO70AcWyT6xcWppw9c0w1
http://www.tempe.gov/Areas/Admin/Content/StyleBund…nOUnqKuoiK61z7_e6NMxo1
http://www.tempe.gov/DefaultContent/Default/kendo/…LGTLBh6mO_aQWPARk7ONM1
http://www.tempe.gov/Project/Contents/Main/x-small.css
http://www.tempe.gov/DefaultContent/Default/StyleB…7IGXKm4NOJhdA51oOtG5A1
http://www.tempe.gov/DefaultContent/Default/StyleB…-z8_WTsoZ7bqx2pLTZtXU1
http://www.tempe.gov/Project/Contents/Main/StyleBu…k0o1lYanFxbGVq1zKJAUo1
priority - 3Reduce server response time
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:
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 0Minify 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 4KiB (29% reduction).
priority - 0Minify 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 2.6KiB (17% reduction).
tempe.gov Mobile Resource Breakdown
Total Resources | 70 |
Number of Hosts | 9 |
Static Resources | 33 |
JavaScript Resources | 11 |
CSS Resources | 10 |
tempe.gov mobile page usability
Last tested: 2017-06-02
tempe.gov Mobile Usability Test Quick Summary
priority - 13Size 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.
<a href="#pagebody"></a>
and 9 others are close to other tap targets.<a href="#" class="flex-prev">Previous</a>
is close to 6 other tap targets.<a href="#" class="flex-next">Next</a>
is close to 6 other tap targets.<a href="/Home/Componen…1?backlist=%2f">Tempe’s 2017 U…dy is underway</a>
and 2 others are close to other tap targets.<a href="/Home/Componen…1?backlist=%2f">Vice Mayor hig…s in new video</a>
and 13 others are close to other tap targets.<a href="/city-hall/com…epartment-news" class="box_bottomlink">More News</a>
and 2 others are close to other tap targets.The tap target
<a href="/home">Home</a>
and 12 others are close to other tap targets.priority - 1Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Vision Internet
and 12 others render only 8 pixels tall.City of Tempe,…ed. Created by
and 13 others render only 8 pixels tall.tempe.gov HTML validation
Errors
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
"..."UTF-8" /><meta http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7; IE=EDGE" /><title..."
Bad start tag in “iframe” in “head”.
"...<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-5NNDW5Q" height="0" width="0" style="display:none;visibility:hidden"></ifra..."
Stray end tag “noscript”.
"...></iframe></noscript> <scri..."
Stray end tag “head”.
"...anager --></head> <bod..."
Start tag “body” seen but an element of the same type was already open.
"...></head> <body class="front_end_body site_standardsitetemplate "> <..."
Cannot recover after last error. Any further errors will be ignored.
"...></head> <body class="front_end_body site_standardsitetemplate "> <..."
tempe.gov similar domains
www.tempe.net
www.tempe.org
www.tempe.info
www.tempe.biz
www.tempe.us
www.tempe.mobi
www.empe.gov
www.tempe.gov
www.rempe.gov
www.trempe.gov
www.rtempe.gov
www.fempe.gov
www.tfempe.gov
www.ftempe.gov
www.gempe.gov
www.tgempe.gov
www.gtempe.gov
www.yempe.gov
www.tyempe.gov
www.ytempe.gov
www.tmpe.gov
www.twmpe.gov
www.tewmpe.gov
www.twempe.gov
www.tsmpe.gov
www.tesmpe.gov
www.tsempe.gov
www.tdmpe.gov
www.tedmpe.gov
www.tdempe.gov
www.trmpe.gov
www.termpe.gov
www.tepe.gov
www.tenpe.gov
www.temnpe.gov
www.tenmpe.gov
www.tejpe.gov
www.temjpe.gov
www.tejmpe.gov
www.tekpe.gov
www.temkpe.gov
www.tekmpe.gov
www.teme.gov
www.temoe.gov
www.tempoe.gov
www.temope.gov
www.temle.gov
www.temple.gov
www.temlpe.gov
www.temp.gov
www.tempw.gov
www.tempew.gov
www.tempwe.gov
www.temps.gov
www.tempes.gov
www.tempse.gov
www.tempd.gov
www.temped.gov
www.tempde.gov
www.tempr.gov
www.temper.gov
www.tempre.gov
tempe.gov 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.
tempe.gov 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.