5.7 sec in total
1.5 sec
4.1 sec
123 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 1.5 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
phoenix.gov performance score
name
value
score
weighting
Value12.6 s
0/100
10%
Value28.4 s
0/100
25%
Value24.0 s
0/100
10%
Value7,170 ms
0/100
30%
Value0.537
14/100
15%
Value50.5 s
0/100
10%
1488 ms
63 ms
371 ms
435 ms
375 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 62% of them (103 requests) were addressed to the original Phoenix.gov, 9% (15 requests) were made to Fonts.gstatic.com and 4% (6 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Phoenix.gov.
Page size can be reduced by 705.8 kB (14%)
5.0 MB
4.3 MB
In fact, the total size of Phoenix.gov main page is 5.0 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. Only a small number of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 314.5 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 314.5 kB or 87% of the original size.
Potential reduce by 124.1 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. Phoenix images are well optimized though.
Potential reduce by 171.2 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 171.2 kB or 12% of the original size.
Potential reduce by 96.0 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 96.0 kB or 37% of the original size.
Number of requests can be reduced by 103 (70%)
147
44
The browser has sent 147 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 82 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.phoenix.gov
1488 ms
gtm.js
63 ms
addtohomescreen.js
371 ms
corev15-51C31438.themedcss
435 ms
searchv15-6159CCCD.themedcss
375 ms
controls15-51FFDD78.themedcss
370 ms
plugins.css
370 ms
style.css
409 ms
citysharepointreset.css
388 ms
addtohomescreen.css
388 ms
custom.css
444 ms
translator.css
456 ms
communications.css
465 ms
newsroom.css
481 ms
initstrings.js
496 ms
init.js
614 ms
ScriptResource.axd
571 ms
blank.js
526 ms
ScriptResource.axd
540 ms
sp.init.js
557 ms
clientrenderer.js
588 ms
srch.resources.js
601 ms
search.clientcontrols.js
645 ms
search.cbs.js
655 ms
item_cityimageslideridlink2.js
656 ms
group_content.js
658 ms
control_cityimageslider.js
670 ms
item_calendarlistconfigurable.js
684 ms
control_citycalendar.js
682 ms
item_newsroomfeedsinglecolumn.js
688 ms
control_newsroom_2columnnewsfeed.js
712 ms
item_breakingnews.js
725 ms
control_genericlist.js
744 ms
item_city_badge.js
770 ms
control_htmlcontent.js
771 ms
item_quicklinks.js
773 ms
control_quicklinks.js
781 ms
css
36 ms
js
76 ms
js
155 ms
js
49 ms
fbevents.js
36 ms
pixel.js
25 ms
destination
134 ms
widgets.js
258 ms
rp.gif
218 ms
t2_aed3hzgh_telemetry
104 ms
987ea4d4c9.js
137 ms
element.js
75 ms
item_explore_nav.js
434 ms
control_explore_nav.js
446 ms
item_footer_item.js
472 ms
control_footer_column_1.js
472 ms
jquery.min.js
471 ms
sp.res.js
461 ms
css
18 ms
sp.runtime.js
457 ms
sp.js
550 ms
sp.ui.dialog.js
463 ms
phxatyourserviceurls.js
474 ms
css
18 ms
script.js
466 ms
css
19 ms
jquery.spservices-2014.01.min.js
468 ms
plugins.js
544 ms
ribbonstyle.js
453 ms
youtubenorelatedfix.js
498 ms
gtrans.js
487 ms
jquery-ui_1-11-4.min.js
537 ms
newtab.js
515 ms
WebResource.axd
499 ms
SB_Countdown.js
486 ms
skip_links_with_nav.js
443 ms
download_tracking.js
431 ms
5aU69_a8oxmIdGl4AQ.ttf
39 ms
5aU19_a8oxmIfNJdERySiA.ttf
42 ms
spcommon.png
89 ms
favicon.ico
98 ms
logo-cop.png
204 ms
searchresultui-61174269.themedpng
205 ms
f_logo_RGB-White_58.png
204 ms
Bar_Button_27.jpg
205 ms
Bar_Button_47.jpg
261 ms
Bar_Button_50.jpg
260 ms
Bar_Button_46.jpg
398 ms
Bar_Button_43.jpg
264 ms
GOPHXBanner.png
239 ms
home_page_badge_AAC.jpg
239 ms
S389.jpg
464 ms
Bar_Button_51.jpg
400 ms
sdk.js
11 ms
sprite-icons.png
392 ms
bg-cop-logo-blue.png
391 ms
MediaPlayer.php
197 ms
tweet_button.534c17036beb62f94dbf2b30b59dc118.en.html
56 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
18 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
60 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
60 ms
sdk.js
40 ms
up_loader.1.1.0.js
164 ms
jot
195 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf
117 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf
115 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf
117 ms
searchcenterurl
275 ms
strings.js
258 ms
theme4.css
298 ms
newsroom.css
256 ms
jquery-ui-1.10.4.custom.css
295 ms
footer.css
300 ms
customstrings.js
315 ms
cop-custom.js
315 ms
moment.min.js
402 ms
jquery-ui.min.js
400 ms
items
547 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
115 ms
player.js
57 ms
js
56 ms
jquery-3.4.1.min.js
109 ms
gmp.js
56 ms
settings
85 ms
player
69 ms
skin.css
67 ms
font-awesome.min.css
65 ms
jquery-3.4.1.min.js
39 ms
hls.light.min.js
74 ms
flowplayer.js
73 ms
custom-flowplayer-event-listeners.js
72 ms
pubnub.4.13.0.js
74 ms
core.js
220 ms
cast_sender.js
182 ms
flowplayer.woff
178 ms
fontawesome-webfont.woff
93 ms
moment.min.js
133 ms
vAh0zdf14wY
161 ms
9y6dktcSDIQ
532 ms
S086_SwimLessons.jpg
161 ms
S384.png
96 ms
S390.jpg
133 ms
S343.jpg
158 ms
S339B.jpg
159 ms
S328.jpg
464 ms
logo_interlink_box3.jpg
204 ms
749x421_Sarah_F_PCC.jpg
523 ms
Copy%20of%20Newsroom%20Image%20(1).png
648 ms
Newsroom_Housing_010.png
673 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf
43 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf
39 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf
41 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf
41 ms
sp.publishing.resources.js
392 ms
mquery.js
381 ms
corev15-51C31438.themedcss
436 ms
H116_Home_Page.jpg
535 ms
www-player.css
15 ms
www-embed-player.js
32 ms
base.js
57 ms
jRYISRuM9q7e_xyYaLp_fsq3qnLjbNevd8JDa-bOkpI.js
211 ms
embed.js
171 ms
mediaplayer.js
108 ms
sp.core.js
307 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
16 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
15 ms
Create
205 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
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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
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: