3.6 sec in total
284 ms
3.2 sec
164 ms
Click here to check amazing Phoenix content for United States. Otherwise, check out these important facts you probably never knew about phoenix.gov
Welcome to the Official Website of the City of Phoenix, Arizona, where you can find information for residents, visitors and businesses.
Visit phoenix.govWe analyzed Phoenix.gov page load time and found that the first response time was 284 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
phoenix.gov performance score
name
value
score
weighting
Value14.2 s
0/100
10%
Value32.7 s
0/100
25%
Value28.2 s
0/100
10%
Value23,350 ms
0/100
30%
Value0.273
45/100
15%
Value52.9 s
0/100
10%
284 ms
500 ms
244 ms
322 ms
309 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 65% of them (71 requests) were addressed to the original Phoenix.gov, 17% (19 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (748 ms) belongs to the original domain Phoenix.gov.
Page size can be reduced by 4.5 MB (63%)
7.1 MB
2.7 MB
In fact, the total size of Phoenix.gov main page is 7.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 344.2 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 344.2 kB or 85% of the original size.
Potential reduce by 247.7 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. Obviously, Phoenix needs image optimization as it can save up to 247.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.3 MB
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 3.3 MB or 72% of the original size.
Potential reduce by 545.4 kB
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. Phoenix.gov needs all CSS files to be minified and compressed as it can save up to 545.4 kB or 81% of the original size.
Number of requests can be reduced by 64 (74%)
87
23
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
phoenix.gov
284 ms
www.phoenix.gov
500 ms
corev15-51C31438.themedcss
244 ms
searchv15-6159CCCD.themedcss
322 ms
controls15-51FFDD78.themedcss
309 ms
plugins.css
311 ms
style.css
313 ms
citysharepointreset.css
305 ms
custom.css
328 ms
init.js
438 ms
ScriptResource.axd
380 ms
blank.js
373 ms
ScriptResource.axd
384 ms
sp.init.js
375 ms
clientrenderer.js
394 ms
ScriptResx.ashx
459 ms
search.clientcontrols.js
508 ms
search.cbs.js
460 ms
item_citynews.js
466 ms
group_content.js
476 ms
control_citynews.js
523 ms
item_cityimageslideridlink.js
526 ms
control_cityimageslider.js
530 ms
control_citycalendar.js
564 ms
item_breakingnews.js
566 ms
control_genericlist.js
598 ms
item_city_badge.js
601 ms
control_htmlcontent.js
610 ms
item_quicklinks.js
612 ms
control_quicklinks.js
646 ms
item_hero.js
645 ms
control_hero.js
683 ms
item_explore_nav.js
685 ms
control_explore_nav.js
691 ms
item_continuingupdates.js
695 ms
control_footer_nav.js
729 ms
jquery.min.js
748 ms
css
53 ms
addthis_widget.js
33 ms
ScriptResx.ashx
727 ms
sp.ui.dialog.js
518 ms
sp.runtime.js
479 ms
sp.js
596 ms
script.js
534 ms
jquery.spservices-2014.01.min.js
562 ms
plugins.js
568 ms
ribbonstyle.js
554 ms
WebResource.axd
516 ms
spcommon.png
205 ms
favicon.ico
204 ms
logo-cop.png
221 ms
searchresultui-61174269.themedpng
219 ms
all.js
431 ms
FqNXgpTpkWI
211 ms
sprite-icons.png
192 ms
bg-cop-logo-blue.png
188 ms
sprite-social-icons.png
396 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
190 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
191 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
191 ms
anMUvcNT0H1YN4FII8wprzsSLeNQG2cy_mKit6iEdYs.ttf
190 ms
anMUvcNT0H1YN4FII8wpr4e2tK5W43RXgBRKkM4A5Qg.ttf
211 ms
7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf
211 ms
anMUvcNT0H1YN4FII8wpr93Z6MveExszb-iKWJY7ddA.ttf
228 ms
r9OmwyQxrgzUAhaLET_KO33biFuL3q2SDfti1FP8KHU.ttf
228 ms
RZunN20OBmkvrU7sA4GPPhPpE1UvVmSV1Lr9FL5pkyg.ttf
227 ms
RZunN20OBmkvrU7sA4GPPqVmZCTV49gQmgPOUhY_xPU.ttf
227 ms
RZunN20OBmkvrU7sA4GPPvAhmxqQ1BKIUahWaanY54Y.ttf
228 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
227 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
229 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
228 ms
analytics.js
207 ms
jquery-ui-1.10.4.custom.css
300 ms
customstrings.js
297 ms
cop-custom.js
323 ms
jquery-ui.min.js
381 ms
300lo.json
120 ms
sh.7c7179124ea24ac6ba46caac.html
45 ms
www-embed-player-vflZsBgOl.css
98 ms
www-embed-player.js
199 ms
base.js
338 ms
linkid.js
19 ms
initstrings.js
161 ms
collect
13 ms
collect
138 ms
layers.3643cb2e25fb91c29386.js
31 ms
strings.js
182 ms
162 ms
xd_arbiter.php
302 ms
moment.min.js
187 ms
moment.min.js
204 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
81 ms
ad_status.js
79 ms
H011_Home_Page.jpg
438 ms
WH%20Tax%20help%20small.jpg
282 ms
S030_Sustain.jpg
215 ms
ymyw2013_winnersB.jpg
224 ms
S025_28MapsLater.jpg
393 ms
S015_Ancient_day.jpg
589 ms
core.js
377 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
33 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
33 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
32 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
31 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
30 ms
ScriptResx.ashx
72 ms
corev15-51C31438.themedcss
178 ms
mediaplayer.js
76 ms
ping
35 ms
phoenix.gov accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
phoenix.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
phoenix.gov SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Phoenix.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 Phoenix.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.
phoenix.gov
Open Graph description is not detected on the main page of Phoenix. 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: