9.2 sec in total
3.5 sec
5.5 sec
145 ms
Click here to check amazing Traffic Truth content. Otherwise, check out these important facts you probably never knew about traffictruth.net
Another tax won't help your traffic jam. Stop the largest tax increase in Georgia history. Vote NO on July 31, Regional Transportation Referendum.
Visit traffictruth.netWe analyzed Traffictruth.net page load time and found that the first response time was 3.5 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
traffictruth.net performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value12.7 s
0/100
25%
Value15.0 s
1/100
10%
Value5,800 ms
0/100
30%
Value0.324
35/100
15%
Value14.2 s
9/100
10%
3485 ms
1273 ms
79 ms
43 ms
49 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original Traffictruth.net, 3% (2 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Traffictruth.net.
Page size can be reduced by 571.9 kB (40%)
1.4 MB
865.5 kB
In fact, the total size of Traffictruth.net main page is 1.4 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. Javascripts take 648.3 kB which makes up the majority of the site volume.
Potential reduce by 27.8 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 27.8 kB or 74% of the original size.
Potential reduce by 13.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. Traffic Truth images are well optimized though.
Potential reduce by 424.9 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 424.9 kB or 66% of the original size.
Potential reduce by 106.1 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. Traffictruth.net needs all CSS files to be minified and compressed as it can save up to 106.1 kB or 83% of the original size.
Number of requests can be reduced by 32 (73%)
44
12
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traffic Truth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
traffictruth.net
3485 ms
www.traffictruth.net
1273 ms
foundation.css
79 ms
app.css
43 ms
shortcode.css
49 ms
elements.css
43 ms
style.css
46 ms
light.css
66 ms
css
19 ms
general.css
104 ms
event.css
77 ms
style.css
71 ms
styles.css
110 ms
style.css
98 ms
cirrusCloud.css
100 ms
jquery.js
117 ms
jquery-migrate.min.js
106 ms
event.min.js
107 ms
wp_cirrus_gwt.nocache.js
107 ms
jquery.orbit.js
136 ms
app.js
138 ms
jquery.placeholder.min.js
139 ms
jquery.reveal.js
141 ms
jquery.tooltips.js
217 ms
modernizr.foundation.js
137 ms
menu.js
139 ms
mobilemenu.js
154 ms
jquery.lazyload.js
156 ms
general.min.js
157 ms
cssstyles.css
155 ms
addthis_widget.js
9 ms
jquery.form.js
151 ms
scripts.js
151 ms
core.min.js
213 ms
widget.min.js
211 ms
tabs.min.js
242 ms
wp-embed.min.js
211 ms
wp-emoji-release.min.js
127 ms
ga.js
86 ms
plusone.js
130 ms
traffic-truth-logo5.png
82 ms
facebook.png
82 ms
twitter.png
73 ms
flickr.png
80 ms
sliderbg.jpg
79 ms
spinner.gif
97 ms
slide4-repeal-regionalism-980x330.png
460 ms
slide1-stop-tax-incr-0517121.jpg
446 ms
slide3-truth-v-fict-051012.png
553 ms
trafficTruthCar.png
399 ms
trafficTruthOwnWords.png
399 ms
trafficTruthGeorgia.png
154 ms
trafficTruthGoliath.png
211 ms
achimps.png
274 ms
_ate.track.config_resp
32 ms
300lo.json
47 ms
19CF2CFAEA361BC9322AB6BA0049A1EC.cache.html
353 ms
sh.48536d49e4da3bdba54606b4.html
38 ms
__utm.gif
27 ms
cb=gapi.loaded_0
5 ms
pixel
20 ms
pixel
13 ms
match-result
2 ms
traffictruth.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
traffictruth.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
traffictruth.net SEO score
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traffictruth.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Traffictruth.net 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.
traffictruth.net
Open Graph description is not detected on the main page of Traffic Truth. 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: