Tools & Wizards About Us
sandag.org screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

sandag.org

SANDAG - SANDAG Home

Page Load Speed

2.7 sec in total

First Response

770 ms

Resources Loaded

1.8 sec

Page Rendered

149 ms

sandag.org screenshot

About Website

Visit sandag.org now to see the best up-to-date SANDAG content for United States and also check out these interesting facts you probably never knew about sandag.org

SANDAG home page

Visit sandag.org

Key Findings

We analyzed Sandag.org page load time and found that the first response time was 770 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

sandag.org performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value25.4 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.313

37/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

sandag.org

770 ms

javascript.js

183 ms

script_genValid.js

258 ms

jquery-1.5.1.min.js

510 ms

jquery-ui-1.8.11.custom.min.js

652 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 63% of them (25 requests) were addressed to the original Sandag.org, 10% (4 requests) were made to Translate.googleapis.com and 8% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (770 ms) belongs to the original domain Sandag.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.4 kB (34%)

Content Size

1.0 MB

After Optimization

669.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sandag.org main page is 1.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. 20% of websites need less resources to load. Images take 510.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.9 kB

  • Original 30.4 kB
  • After minification 24.1 kB
  • After compression 7.4 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. This page needs HTML code to be minified as it can gain 6.2 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.9 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 45.8 kB

  • Original 510.9 kB
  • After minification 465.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. SANDAG images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 226.5 kB

  • Original 412.6 kB
  • After minification 397.8 kB
  • After compression 186.1 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 226.5 kB or 55% of the original size.

CSS Optimization

-81%

Potential reduce by 47.2 kB

  • Original 58.1 kB
  • After minification 41.0 kB
  • After compression 10.8 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. Sandag.org needs all CSS files to be minified and compressed as it can save up to 47.2 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sandag.org

sandag.org

770 ms

javascript.js

javascript.js

183 ms

script_genValid.js

script_genValid.js

258 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

510 ms

jquery-ui-1.8.11.custom.min.js

jquery-ui-1.8.11.custom.min.js

652 ms

jquery-ui-1.8.11.custom.css

jquery-ui-1.8.11.custom.css

347 ms

mainLayout.css

mainLayout.css

266 ms

homeLayout.css

homeLayout.css

416 ms

interiorLayout.css

interiorLayout.css

334 ms

links.css

links.css

346 ms

jquery.easyslides.source.v1.1.js

jquery.easyslides.source.v1.1.js

353 ms

element.js

element.js

49 ms

analytics.js

analytics.js

63 ms

logo_sandag.gif

logo_sandag.gif

79 ms

btn_search_lg.png

btn_search_lg.png

80 ms

programs.png

programs.png

80 ms

resources.png

resources.png

82 ms

services.png

services.png

80 ms

emailnewsletter.png

emailnewsletter.png

83 ms

btn_email_go.png

btn_email_go.png

148 ms

facebook.png

facebook.png

152 ms

twitter.png

twitter.png

152 ms

youtube.png

youtube.png

153 ms

gtm.js

gtm.js

75 ms

activityi;src=5295113;type=rtlfq0;cat=httpw0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1;num=4359259356278.9263

activityi;src=5295113;type=rtlfq0;cat=httpw0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1;num=4359259356278.9263

93 ms

translateelement.css

translateelement.css

87 ms

main.js

main.js

97 ms

bg_80ofOrig.png

bg_80ofOrig.png

96 ms

1.jpg

1.jpg

257 ms

collect

collect

26 ms

collect

collect

59 ms

collect

collect

22 ms

beacon_call.js

beacon_call.js

110 ms

welcome3.jpg

welcome3.jpg

380 ms

gis1.jpg

gis1.jpg

289 ms

element_main.js

element_main.js

47 ms

translate_24dp.png

translate_24dp.png

51 ms

l

l

39 ms

googlelogo_color_42x16dp.png

googlelogo_color_42x16dp.png

54 ms

beacon

beacon

23 ms

Accessibility Review

sandag.org accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

sandag.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sandag.org SEO score

83

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

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 Sandag.org 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 Sandag.org 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

sandag.org

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