Tools & Wizards About Us
pima.gov screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    44% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

pima.gov

Pima County, AZ | Official Website

Page Load Speed

16.4 sec in total

First Response

296 ms

Resources Loaded

10.4 sec

Page Rendered

5.7 sec

pima.gov screenshot

About Website

Welcome to pima.gov homepage info - get ready to check Pima best content for United States right away, or after learning these important things about pima.gov

Pima County Government services and news including Tucson, Marana, Ajo, Oro Valley, Sahuarita, Three Points and Arivaca.

Visit pima.gov

Key Findings

We analyzed Pima.gov page load time and found that the first response time was 296 ms and then it took 16.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

pima.gov performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

pima.gov

296 ms

webcms.pima.gov

1969 ms

jquery.latest.js

631 ms

jquery.migrate.js

630 ms

merged.css

779 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pima.gov, 89% (62 requests) were made to Webcms.pima.gov and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Webcms.pima.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (27%)

Content Size

5.0 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pima.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. 70% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 81.7 kB

  • Original 105.3 kB
  • After minification 100.9 kB
  • After compression 23.6 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 81.7 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 165.9 kB

  • Original 3.5 MB
  • After minification 3.3 MB

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. Pima images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 871.0 kB

  • Original 1.2 MB
  • After minification 904.2 kB
  • After compression 294.4 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 871.0 kB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 232.4 kB

  • Original 270.7 kB
  • After minification 209.0 kB
  • After compression 38.3 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. Pima.gov needs all CSS files to be minified and compressed as it can save up to 232.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (35%)

Requests Now

62

After Optimization

40

  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pima. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pima.gov

pima.gov

296 ms

webcms.pima.gov

webcms.pima.gov

1969 ms

jquery.latest.js

jquery.latest.js

631 ms

jquery.migrate.js

jquery.migrate.js

630 ms

merged.css

merged.css

779 ms

pima_merged.css

pima_merged.css

1406 ms

GoogleAnalytics.js

GoogleAnalytics.js

778 ms

PortalThemeStyle.ashx

PortalThemeStyle.ashx

776 ms

PortalThemeStyle.ashx

PortalThemeStyle.ashx

457 ms

WebResource.axd

WebResource.axd

776 ms

Common_Control.js

Common_Control.js

777 ms

ScriptResource.axd

ScriptResource.axd

1847 ms

ScriptResource.axd

ScriptResource.axd

1647 ms

megamenufade.js

megamenufade.js

1647 ms

hovereffect.js

hovereffect.js

1538 ms

MyFontsWebfontsKit.css

MyFontsWebfontsKit.css

1736 ms

css

css

344 ms

tabs4.js

tabs4.js

1735 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

2259 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

1770 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

1882 ms

fontsizer2.js

fontsizer2.js

2163 ms

Json2.js

Json2.js

2163 ms

jquery-cookie.js

jquery-cookie.js

2163 ms

ga.js

ga.js

870 ms

170502_Pure-water_001.jpg

170502_Pure-water_001.jpg

788 ms

170725_Loop-culvert_001.jpg

170725_Loop-culvert_001.jpg

760 ms

170417_Arivaca-Road_002.jpg

170417_Arivaca-Road_002.jpg

915 ms

120713-Titan-Missile-Museum-p2.jpg

120713-Titan-Missile-Museum-p2.jpg

913 ms

170721_Thamzen%20Carson_032.jpg

170721_Thamzen%20Carson_032.jpg

914 ms

trail%20steward_web.jpg

trail%20steward_web.jpg

800 ms

a-miller-dist1.jpg

a-miller-dist1.jpg

800 ms

Web_Valadez.jpg

Web_Valadez.jpg

912 ms

Web_Bronson.jpg

Web_Bronson.jpg

908 ms

christy%20mug2.jpg

christy%20mug2.jpg

907 ms

Web_Elias.jpg

Web_Elias.jpg

900 ms

150107_Joint%20Courts%20Building06.jpg

150107_Joint%20Courts%20Building06.jpg

900 ms

170418_Board%20of%20supervisors_001%20(1).jpg

170418_Board%20of%20supervisors_001%20(1).jpg

977 ms

150501_Hazy%20Sky_001.jpg

150501_Hazy%20Sky_001.jpg

977 ms

170630_Las%20Artes%20Graduation_001.jpg

170630_Las%20Artes%20Graduation_001.jpg

978 ms

170503_Pacc_001.jpg

170503_Pacc_001.jpg

978 ms

3_new%20laptops_003.jpg

3_new%20laptops_003.jpg

976 ms

160409_Tour%20de%20Cookie_004%20(2).jpg

160409_Tour%20de%20Cookie_004%20(2).jpg

1041 ms

170121_gas%20barbecue%20grill_001.jpg

170121_gas%20barbecue%20grill_001.jpg

978 ms

footer-seal.jpg

footer-seal.jpg

978 ms

tw-sm.png

tw-sm.png

1040 ms

fb-sm.png

fb-sm.png

1040 ms

pima-logo.png

pima-logo.png

1040 ms

home-tabs-over.png

home-tabs-over.png

1040 ms

home-tabs-over-first.png

home-tabs-over-first.png

1058 ms

home-tabs-over-last.png

home-tabs-over-last.png

1874 ms

__utm.gif

__utm.gif

265 ms

collect

collect

688 ms

Home-v2-bg.jpg

Home-v2-bg.jpg

581 ms

130529-Homepage-1-SFW.jpg

130529-Homepage-1-SFW.jpg

588 ms

information.gif

information.gif

1716 ms

home-tabs.png

home-tabs.png

1717 ms

round-middle.png

round-middle.png

1826 ms

bluedash.png

bluedash.png

1716 ms

bluedash-ql3.png

bluedash-ql3.png

1717 ms

footer-gradient.jpg

footer-gradient.jpg

1716 ms

pima-bluestrip-subpage.png

pima-bluestrip-subpage.png

1825 ms

Template-gradient-for-menu.png

Template-gradient-for-menu.png

1788 ms

cse.js

cse.js

602 ms

menu3.png

menu3.png

786 ms

cse.js

cse.js

689 ms

megamenu-bg.png

megamenu-bg.png

456 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

455 ms

235C9C_1_0.woff

235C9C_1_0.woff

457 ms

235C9C_0_0.woff

235C9C_0_0.woff

696 ms

Accessibility Review

pima.gov accessibility score

91

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pima.gov best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pima.gov SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pima.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 Pima.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.

Social Sharing Optimization

pima.gov

Open Graph description is not detected on the main page of Pima. 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: