Tools & Wizards About Us
vanderhaags.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

vanderhaags.com

Used Heavy Duty Truck Parts | Quality Semi Truck Salvage

Page Load Speed

3 sec in total

First Response

60 ms

Resources Loaded

2.5 sec

Page Rendered

402 ms

vanderhaags.com screenshot

About Website

Welcome to vanderhaags.com homepage info - get ready to check Vanderhaags best content for United States right away, or after learning these important things about vanderhaags.com

Vander Haag's is your destination for high quality new and used heavy duty truck parts, semi truck salvage, trucks, trailers, equipment and service. Give us a call today.

Visit vanderhaags.com

Key Findings

We analyzed Vanderhaags.com page load time and found that the first response time was 60 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

vanderhaags.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

65/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

vanderhaags.com

60 ms

www.vanderhaags.com

57 ms

index.php

82 ms

jquery.mmenu.all.css

33 ms

vh.css

62 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 88% of them (80 requests) were addressed to the original Vanderhaags.com, 2% (2 requests) were made to Verify.authorize.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Vanderhaags.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 506.2 kB (28%)

Content Size

1.8 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vanderhaags.com main page is 1.8 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 68.4 kB

  • Original 81.7 kB
  • After minification 72.4 kB
  • After compression 13.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 9.3 kB, which is 11% 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 68.4 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 34.7 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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. Vanderhaags images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 209.9 kB

  • Original 331.7 kB
  • After minification 318.7 kB
  • After compression 121.8 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 209.9 kB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 193.2 kB

  • Original 225.5 kB
  • After minification 205.4 kB
  • After compression 32.2 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. Vanderhaags.com needs all CSS files to be minified and compressed as it can save up to 193.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (22%)

Requests Now

86

After Optimization

67

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vanderhaags.com

vanderhaags.com

60 ms

www.vanderhaags.com

www.vanderhaags.com

57 ms

index.php

index.php

82 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

33 ms

vh.css

vh.css

62 ms

normalize.min.css

normalize.min.css

69 ms

foundation.min.css

foundation.min.css

94 ms

materialdesigncss.css

materialdesigncss.css

72 ms

css

css

77 ms

jquery.min.js

jquery.min.js

10 ms

hammer.min.js

hammer.min.js

69 ms

jquery.mmenu.dragopen.min.js

jquery.mmenu.dragopen.min.js

72 ms

jquery.mmenu.min.all.js

jquery.mmenu.min.all.js

86 ms

modernizr.js

modernizr.js

85 ms

materialdesignjs.js

materialdesignjs.js

86 ms

jquery.carouFredSel-6.2.1-packed.min.js

jquery.carouFredSel-6.2.1-packed.min.js

329 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

88 ms

jquery.transit.min.js

jquery.transit.min.js

354 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

356 ms

foundation.min.js

foundation.min.js

355 ms

seal.js

seal.js

51 ms

conversion.js

conversion.js

46 ms

secure90x72.gif

secure90x72.gif

411 ms

analytics.js

analytics.js

404 ms

sprites.png

sprites.png

304 ms

truckshome.png

truckshome.png

504 ms

engine.png

engine.png

302 ms

truck.png

truck.png

304 ms

trailer.png

trailer.png

302 ms

equipment.png

equipment.png

286 ms

display.php

display.php

352 ms

display.php

display.php

474 ms

display.php

display.php

405 ms

display.php

display.php

368 ms

display.php

display.php

435 ms

display.php

display.php

507 ms

display.php

display.php

452 ms

display.php

display.php

558 ms

display.php

display.php

523 ms

display.php

display.php

623 ms

display.php

display.php

589 ms

display.php

display.php

721 ms

display.php

display.php

653 ms

display.php

display.php

686 ms

display.php

display.php

750 ms

display.php

display.php

782 ms

display.php

display.php

818 ms

display.php

display.php

890 ms

display.php

display.php

853 ms

display.php

display.php

912 ms

display.php

display.php

948 ms

display.php

display.php

982 ms

display.php

display.php

1000 ms

display.php

display.php

1036 ms

display.php

display.php

1060 ms

display.php

display.php

1093 ms

display.php

display.php

1095 ms

display.php

display.php

1128 ms

display.php

display.php

1121 ms

182 ms

display.php

display.php

976 ms

collect

collect

12 ms

collect

collect

62 ms

38 ms

display.php

display.php

1089 ms

display.php

display.php

1108 ms

display.php

display.php

977 ms

display.php

display.php

940 ms

display.php

display.php

1040 ms

display.php

display.php

958 ms

display.php

display.php

1128 ms

display.php

display.php

1263 ms

display.php

display.php

1200 ms

display.php

display.php

988 ms

display.php

display.php

1098 ms

display.php

display.php

1012 ms

display.php

display.php

1167 ms

display.php

display.php

1375 ms

display.php

display.php

1212 ms

display.php

display.php

1149 ms

display.php

display.php

1107 ms

display.php

display.php

1276 ms

display.php

display.php

1156 ms

display.php

display.php

1090 ms

vhiqr.png

vhiqr.png

1011 ms

carlogov3.png

carlogov3.png

1005 ms

aralogo.png

aralogo.png

978 ms

icarelogo.png

icarelogo.png

958 ms

itpalogo.png

itpalogo.png

932 ms

iarlogo.png

iarlogo.png

923 ms

chartbeat.js

chartbeat.js

20 ms

Accessibility Review

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

vanderhaags.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

vanderhaags.com SEO score

90

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vanderhaags.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 Vanderhaags.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

vanderhaags.com

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