Tools & Wizards About Us
columbiafreightliner.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

columbiafreightliner.com

Commercial Trucks & Semi-Truck Dealerships | Premier Truck Group Serving all of North America

Page Load Speed

2.3 sec in total

First Response

28 ms

Resources Loaded

742 ms

Page Rendered

1.6 sec

columbiafreightliner.com screenshot

About Website

Click here to check amazing Columbiafreightliner content. Otherwise, check out these important facts you probably never knew about columbiafreightliner.com

With locations in the United States and Canada the Premier Truck Group is the best place to purchase your next vehicle, obtain quality service, purchase all makes of truck parts, or even have paint an...

Visit columbiafreightliner.com

Key Findings

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

columbiafreightliner.com performance score

0

Network Requests Diagram

columbiafreightliner.com

28 ms

www.premiertruck.com

182 ms

foundation.css

52 ms

font-icons.css

53 ms

foundation-theme.css

54 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Columbiafreightliner.com, 57% (37 requests) were made to Images.ebizautos.media and 14% (9 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Images.ebizautos.media.

Page Optimization Overview & Recommendations

Page size can be reduced by 760.2 kB (35%)

Content Size

2.2 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Columbiafreightliner.com main page is 2.2 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. 75% 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. Images take 819.8 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 679.1 kB

  • Original 761.5 kB
  • After minification 623.6 kB
  • After compression 82.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. This page needs HTML code to be minified as it can gain 137.9 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 679.1 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 87 B

  • Original 819.8 kB
  • After minification 819.7 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. Columbiafreightliner images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 81.0 kB

  • Original 586.7 kB
  • After minification 586.7 kB
  • After compression 505.7 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 81.0 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (67%)

Requests Now

58

After Optimization

19

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

columbiafreightliner.com

columbiafreightliner.com

28 ms

www.premiertruck.com

www.premiertruck.com

182 ms

foundation.css

foundation.css

52 ms

font-icons.css

font-icons.css

53 ms

foundation-theme.css

foundation-theme.css

54 ms

responsive.css

responsive.css

60 ms

custom.css

custom.css

51 ms

blocker.js

blocker.js

47 ms

jquery.min.js

jquery.min.js

60 ms

jquery.cookie.min.js

jquery.cookie.min.js

70 ms

pas-common.min.js

pas-common.min.js

71 ms

pas-client.min.js

pas-client.min.js

70 ms

pag_custom_tracking.js

pag_custom_tracking.js

72 ms

global.js

global.js

81 ms

gallery.js

gallery.js

88 ms

js

js

87 ms

js

js

188 ms

vehicles_info_manager.js

vehicles_info_manager.js

87 ms

banner.js

banner.js

66 ms

jquery-cycle2.js

jquery-cycle2.js

72 ms

slick.js

slick.js

157 ms

plugins-main.js

plugins-main.js

216 ms

functions-main.js

functions-main.js

157 ms

jquery.validate.js

jquery.validate.js

156 ms

3130.js

3130.js

40 ms

siteanalyze_84218.js

siteanalyze_84218.js

50 ms

conversion.js

conversion.js

56 ms

pageview.min.js

pageview.min.js

144 ms

swiper-bundle.js

swiper-bundle.js

156 ms

functions-swiper-fv2.js

functions-swiper-fv2.js

156 ms

owl-plugins.js

owl-plugins.js

271 ms

functions-home-owl-carousel.js

functions-home-owl-carousel.js

272 ms

functions-pas-dashboard.js

functions-pas-dashboard.js

269 ms

leads.js

leads.js

269 ms

gtm.js

gtm.js

133 ms

analytics.js

analytics.js

115 ms

gtm.js

gtm.js

220 ms

gtm.js

gtm.js

241 ms

gtm.js

gtm.js

219 ms

gtm.js

gtm.js

261 ms

gtm.js

gtm.js

274 ms

DPA8K-Promo_2024JUL_Header-Home.jpg

DPA8K-Promo_2024JUL_Header-Home.jpg

245 ms

insight.min.js

insight.min.js

233 ms

fbevents.js

fbevents.js

229 ms

widget.js

widget.js

227 ms

219 ms

sp.gif

sp.gif

152 ms

logo.png

logo.png

197 ms

logo@2x.png

logo@2x.png

200 ms

hero-d.jpg

hero-d.jpg

217 ms

cascadia-logo.png

cascadia-logo.png

200 ms

hero-bg-d.jpg

hero-bg-d.jpg

217 ms

home-hero-logo-freightliner.png

home-hero-logo-freightliner.png

199 ms

home-hero-logo-western-star.png

home-hero-logo-western-star.png

220 ms

home-hero-logo-thomas-built-buses.png

home-hero-logo-thomas-built-buses.png

271 ms

home-hero-logo-isuzu.png

home-hero-logo-isuzu.png

273 ms

PTG-ONE-homepagee-banner-desktop.jpg

PTG-ONE-homepagee-banner-desktop.jpg

275 ms

PTG-ONE-homepagee-banner-mobile.jpg

PTG-ONE-homepagee-banner-mobile.jpg

272 ms

49-bg.jpg

49-bg.jpg

274 ms

collect

collect

103 ms

collect

collect

124 ms

js

js

81 ms

widget_app_1730455764190.js

widget_app_1730455764190.js

183 ms

68 ms

insight_tag_errors.gif

insight_tag_errors.gif

71 ms

SEO Factors

columbiafreightliner.com SEO score

0

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

columbiafreightliner.com

Open Graph description is not detected on the main page of Columbiafreightliner. 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: