Tools & Wizards About Us

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

planning.dot.gov

Transportation Planning Capacity Building - Transportation Planning Capacity Building Program

Page Load Speed

2.5 sec in total

First Response

305 ms

Resources Loaded

2 sec

Page Rendered

247 ms

About Website

Click here to check amazing Planning Dot content for United States. Otherwise, check out these important facts you probably never knew about planning.dot.gov

The Transportation Planning Capacity Building Program (TPCB) is your source for transportaion planning resources. Search our planning resources database.

Visit planning.dot.gov

Key Findings

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

Performance Metrics

planning.dot.gov performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

planning.dot.gov

305 ms

planning.dot.gov

225 ms

www.planning.dot.gov

237 ms

js

67 ms

bootstrap.min.css

49 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 67% of them (29 requests) were addressed to the original Planning.dot.gov, 9% (4 requests) were made to Fhwa.dot.gov and 9% (4 requests) were made to Search.usa.gov. The less responsive or slowest element that took the longest time to load (895 ms) belongs to the original domain Planning.dot.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 585.2 kB (17%)

Content Size

3.5 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planning.dot.gov main page is 3.5 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. 45% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 17.5 kB

  • Original 21.9 kB
  • After minification 15.8 kB
  • After compression 4.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.1 kB, which is 28% 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 17.5 kB or 80% of the original size.

Image Optimization

-16%

Potential reduce by 533.3 kB

  • Original 3.3 MB
  • After minification 2.8 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. Obviously, Planning Dot needs image optimization as it can save up to 533.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 20.5 kB

  • Original 135.1 kB
  • After minification 135.1 kB
  • After compression 114.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 20.5 kB or 15% of the original size.

CSS Optimization

-33%

Potential reduce by 14.0 kB

  • Original 42.9 kB
  • After minification 42.9 kB
  • After compression 28.9 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. Planning.dot.gov needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 33% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

planning.dot.gov accessibility score

87

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

planning.dot.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

planning.dot.gov 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 Planning.dot.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 Planning.dot.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

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