2.2 sec in total
171 ms
1.7 sec
372 ms
Visit freightcom.com now to see the best up-to-date Freightcom content for Canada and also check out these interesting facts you probably never knew about freightcom.com
Get better muti-carrier, multi-mode, and eCommerce shipping on domestic Canada, cross-border, and international LTL Pallet and Parcel, all in one total shipping solution!
Visit freightcom.comWe analyzed Freightcom.com page load time and found that the first response time was 171 ms and then it took 2 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.
freightcom.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value16.0 s
0/100
25%
Value8.9 s
15/100
10%
Value1,760 ms
10/100
30%
Value0.028
100/100
15%
Value23.9 s
1/100
10%
171 ms
117 ms
68 ms
87 ms
87 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 75% of them (59 requests) were addressed to the original Freightcom.com, 5% (4 requests) were made to Google-analytics.com and 5% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (534 ms) belongs to the original domain Freightcom.com.
Page size can be reduced by 687.3 kB (50%)
1.4 MB
674.0 kB
In fact, the total size of Freightcom.com 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. 70% of websites need less resources to load. Javascripts take 490.7 kB which makes up the majority of the site volume.
Potential reduce by 35.3 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 35.3 kB or 80% of the original size.
Potential reduce by 27.4 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. Freightcom images are well optimized though.
Potential reduce by 303.6 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 303.6 kB or 62% of the original size.
Potential reduce by 320.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. Freightcom.com needs all CSS files to be minified and compressed as it can save up to 320.9 kB or 84% of the original size.
Number of requests can be reduced by 36 (48%)
75
39
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freightcom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
freightcom.com
171 ms
bootstrap.css
117 ms
style.css
68 ms
bootstrap.min.js
87 ms
stepcarousel.js
87 ms
snapEngage.js
70 ms
jquery-1.8.2.min.js
151 ms
jquery.carouFredSel-6.2.1-packed.js
176 ms
jquery.meanmenu.js
108 ms
city.js
107 ms
orderManager.js
106 ms
home.css
174 ms
AC_RunActiveContent.js
229 ms
SpryMenuBar.js
229 ms
ffdb69bf-1731-4e5a-8571-6767176efadb.js
382 ms
gtm.js
193 ms
analytics.js
191 ms
freightcom-logo.png
131 ms
g.png
130 ms
linkedin-icon.png
129 ms
google+-icon.png
123 ms
facebook-icon.png
128 ms
twitter-icon.png
127 ms
image008.jpg
170 ms
image009.jpg
170 ms
image010.jpg
161 ms
image012.jpg
160 ms
image016.png
159 ms
image017.jpg
158 ms
pre.png
282 ms
next.png
283 ms
a1.jpg
277 ms
a2.jpg
276 ms
a3.jpg
277 ms
a4.jpg
276 ms
a7.jpg
284 ms
a8.jpg
277 ms
clearlane.png
277 ms
DNR.png
278 ms
fedex.jpg
278 ms
Frontline.png
282 ms
Newpenn.jpg
282 ms
Polaris.jpg
283 ms
Purolator.png
281 ms
Speedy.png
279 ms
Wilson.png
279 ms
TST.jpg
283 ms
Yrc.png
283 ms
NEMF.png
285 ms
MTS.png
280 ms
TLS.jpg
283 ms
GOJIT_ORG.png
282 ms
SHIFT_Original.png
283 ms
player_api
194 ms
Front%20Line.png
195 ms
CCT_ORG.png
195 ms
bluegridheader-img.jpg
491 ms
truckflaghand-header-img.png
534 ms
telephone-icon.png
196 ms
logbg.jpg
449 ms
customerlogin-bg.png
447 ms
collect
349 ms
collect
326 ms
conversion_async.js
299 ms
collect
92 ms
footbg1.jpg
133 ms
www-widgetapi.js
136 ms
chat.png
330 ms
blank.gif
41 ms
85 ms
JCgBd9iX58g
85 ms
137 ms
www-embed-player-vflfNyN_r.css
28 ms
www-embed-player.js
77 ms
base.js
123 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
24 ms
ad_status.js
48 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
100 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
100 ms
freightcom.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
freightcom.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
freightcom.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freightcom.com 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 Freightcom.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.
freightcom.com
Open Graph description is not detected on the main page of Freightcom. 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: