Modot.Org - Info receives about 3,563 unique visitors and 6,770 (1.90 per visitor) page views per day which should earn about $73.61/day from advertising revenue. Estimated site value is $53,937.02. According to Alexa Traffic Rank is ranked number 285,801 in the world and 0.00021% of global Internet users visit it. Site is hosted in Columbus, Ohio, 43215, United States and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Web Servers
Font Scripts
Font Awesome
Tag Managers
Google Tag Manager
Programming Languages
PHP Profile

Title: Home Page | Missouri Department of Transportation
Description: Official site. Contains construction project information and news.
Keywords: Missouri Department of Transportation, MoDOT, Missouri Roads, Missouri Highways, Missouri Road Conditions, Missouri Work Zones, Missouri Government, Missouri Maps, Missouri Jobs, Missouri Travel, Branson Travel, Pete Rahn, St. Louis Road Conditions, Visiting Missouri, Kansas City Road Conditions, Springfield Road Conditions
Last update was 213 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

3.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
285,801 visit alexa
Alexa Reach:
0.00021%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

United States 94.8%94.8%65016

Where do visitors go on this site?


Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

United States 6,418$73.61

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 1,155$13.25

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
ISP:, Inc. 
Server Location:
Ohio, OH
United States, US

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
(641 ms) 92 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)2.8s 43% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 43% 43% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 43% 12% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 12%
First Input Delay (FID)6ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)2.3s 61% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 61% 30% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 30% 8% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 8%
First Input Delay (FID)7ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
200 ms3 ms1 ms
73 ms21 ms1 ms
61 ms58 ms3 ms
55 ms40 ms3 ms
Properly size images - Potential savings of 11 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
13 KB3 KB
12 KB3 KB
11 KB3 KB
8 KB2 KB
Remove unused CSS - Potential savings of 33 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
37 KB33 KB
Avoids enormous network payloads - Total size was 1,563 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

162 KB
157 KB
121 KB
100 KB
86 KB
85 KB
84 KB
83 KB
76 KB
75 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
136 ms
Style & Layout
123 ms
92 ms
Parse HTML & CSS
25 ms
21 ms
Script Parsing & Compilation
11 ms
Serve images in next-gen formats - Potential savings of 49 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
40 KB39 KB
34 KB11 KB
Avoid an excessive DOM size - 1,393 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 49 requests • 1,563 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
491563 KB
28920 KB
6402 KB
7136 KB
153 KB
450 KB
32 KB
00 KB
421433 KB
Eliminate render-blocking resources - Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
1 KB70
3 KB230
7 KB270
3 KB230
37 KB350
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms136 ms0 KB0 KB301text/html
136 ms344 ms53 KB185 KB200text/htmlDocument
355 ms444 ms1 KB0 KB200text/javascriptScript
355 ms371 ms3 KB10 KB200text/cssStylesheet
355 ms1478 ms7 KB30 KB200text/cssStylesheet
355 ms368 ms3 KB15 KB200text/cssStylesheet
356 ms396 ms37 KB274 KB200text/cssStylesheet
356 ms636 ms1 KB1 KB200image/svg+xmlImage
361 ms385 ms13 KB13 KB200image/jpegImage
457 ms481 ms8 KB8 KB200image/jpegImage
457 ms471 ms12 KB12 KB200image/jpegImage
457 ms471 ms12 KB11 KB200image/jpegImage
457 ms485 ms39 KB39 KB200image/jpegImage
457 ms479 ms4 KB4 KB200image/jpegImage
457 ms470 ms4 KB3 KB200image/jpegImage
457 ms496 ms4 KB4 KB200image/jpegImage
457 ms470 ms5 KB4 KB200image/jpegImage
457 ms483 ms18 KB23 KB200image/jpegImage
458 ms481 ms4 KB4 KB200image/jpegImage
458 ms489 ms5 KB4 KB200image/jpegImage
458 ms483 ms4 KB3 KB200image/jpegImage
458 ms499 ms4 KB4 KB200image/jpegImage
386 ms802 ms47 KB153 KB200text/javascriptScript
456 ms482 ms8 KB20 KB200application/javascriptScript
456 ms473 ms14 KB50 KB200text/javascriptScript
456 ms545 ms28 KB122 KB200text/javascriptScript
458 ms468 ms21 KB55 KB200application/javascriptScript
481 ms486 ms18 KB43 KB200text/javascriptScript
503 ms531 ms162 KB162 KB200image/jpegImage
505 ms538 ms100 KB100 KB200image/jpegImage
505 ms523 ms83 KB84 KB200image/jpegImage
506 ms533 ms157 KB157 KB200image/jpegImage
506 ms533 ms75 KB75 KB200image/jpegImage
506 ms547 ms121 KB121 KB200image/jpegImage
507 ms534 ms34 KB37 KB200image/jpegImage
507 ms518 ms2 KB2 KB200image/svg+xmlImage
508 ms530 ms1 KB1 KB200image/svg+xmlImage
510 ms528 ms40 KB53 KB200image/pngImage
510 ms534 ms6 KB10 KB200image/svg+xmlImage
510 ms539 ms86 KB86 KB200application/octet-streamFont
511 ms548 ms84 KB84 KB200application/octet-streamFont
511 ms538 ms85 KB84 KB200application/octet-streamFont
512 ms539 ms36 KB35 KB200application/octet-streamFont
532 ms560 ms36 KB35 KB200application/octet-streamFont>m=2wgaa0TF6G5C6&z=1046605440
563 ms585 ms1 KB0 KB302text/html
585 ms608 ms1 KB0 KB302text/html
608 ms617 ms1 KB0 KB200image/gifImage
1509 ms1530 ms76 KB75 KB200font/woff2Font
1640 ms1715 ms1 KB1 KB200image/svg+xmlImage
Uses efficient cache policy on static assets - 6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
7200000 ms18 KB
1209600000 ms47 KB
1209600000 ms28 KB
1209600000 ms1 KB
1209600000 ms1 KB
1209600000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

