1.3 sec in total
85 ms
730 ms
504 ms
Welcome to passport.freightwaves.com homepage info - get ready to check Passport Freight Waves best content for United States right away, or after learning these important things about passport.freightwaves.com
Freight market intelligence and survey-driven logistics research written by indusry experts. Our research comes from our data intelligence platform, SONAR.
Visit passport.freightwaves.comWe analyzed Passport.freightwaves.com page load time and found that the first response time was 85 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.
passport.freightwaves.com performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value9.8 s
0/100
25%
Value6.9 s
33/100
10%
Value4,550 ms
0/100
30%
Value0.101
89/100
15%
Value23.6 s
1/100
10%
85 ms
128 ms
15 ms
56 ms
90 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 85% of them (35 requests) were addressed to the original Passport.freightwaves.com, 7% (3 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Olytics.omeda.com. The less responsive or slowest element that took the longest time to load (333 ms) belongs to the original domain Passport.freightwaves.com.
Page size can be reduced by 136.2 kB (14%)
961.6 kB
825.4 kB
In fact, the total size of Passport.freightwaves.com main page is 961.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 410.1 kB which makes up the majority of the site volume.
Potential reduce by 134.9 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 134.9 kB or 82% of the original size.
Potential reduce by 2 B
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. Passport Freight Waves images are well optimized though.
Potential reduce by 571 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 776 B
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. Passport.freightwaves.com has all CSS files already compressed.
Number of requests can be reduced by 29 (78%)
37
8
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Passport Freight Waves. 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 19 to 1 for CSS and as a result speed up the page load time.
passport.freightwaves.com
85 ms
passport.freightwaves.com
128 ms
theme.css
15 ms
style.min.css
56 ms
tribe-events-single-skeleton.min.css
90 ms
tribe-events-single-full.min.css
35 ms
widget-base.min.css
60 ms
style.min.css
33 ms
js_composer.min.css
38 ms
frontend.min.css
60 ms
css
58 ms
frontend.min.css
111 ms
js-composer-frontend.css
61 ms
elementor-frontend.css
66 ms
style.css
67 ms
darkmode.css
107 ms
scheme.css
69 ms
plugin.css
92 ms
plugin.css
84 ms
jquery.min.js
86 ms
jquery-migrate.min.js
101 ms
css
54 ms
css
54 ms
gtm4wp-form-move-tracker.js
98 ms
comment-reply.min.js
333 ms
hoverIntent.min.js
107 ms
imagesloaded.min.js
329 ms
frontend.min.js
331 ms
plugin.js
329 ms
plugin.js
330 ms
js_composer_front.min.js
331 ms
olytics.min.js
189 ms
gtm.js
278 ms
FW-Passport-Web-White-Small.png
111 ms
preloader-dark.gif
176 ms
FW-SONAR-Rocky-Road-2023-Feature-1140x642.jpg
109 ms
FW-Passport-Stamp-BG-Blue-v2@72dpi-ignore.jpg
174 ms
jeg-empty.png
110 ms
font
108 ms
fontawesome-webfont.woff
154 ms
jegicon.woff
103 ms
passport.freightwaves.com accessibility score
passport.freightwaves.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
passport.freightwaves.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Passport.freightwaves.com 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 Passport.freightwaves.com 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.
passport.freightwaves.com
Open Graph data is detected on the main page of Passport Freight Waves. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: