6.2 sec in total
248 ms
5.4 sec
553 ms
Visit tempe.gov now to see the best up-to-date Tempe content for United States and also check out these interesting facts you probably never knew about tempe.gov
This is the official website for the City of Tempe, Arizona. You may find all information about the city and its government services here.
Visit tempe.govWe analyzed Tempe.gov page load time and found that the first response time was 248 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tempe.gov performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value40.1 s
0/100
25%
Value6.2 s
43/100
10%
Value460 ms
62/100
30%
Value0
100/100
15%
Value10.3 s
25/100
10%
248 ms
611 ms
330 ms
277 ms
206 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 92% of them (66 requests) were addressed to the original Tempe.gov, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Rum-static.pingdom.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Tempe.gov.
Page size can be reduced by 142.3 kB (8%)
1.7 MB
1.6 MB
In fact, the total size of Tempe.gov main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 58.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.8 kB or 82% of the original size.
Potential reduce by 77.0 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Tempe images are well optimized though.
Potential reduce by 6.5 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.5 kB or 25% of the original size.
Potential reduce by 93 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Tempe.gov needs all CSS files to be minified and compressed as it can save up to 93 B or 43% of the original size.
Number of requests can be reduced by 11 (16%)
68
57
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tempe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
tempe.gov
248 ms
www.tempe.gov
611 ms
StyleBundleDesignTheme.cssbnd
330 ms
StyleBundleDesignTheme.cssbnd
277 ms
StyleBundleFrontendExtra.cssbnd
206 ms
ScriptBundleFAllInOne.jsbnd
547 ms
x-small.css
142 ms
StyleBundleMegaMenuDropDown.cssbnd
191 ms
StyleBundleMegaMenuDropDown.cssbnd
216 ms
homelayout_scripts.js
203 ms
ScriptBundleVisionFrontend.jsbnd
303 ms
ga.js
61 ms
prum.min.js
90 ms
messagebox_strip.gif
151 ms
footer_bg_home.jpg
337 ms
main_bg.jpg
391 ms
spacer.gif
135 ms
logo.png
359 ms
sitemap.gif
132 ms
contact.gif
133 ms
go_buttons.png
334 ms
go_button.png
354 ms
ShowImage
447 ms
ShowImage
343 ms
ShowImage
435 ms
ShowImage
364 ms
ShowImage
470 ms
ShowImage
435 ms
ShowImage
436 ms
ShowImage
469 ms
ShowImage
467 ms
ShowImage
468 ms
ShowImage
468 ms
ShowImage
493 ms
ShowImage
551 ms
ShowImage
581 ms
ShowImage
574 ms
ShowImage
587 ms
ShowImage
583 ms
ShowImage
563 ms
ShowImage
804 ms
ShowImage
802 ms
ShowImage
778 ms
mainnav.png
719 ms
get_involved.png
684 ms
__utm.gif
77 ms
collect
192 ms
collage_bg_new.png
390 ms
home_content_top.png
395 ms
button_bg.png
334 ms
content_strip.png
326 ms
news_shadow.png
325 ms
news_title_bg.jpg
323 ms
news_link.png
294 ms
events_title_bg.png
345 ms
events_link.png
344 ms
social_shadow.png
336 ms
topics_shadow.png
337 ms
topics_link.png
336 ms
ga-audiences
269 ms
Print.cssbnd
68 ms
Print.cssbnd
87 ms
ShowImage
92 ms
ShowImage
82 ms
ShowImage
2360 ms
ShowImage
84 ms
ShowImage
89 ms
ShowImage
83 ms
prev.png
138 ms
next.png
140 ms
home_buttons.png
141 ms
beacon.gif
71 ms
tempe.gov accessibility score
tempe.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
tempe.gov SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tempe.gov can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Tempe.gov main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
tempe.gov
Open Graph description is not detected on the main page of Tempe. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: