Tools & Wizards About Us
canalcartage.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

canalcartage.com

Canal Cartage | Commercial Freight Services | Houston, TX

Page Load Speed

2.4 sec in total

First Response

34 ms

Resources Loaded

860 ms

Page Rendered

1.6 sec

canalcartage.com screenshot

About Website

Click here to check amazing Canal Cartage content for United States. Otherwise, check out these important facts you probably never knew about canalcartage.com

Canal Cartage provides commercial freight services of cross-dock, warehouse storage, trans-loading, and container drayage for Texas.

Visit canalcartage.com

Key Findings

We analyzed Canalcartage.com page load time and found that the first response time was 34 ms and then it took 2.4 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

canalcartage.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value5,040 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

canalcartage.com

34 ms

canalcartage.com

115 ms

formidableforms.css

58 ms

style.css

70 ms

toolbar.css

78 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 85% of them (75 requests) were addressed to the original Canalcartage.com, 7% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (412 ms) relates to the external source Maps.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.6 kB (12%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Canalcartage.com main page is 1.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 905.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 189.6 kB

  • Original 230.8 kB
  • After minification 230.7 kB
  • After compression 41.2 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 189.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 1.9 kB

  • Original 344.7 kB
  • After minification 342.8 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. Canal Cartage images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.1 kB

  • Original 905.0 kB
  • After minification 905.0 kB
  • After compression 902.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 990 B

  • Original 127.0 kB
  • After minification 127.0 kB
  • After compression 126.0 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. Canalcartage.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 75 (94%)

Requests Now

80

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

canalcartage.com

canalcartage.com

34 ms

canalcartage.com

canalcartage.com

115 ms

formidableforms.css

formidableforms.css

58 ms

style.css

style.css

70 ms

toolbar.css

toolbar.css

78 ms

style.min.css

style.min.css

79 ms

theme.min.css

theme.min.css

69 ms

header-footer.min.css

header-footer.min.css

78 ms

frontend-lite.min.css

frontend-lite.min.css

84 ms

post-2483.css

post-2483.css

84 ms

swiper.min.css

swiper.min.css

79 ms

wp_social_ninja_reviews.css

wp_social_ninja_reviews.css

91 ms

frontend-lite.min.css

frontend-lite.min.css

95 ms

post-19.css

post-19.css

90 ms

post-2482.css

post-2482.css

97 ms

post-2500.css

post-2500.css

107 ms

jquery.min.js

jquery.min.js

119 ms

jquery-migrate.min.js

jquery-migrate.min.js

112 ms

wpgmza_data.js

wpgmza_data.js

111 ms

analytics-talk-content-tracking.js

analytics-talk-content-tracking.js

105 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

104 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

112 ms

widget-icon-list.min.css

widget-icon-list.min.css

160 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

161 ms

css

css

112 ms

all.css

all.css

94 ms

fa-4to5.css

fa-4to5.css

222 ms

common.css

common.css

224 ms

remodal.css

remodal.css

223 ms

remodal-default-theme.css

remodal-default-theme.css

226 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

227 ms

components.css

components.css

228 ms

compat.css

compat.css

230 ms

owl.carousel.min.css

owl.carousel.min.css

231 ms

owl.theme.default.min.css

owl.theme.default.min.css

232 ms

carousel_sky.css

carousel_sky.css

234 ms

featherlight.min.css

featherlight.min.css

233 ms

dataTables.responsive.css

dataTables.responsive.css

235 ms

pagination.css

pagination.css

237 ms

element.js

element.js

221 ms

api.js

api.js

106 ms

js

js

412 ms

components.css

components.css

337 ms

scripts.js

scripts.js

179 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

300 ms

hello-frontend.min.js

hello-frontend.min.js

300 ms

jquery.sticky.min.js

jquery.sticky.min.js

299 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

297 ms

swiper-bundle.min.js

swiper-bundle.min.js

298 ms

wp-social-review.js

wp-social-review.js

297 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

289 ms

dataTables.responsive.js

dataTables.responsive.js

288 ms

jquery-cookie.js

jquery-cookie.js

286 ms

remodal.min.js

remodal.min.js

284 ms

pep.js

pep.js

285 ms

text.js

text.js

322 ms

pako_deflate.min.js

pako_deflate.min.js

313 ms

wp-google-maps-pro.min.js

wp-google-maps-pro.min.js

328 ms

owl.carousel.js

owl.carousel.js

308 ms

featherlight.min.js

featherlight.min.js

332 ms

polyline.js

polyline.js

327 ms

core.min.js

core.min.js

381 ms

gtm.js

gtm.js

305 ms

mouse.min.js

mouse.min.js

336 ms

sortable.min.js

sortable.min.js

270 ms

pagination.min.js

pagination.min.js

267 ms

CanvasLayerOptions.js

CanvasLayerOptions.js

266 ms

CanvasLayer.js

CanvasLayer.js

265 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

304 ms

webpack.runtime.min.js

webpack.runtime.min.js

302 ms

frontend-modules.min.js

frontend-modules.min.js

298 ms

hooks.min.js

hooks.min.js

338 ms

i18n.min.js

i18n.min.js

298 ms

frontend.min.js

frontend.min.js

298 ms

waypoints.min.js

waypoints.min.js

336 ms

frontend.min.js

frontend.min.js

335 ms

elements-handlers.min.js

elements-handlers.min.js

335 ms

lazyload.min.js

lazyload.min.js

333 ms

Canal-Cartage-Logo-Transparent-Large.png

Canal-Cartage-Logo-Transparent-Large.png

355 ms

Canal-Cartage-Company-Warehouse-1.png

Canal-Cartage-Company-Warehouse-1.png

356 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

170 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

246 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

280 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

282 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

282 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

281 ms

flags18.png

flags18.png

228 ms

recaptcha__en.js

recaptcha__en.js

190 ms

Accessibility Review

canalcartage.com accessibility score

91

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

Best Practices

canalcartage.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

canalcartage.com SEO score

75

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

High

Image elements do not have [alt] attributes

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 Canalcartage.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 Canalcartage.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.

Social Sharing Optimization

canalcartage.com

Open Graph data is detected on the main page of Canal Cartage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: