Tools & Wizards About Us
drayage.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

drayage.com

the Drayage Directory - Intermodal Container Trucking Transportation by Metro Marketplace (for Rail and Port Terminals)

Page Load Speed

1.8 sec in total

First Response

435 ms

Resources Loaded

1.2 sec

Page Rendered

166 ms

drayage.com screenshot

About Website

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

A directory of Drayage Transpotation Trucking Companies for moving Import Export Ocean and Intermodal Rail Containers. Search by Metro Marketplace for Draymen that interchange from Port and Rail Termi...

Visit drayage.com

Key Findings

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

Performance Metrics

drayage.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

drayage.com

435 ms

style.css

177 ms

DrayageDirectory_logo.jpg

264 ms

clr.gif

176 ms

truckNEWsml2.jpg

432 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 19% of them (9 requests) were addressed to the original Drayage.com, 42% (20 requests) were made to Static.xx.fbcdn.net and 23% (11 requests) were made to Loadmatch.com. The less responsive or slowest element that took the longest time to load (679 ms) relates to the external source Loadmatch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 77.0 kB (48%)

Content Size

158.9 kB

After Optimization

82.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Drayage.com main page is 158.9 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. 55% of websites need less resources to load. Images take 131.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 14.9 kB

  • Original 20.5 kB
  • After minification 20.1 kB
  • After compression 5.6 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 14.9 kB or 73% of the original size.

Image Optimization

-43%

Potential reduce by 56.9 kB

  • Original 131.9 kB
  • After minification 75.0 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. Obviously, Drayage needs image optimization as it can save up to 56.9 kB or 43% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-79%

Potential reduce by 5.2 kB

  • Original 6.6 kB
  • After minification 5.0 kB
  • After compression 1.4 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. Drayage.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (49%)

Requests Now

47

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drayage. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

drayage.com

drayage.com

435 ms

style.css

style.css

177 ms

DrayageDirectory_logo.jpg

DrayageDirectory_logo.jpg

264 ms

clr.gif

clr.gif

176 ms

truckNEWsml2.jpg

truckNEWsml2.jpg

432 ms

liftpicsml.jpg

liftpicsml.jpg

417 ms

demotrainsml2.jpg

demotrainsml2.jpg

675 ms

all.js

all.js

7 ms

PPTimg.png

PPTimg.png

679 ms

icon_pdf.gif

icon_pdf.gif

330 ms

curve-blk.gif

curve-blk.gif

341 ms

IN.gif

IN.gif

315 ms

T.gif

T.gif

558 ms

F.gif

F.gif

563 ms

NCBFAA.gif

NCBFAA.gif

563 ms

IANAsml.gif

IANAsml.gif

558 ms

TIAsml.gif

TIAsml.gif

563 ms

bgBdk.gif

bgBdk.gif

90 ms

bgBlt.gif

bgBlt.gif

89 ms

bgGlt.gif

bgGlt.gif

89 ms

bgShdwBot.gif

bgShdwBot.gif

312 ms

134 ms

xd_arbiter.php

xd_arbiter.php

33 ms

xd_arbiter.php

xd_arbiter.php

43 ms

like_box.php

like_box.php

210 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

28 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

34 ms

Czh0gDTFcBt.css

Czh0gDTFcBt.css

28 ms

Ek6lpayKeeB.css

Ek6lpayKeeB.css

47 ms

EoarYgA68t4.css

EoarYgA68t4.css

38 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

46 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

70 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

32 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

80 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

82 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

80 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

86 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

92 ms

1FCa-btixu2.js

1FCa-btixu2.js

78 ms

10649872_943612082322548_2283640365784092456_n.jpg

10649872_943612082322548_2283640365784092456_n.jpg

120 ms

safe_image.php

safe_image.php

118 ms

1510660_943977008952722_8967937390211248702_n.png

1510660_943977008952722_8967937390211248702_n.png

61 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

18 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

17 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

17 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

17 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

10 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

5 ms

Accessibility Review

drayage.com accessibility score

68

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

drayage.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

drayage.com SEO score

88

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

Image elements do not have [alt] attributes

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

drayage.com

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