armorfreight.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.

59 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

7 third-party services load with your homepage (Google Tag Manager, YouTube and Other Google APIs/SDKs and others), adding 2.1 MB and 1.3 s of main-thread time.

Google Tag Manager costs a phone 675 ms of main-thread work and 771 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

YouTube costs a phone 549 ms of main-thread work and 1,013 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

2 images could be 578 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.

A phone's processor spends 3.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

16 long tasks block the main thread while loading, the longest for 230 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 files are served with short cache lifetimes, so returning visitors download them again (3 KiB).

The first text or image appears after 9.1 s on a phone. Good is under 1.8 s.

Your largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FREIGHT. WAREHOUSING. DISTRIBUTION. One Team. One Plan. One…”.

The page becomes fully interactive after 23.2 s. Good is under 3.8 s.

Visually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 500 ms in total while the page loads. Good is under 200 ms.

The layout shifts by 0.129 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.5 MB in 127 requests on a phone: scripts 2.1 MB (44), images 1.7 MB (13) and fonts 466 KiB (11). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

52 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h3 → h5, h3 → h5 and h1 → h5), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“WHAT WE OFFER”, “888-507-0767” and “CONTACT US”). One clear main headline is easier for people and search engines.

8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 113 pages on armorfreight.com and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/allentown-warehousing and /warehouse-crossdock-quote all use the title “Allentown Warehousing & Cross-Docking Services”. Search engines can't tell which page to show for a search, so each competes with the others.

We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://armorfreight.com' has been blo…”.

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

armorfreight.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

armorfreight.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 933 words of visible text.

armorfreight.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be armorfreight.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.