Tools & Wizards About Us
webapps.sandiego.gov screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

webapps.sandiego.gov

Planned Web Service Maintenance | City of San Diego Official Website

Page Load Speed

1.3 sec in total

First Response

141 ms

Resources Loaded

1 sec

Page Rendered

128 ms

webapps.sandiego.gov screenshot

About Website

Click here to check amazing Web Apps San Diego content for United States. Otherwise, check out these important facts you probably never knew about webapps.sandiego.gov

  The page you are trying to access is currently unavailable due to planned maintenance. Please try back in approximately two hours to allow time for completion of these important maintenance tasks. W...

Visit webapps.sandiego.gov

Key Findings

We analyzed Webapps.sandiego.gov page load time and found that the first response time was 141 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

webapps.sandiego.gov performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value16,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value28.0 s

0/100

10%

Network Requests Diagram

webapps.sandiego.gov

141 ms

appdown

21 ms

css_Kf3dyNBlCaNHleCPrMnXEzvMNvOFqR93BIjuYvB5l4c.css

14 ms

css_0yrvts0wkkqToJkGRmFcCPmqsIk24gDg-rFki62kIx0.css

31 ms

css_w2jjvUWt9WyCz64K2Gj8DN1lmkysx0jl1hU3pI0ZELk.css

35 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Webapps.sandiego.gov, 58% (42 requests) were made to Sandiego.gov and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (307 ms) relates to the external source Sandiego.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 634.9 kB (37%)

Content Size

1.7 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webapps.sandiego.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. 60% of websites need less resources to load. Images take 821.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 49.2 kB

  • Original 67.4 kB
  • After minification 67.4 kB
  • After compression 18.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 49.2 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 821.6 kB
  • After minification 819.2 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. Web Apps San Diego images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 406.6 kB

  • Original 599.3 kB
  • After minification 425.3 kB
  • After compression 192.7 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 406.6 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 176.6 kB

  • Original 218.9 kB
  • After minification 216.1 kB
  • After compression 42.2 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. Webapps.sandiego.gov needs all CSS files to be minified and compressed as it can save up to 176.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (54%)

Requests Now

63

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webapps.sandiego.gov

webapps.sandiego.gov

141 ms

appdown

appdown

21 ms

css_Kf3dyNBlCaNHleCPrMnXEzvMNvOFqR93BIjuYvB5l4c.css

css_Kf3dyNBlCaNHleCPrMnXEzvMNvOFqR93BIjuYvB5l4c.css

14 ms

css_0yrvts0wkkqToJkGRmFcCPmqsIk24gDg-rFki62kIx0.css

css_0yrvts0wkkqToJkGRmFcCPmqsIk24gDg-rFki62kIx0.css

31 ms

css_w2jjvUWt9WyCz64K2Gj8DN1lmkysx0jl1hU3pI0ZELk.css

css_w2jjvUWt9WyCz64K2Gj8DN1lmkysx0jl1hU3pI0ZELk.css

35 ms

css

css

61 ms

main.min.css

main.min.css

36 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

68 ms

js_QDpO160Ifm_w0RDXSybTgl37H8KXGWu1a-_47ZilhEY.js

js_QDpO160Ifm_w0RDXSybTgl37H8KXGWu1a-_47ZilhEY.js

28 ms

js_uPQwY6eviR5HMC2n3f1iX0Ih9fKe1pPNNpmLSpdK40Q.js

js_uPQwY6eviR5HMC2n3f1iX0Ih9fKe1pPNNpmLSpdK40Q.js

54 ms

js_JITF9mHWwYZsm7yVnf9zMAMSPI2BERAJOQANa-yGTLs.js

js_JITF9mHWwYZsm7yVnf9zMAMSPI2BERAJOQANa-yGTLs.js

85 ms

js_nx2ZQkNpKGa-vp1uWPmDDMlOpNZZrZl-9Fe2Ry-g6eQ.js

js_nx2ZQkNpKGa-vp1uWPmDDMlOpNZZrZl-9Fe2Ry-g6eQ.js

55 ms

require.js

require.js

55 ms

js_AZ9y0PShar4GyPuQUcAgecHmIwX4TUOo0HFPa06mnF0.js

js_AZ9y0PShar4GyPuQUcAgecHmIwX4TUOo0HFPa06mnF0.js

54 ms

element.js

element.js

254 ms

js_injector_14.js

js_injector_14.js

61 ms

js_injector_49.js

js_injector_49.js

253 ms

sdk.js

sdk.js

213 ms

widgets.js

widgets.js

123 ms

logo.png

logo.png

46 ms

logo-mark-blue.png

logo-mark-blue.png

45 ms

search-icon-blue.png

search-icon-blue.png

90 ms

blaboa-park_0.jpg

blaboa-park_0.jpg

44 ms

torrey-pines.jpg

torrey-pines.jpg

43 ms

special-events.jpg

special-events.jpg

43 ms

waterbill.jpg

waterbill.jpg

93 ms

trash-schedule.jpg

trash-schedule.jpg

93 ms

featureparkingmeter_0.jpg

featureparkingmeter_0.jpg

139 ms

business-tax.jpg

business-tax.jpg

96 ms

development-process.jpg

development-process.jpg

93 ms

business-steps_0.jpg

business-steps_0.jpg

139 ms

library-catalog.jpg

library-catalog.jpg

142 ms

library-card.jpg

library-card.jpg

141 ms

library-volunteer.jpg

library-volunteer.jpg

142 ms

neighborhood-watch-logo.jpg

neighborhood-watch-logo.jpg

255 ms

alert-sd.jpg

alert-sd.jpg

169 ms

flag-th.png

flag-th.png

249 ms

council-meetings.jpg

council-meetings.jpg

168 ms

committee-meeting.jpg

committee-meeting.jpg

169 ms

fy18cover-adopted.jpg

fy18cover-adopted.jpg

288 ms

employment.jpg

employment.jpg

249 ms

skyline-v2.jpg

skyline-v2.jpg

288 ms

logo--white--sm.png

logo--white--sm.png

253 ms

best-of-web-badge.png

best-of-web-badge.png

291 ms

translateelement.css

translateelement.css

152 ms

main.js

main.js

247 ms

survey.js

survey.js

288 ms

main-built.js

main-built.js

307 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

135 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

164 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

252 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

252 ms

icomoon.ttf

icomoon.ttf

305 ms

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf

251 ms

ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf

ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf

251 ms

socials.ttf

socials.ttf

284 ms

244 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

281 ms

analytics.js

analytics.js

212 ms

gtm.js

gtm.js

211 ms

extlink_s.png

extlink_s.png

132 ms

element_main.js

element_main.js

60 ms

150 ms

translate_24dp.png

translate_24dp.png

91 ms

l

l

56 ms

cleardot.gif

cleardot.gif

103 ms

translate_24dp.png

translate_24dp.png

72 ms

linkid.js

linkid.js

42 ms

te_ctrl3.gif

te_ctrl3.gif

23 ms

collect

collect

7 ms

collect

collect

47 ms

collect

collect

5 ms

collect

collect

54 ms

Accessibility Review

webapps.sandiego.gov accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Links do not have a discernible name

Best Practices

webapps.sandiego.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

webapps.sandiego.gov SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 Webapps.sandiego.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 Webapps.sandiego.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

webapps.sandiego.gov

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