SizeMain-Thread Blocking Time
97 KB0 ms
21 KB0 ms
19 KB0 ms
8 KB0 ms
1 KB0 ms
1 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
370 ms
6 ms
469 ms
20 ms
500 ms
6 ms
514 ms
74 ms
611 ms
6 ms
617 ms
7 ms
624 ms
7 ms
1505 ms
18 ms
1524 ms
36 ms
1563 ms
6 ms
1569 ms
6 ms
1575 ms
34 ms
1609 ms
97 ms
1706 ms
8 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
22 ms
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Avoid chaining critical requests - 10 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 210 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

52.5KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. Prioritize the above-the-fold content so that it can be rendered with only the first 2 round-trips' worth of HTML.

Only about 38% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.
Click to see the screenshot with 2 round trips:

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 59.3KiB (48% reduction).

Compressing could save 51.1KiB (96% reduction).
Compressing***0.png.jpg?itok=X3rLL5hy could save 3.7KiB (11% reduction).
Compressing could save 2.9KiB (13% reduction).
Compressing could save 519B (16% reduction).
Compressing could save 402B (12% reduction).
Compressing could save 401B (11% reduction).
Compressing could save 383B (12% reduction).

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 422 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <div class="alert">Flooding Infor…t information.</div> falls outside the viewport.
The element <ul class="social-media-l…ine horizontal">Instagram…Facebook</ul> falls outside the viewport.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (15 minutes)******ytics.js (2 hours)

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <li class="slick-active">1</li> and 5 others are close to other tap targets.
The tap target <button id="slick-slide-control00" type="button">1</button> is close to 1 other tap targets.
The tap target <button id="slick-slide-control01" type="button">2</button> and 4 others are close to other tap targets.
The tap target <a href="tel:18882756636">1-888-ASK-MODOT (275-6636)</a> and 1 others are close to other tap targets.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 184.94 KB
Compressed size: 51.46 KB
File reduced by: 133.48 KB (72%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Amazon
Valid from: Oct 4 00:00:00 2019 GMT
Valid until: Nov 4 12:00:00 2020 GMT

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

United States/Missouri

+ Http Header

Date: Mon, 28 Oct 2019 11:02:38 GMT
Server: Apache/2.4.39 () OpenSSL/1.0.2k-fips
Content-Length: 230
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Cache-Control: max-age=3600, public
Cache-control: no-cache="set-cookie"
Content-Encoding: gzip
Content-language: en
Content-Type: text/html; charset=UTF-8
Date: Mon, 28 Oct 2019 11:02:39 GMT
ETag: "1572042007-gzip"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Fri, 25 Oct 2019 22:20:07 GMT
Link: <>; rel="shortlink", <>; rel="canonical"
Link: <//>; rel=preconnect; crossorigin
Link: <//>; rel=dns-prefetch
Server: Apache
Set-Cookie: AWSELB=13E3B5FF1EBB67AF1A352B396396B0C69A6689755EAADAC521394FC5BAA9E9BF6B45FC041146034F986C720D2241F583BF41F44749FB61395AA36CA33FAD8872FBC06F3DEE;PATH=/;MAX-AGE=1800
Vary: Cookie,Accept-Encoding,User-Agent
X-Content-Type-Options: nosniff
X-Content-Type-Options: nosniff
x-dns-prefetch-control: on
X-Drupal-Cache: HIT
X-Drupal-Dynamic-Cache: MISS
X-Frame-Options: SAMEORIGIN
X-Generator: Drupal 8 (
X-UA-Compatible: IE=edge
Content-Length: 52696
Connection: keep-alive

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
Domain Age:
18 years 9 months 19 days  

whois lookup at
Domain Name: MODOT.ORG
Registry Domain ID: D51423847-LROR
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-03-28T12:48:16Z
Creation Date: 2001-01-09T16:13:59Z
Registry Expiry Date: 2029-01-09T16:13:59Z
Registrar Registration Expiration Date:
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8003337680
Domain Status: clientTransferProhibited
Registrant Organization:
Registrant State/Province: FL
Registrant Country: US
Name Server: NS1.MODOT.MO.GOV
Name Server: NS2.MODOT.MO.GOV
Name Server: NS3.MODOT.MO.GOV
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form
>>> Last update of WHOIS database: 2019-10-28T11:03:24Z <<<

For more information on Whois status codes, please visit

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 213 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget